[hogdriver]

This is my situation:

1 – have an EJB module which references two seperate projects, ‘A’ and ‘B’.
2 – have an Enterprise J2EE project which has the EJB module

I am able to deploy the EAR with the two dependent project ‘A’ and ‘B’ JAR files in the root of the EAR file/directory. However, the EJB project has no reference in the manifest to those dependent JAR files it needs to be deployed properly.

I was reading the tutorial included in my version of MyEclipse (4.0.3 GA) and it talks about adding project references, which I have done. Then it goes onto say as part of the last point in the help document, to right-click on my EAR project, select MyEclipse, then select the “Generate Module Manifests” menu. I DON’T HAVE THIS MENU OPTION. Am I missing something? It sounds logical that this step would be here, just I don’t have it. Is the tutorial old and this is no longer an option with MyEclipse?

Please help, thanks!

[Scott Anderson]

Sorry for the confusion. What you need to select when you right-click on your EAR project in the Package Explorer view is MyEclipse > New Module Manifests. It looks like the menu option has simply been renamed and the tutorial is a bit out of date with that.

[hogdriver]

Scott, I saw the option you mention. It generated an empty manifest file.
For now I’ve gone into the Manifest file for my EJB project and added a.jar and b.jar to the class-path declaration. Any way to get this auto generatyed from MyEclipse?

[Scott Anderson]

Try adding Project References from your enterprise project to the ‘library’ projects (A & B) that your EJB project requires. Then, try generating the manifests. Did that work?

[Author]

Posts