We have an issue with one of our applications being migrated to MyEclipse Blue in which the generated module manifest for the EJB project contains the name of the Java project JAR file in an incorrect case in the class path. The name was generated as pparpcjava.jar. This caused a runtime error in the deployment environment. The name of the JAR was manually changed to pparpcJava.jar and this solved the problem. However, the application fails to run in the local development environment unless the name is changed back to pparpcjava.jar.

Is this a known bug in MEB or does eclipse not like the word java with a capital "J"?

*** Date: Tuesday, August 9, 2011 10:43:45 AM ET

*** Platform Details:

*** System properties:
awt.toolkit=sun.awt.windows.WToolkit
birt.designer=true
birt.viewer.root.path=/C:/Program Files/Genuitec/Common/plugins/org.eclipse.birt.report.viewer_2.5.2.v20091210/birt/
birt.viewer.working.path=C:\workspaces\.metadata\.plugins\org.eclipse.birt.report.viewer
com.genuitec.pulse.client.basedir.location.override=C:\Program Files\Genuitec
com.genuitec.pulse.client.blueprint.id=rb-578451-1290523577981
com.genuitec.pulse.client.credentials=fi7E1gqdKuoZx+6tZUsfI94dcBeg6Imeyxl7GYbKjt8w0gbOWbsiMM9RNPoRAVOM+cg3r8jdAHBd Rcb0YxVDcUMcKaUvzVKXAUEU1mMZDObm1U3MbbCOA6teRRRVMn7ztaUA4WtIi2z98IJpc0Wg7f4U GdqQYMA/LThOpb1CH7s=
com.genuitec.pulse.client.handshake.id=054dfb52-30fd-462e-b8d9-395c94edd4b2
com.genuitec.pulse.common.server.url=https://www.poweredbypulse.com:443
eclipse.commands=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\Genuitec\MyEclipse-Blue-Edition-8.6\myeclipse-blue.exe
-name
Myeclipse-blue
--launcher.library
C:\Program Files\Genuitec\MyEclipse-Blue-Edition-8.6\../Common/plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519\eclipse_1206.dll
-startup
C:\Program Files\Genuitec\MyEclipse-Blue-Edition-8.6\../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-install
C:/Program Files/Genuitec/MyEclipse-Blue-Edition-8.6
-vm
C:/Program Files/Genuitec/Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dll
eclipse.home.location=file:/C:/Program Files/Genuitec/MyEclipse-Blue-Edition-8.6/
eclipse.launcher=C:\Program Files\Genuitec\MyEclipse-Blue-Edition-8.6\myeclipse-blue.exe
eclipse.p2.data.area=C:\Program Files\Genuitec\Common\configuration
eclipse.p2.profile=com.poweredbypulse.profile-0-rb-578451-1290523577981
eclipse.product=com.genuitec.myeclipse.blue.product85.ide
eclipse.startTime=1312900931360
eclipse.vm=C:/Program Files/Genuitec/Common/binary/com.sun.java.jdk.win32.x86_1.6.0.013/jre/bin/client/jvm.dll
eclipse.vmargs=-Xmx512m
-XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=64m

akoniv79,

I have escalated your post to dev team. They would get back to you on this.

Sorry for the inconvenience.

akoniv,

This appears to be a general case specific problem, not a problem with "Java" itself.

1) This is a dependent Java project and not an actual JAR file, correct?
2)

Quote:

The name was generated as pparpcjava.jar

- can you please clarify this point, is this the generated JAR file or an entry in the MANIFEST.MF.
2) Just to be clear, can you please state what the name of the project is and what the entry in the MANIFEST.MF is?
3) You mentioned changing the name of the JAR, was this in the manifest.mf of the ejb or elsewhere?

Support-Brian wrote:

akoniv, This appears to be a general case specific problem, not a problem with "Java" itself. 1) This is a dependent Java project and not an actual JAR file, correct? yes 2) Quote: The name was generated as pparpcjava.jar - can you please clarify this point, is this the generated JAR file or an entry in the MANIFEST.MF. yes, once the manifest file is generated the dependant project jar file shows up spelled incorrectly 3) Just to be clear, can you please state what the name of the project is and what the entry in the MANIFEST.MF is? name of the project is pparpcJava 4) You mentioned changing the name of the JAR, was this in the manifest.mf of the ejb or elsewhere?

The name was changed manually in the manifest file to have both spellings in order to work when deployed.

This appears to be a general case specific problem, not a problem with "Java" itself.

1) yes
2) yes, once the manifest file is generated the dependant project jar file shows up spelled incorrectly
3) name of the project is pparpcJava

sorry posted incorrectly