[fstofberg]

Hi,
We are in the process of evaluating MEBlue9 looking to replace RAD7.5

What we had in RAD was the following (and it worked perfectly)

Ear Project
 |
 +lib
 | |
 | +-logging/3rd party jars
 |
 +-multiple jar project (normal java)
 |
 +-multiple war projects

Now, our war AND jar projects have references to both our jar projects as well as the 3rd party jars. These are resolved in META-INF/MANIFEST.MF

This all works 100% in RAD, and ear exporting is good.

Experience with MEBlue9 is slightly different.
When checking our projects out of SVN and applying the “Enhance RAD Projects to work with MyEclipse…” every thing SEEMS fine, all compiles and all is happy
BUT
When adding my EAR Project to a WAS runtime (6.1 or 7, makes no difference) the ear gets built and deployed (packaged or exploded, makes no difference). Upon inspection of the ear file, all the 3rd party jars (earProjec/lib/abc.jar) are copied to the root of the ear. This causes the ear file to be MUCH larger in size than it should be, and because the jar/war projects have references to the jars inside lib (via MANIFEST.MF) all the 3rd party jars that are in the ear root are redundant.

How can we have the 3rd party jars not copy to the root of the ear?

I hope this makes sence 🙂
Thanks

[support-swapna]

fstofberg,

1) You can change your EAR deployment policies for a particular project from Project > Properties > MyEclipse > EAR > Library Deployment Policies.

2) If you want to change the EAR deployment policies for your workspace, then go to Window > Preferences > MyEclipse > Java Enterprise Project > EAR Project > Library Deployment Policies.

3) Here is a quickstart doc for your reference
http://www.myeclipseide.com/documentation/quickstarts/earprojects/#advanced_features

Let me know how this works for you.

[fstofberg]

hi swapna
I have tried all possible combinations of the library deployment policies.

But all the Libraries are still copied to the root of the trunk.

followed the link to the letter, but nothing

[support-swapna]

fstofberg,

We do not support sophisticated EAR build path management as RAD does. We are planning to implement that in the future.

Currently we can offer you workaround:

1. Create new project with all 3-rd party libraries.
2. Mark all of the jars exported on build path preference path.
3. Add that project to build path of each of the EAR projects.
4. Project > Properties > MyEclipse > EAR . Choose Ignore for ‘Dependent Java project deployment policy’.

Let me know how this works for you.

[Author]

Posts