For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 1 reply, 2 voices, and was last updated 14 years, 11 months ago by
.
-
Posts
-
I’ve migrated an application from RAD7.5 into MEB8.6. The application is currently bulding cleanly and running just fine in MEB8.6. The MEB workspace contains the following projects:
FTNTID (this is the EAR project)
FTNTIDBusiness (contains some business logic)
FTNTIDCommon (contains code common to all projects in workspace)
FTNTIDEJB (contains Session EJBs)
FTNTIDWeb (contains the JSF specific code)The application builds fine and I can run it locally. However, for some reason, in the EAR file, the JAR files at the root of the EAR do not all match the projects in the workspace. FTNTIDEJB and FTNTIDWeb match precisely, but the JAR for FTNTIDBusiness is ftntidbusiness.jar and the JAR for FTNTIDCommon is ftntidcommon.jar. Also, when I generated the manifest files for the EJB and Web project using the option in under MyEclipse, it generates using the lower case names.
This works fine in my local environment, but causes runtime issues in the server environment.
Is there any way to control how the JAR names are generated? Why don’t the JAR names always match the project names in the workspace?
jstanisic,
We were able to replicate your problem locally .Seems to occur only for dependent Java projects while EJB and Web projects are OK. I assume that for production you are using the export EAR option to generate an EAR which you take to your server?
Unfortunately I cannot recommend a workaround right now, but we have filed this and will very likely fix this in the 9.0M2 release.
Also, when I generated the manifest files for the EJB and Web project using the option in under MyEclipse, it generates using the lower case names.
Could you clarify which option you were using exactly?
Sorry for the inconvenience caused and thanks for reporting this issue.
