[pcable]

I have a question regarding a high level MyEclipse configuration setting.
Just so that we are on the same page about which setting, you get to the setting in question as follows:
Window –> Preferences… –> MyEclipse –> J2EE Project –> Web Project
then on the Deployment Tab

I have some projects that need the “Dependent Java Project Deployment Policy” set to “Jar dependent Java project output and place in ‘lib’ directory” and then I have another project that needs the policy set to “Ignore dependent Java projects (I will manually manage them)”.

Is there a way to keep this set one way and then set them per a project level setting that gets saved in one of the .* properties files?

[Loyal Water]

You can set the deployment policy at project level as well. You can go to Project > Properties > MyEclipse > Web then under the Deployment tab you can uncheck the “Use workbench default settings” check box and set your deployment policy which would be project specific.

[pcable]

What deployment policy would you recommend for the global policy?

[Loyal Water]

If you have dependent projects then I guess using the Smart Deployment for dependent Java projects makes the most sense to me. Actually depends on what your project needs.

[Geoff]

Okay so I am trying to work deploy jars that the web and ejb projects depend on in the ear project that they are included in.

I have been doing something very similar in Netbeans and now I am trying to switch back to MyEclipse after my Hiatus.

Anyway, this is what I learned about deploying jar files (say my entity beans) in Java EE 5. They belong in the /lib directory of the ear file. The app server will then make them available to all applications deployed in the ear file (using the same class loader). If they are included in the web app then they cannot be passed from the web app to the ejb layer.

So netbeans offers a nice way to handle this. When you add project dependencies to your web / ejb projects you can uncheck the package option so that the jar is not packaged with each unit. Then you pull up your packaging settings for the ear project and then you tell it to package all of these jars and you can specify the folder to use (/lib).

When I am trying to configure MyEclipse to do something similar (by going through the Deployment Policy) I do not see any way to specify that they should go to the /lib directory. Instead it says they will go to the root of the ear and I need to specify the Classpath in the Manifest. I believe this is not the right way to do it. Can you provide me some insight on this? Are you guys planning on changing this?

Also, as a side note, normally I add project dependencies using the Build Path dialog. Now I’ve noticed that the properties page also includes Project Deployments and that they say about the same thing. In addition, the projects that are checked do not match. I’m not sure if this is a MyEclipse thing or not, but since it is so releated I thought I ought to include it here as well.

Thanks again for such a great product.

I am using MyEclipse 5.5.1 on Eclipse 3.2.2 on LInux using java SE 5_11

[Riyad Kalla]

Geoff,
I’ve filed this issue for investigation, it sounds like something changed with java EE 5 and we need to support it.

As for deployment filtering, it’s only based on *type* right now, but we do need to add our full deployment filtering that we’ve been working on to a future release, most likely 6.1

[Author]

Posts