[leaked]

– System Setup ——————————-
*** Date:
Tuesday, March 27, 2007 3:25:47 PM EDT

** System properties:
OS=Windows2000
OS version=5.0
Java version=1.5.0_10

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 5.1.0 GA
Build id: 20061111-5.1.0-GA

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 5.1.0 GA
Build id: 20061111-5.1.0-GA

Eclipse Platform

Version: 3.2.1.r321_v20060921-b_XVA-INSQSyMtx
Build id: M20060629-1905

Eclipse Java Development Tools

Version: 3.2.1.r321_v20060905-R4CM1Znkvre9wC-
Build id: M20060921-0945

Eclipse Graphical Editing Framework

Version: 3.2.0.v20060626
Build id: 20060921-1617

Eclipse Project SDK

Version: 3.2.1.r321_v20060801-tQ1w49KnTArT0FZ
Build id: M20060921-0945

Eclipse RCP

Version: 3.2.1.r321_v20060801-2ekW2BxmcpPUOoq
Build id: M20060629-1905

Eclipse Plug-in Development Environment

Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG
Build id: M20060921-0945

Eclipse Graphical Editing Framework

Version: 3.2.1.v20060921
Build id: 20060921-1617

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\Java\eclipse\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
114_54
-product
com.genuitec.myeclipse.product.ide
-vm
C:\WINNT\SYSTEM32\javaw.exe

Are there any exceptions in the Eclipse log file? No

– Message Body ——————————-

When executing “Export…, EAR file (MyEclipse)” on a MyEclipse EAR project which has the “Dependent Java Project Deployment Policy” set as “Jar dependent Java projects (See Notice)” bullet selected and is referencing a dependent project who’se project name (and directory) contains both uppercase and lowercase letters and has included that JAR as a “java module” within the EAR deployment descriptor file (application.xml), the resulting EAR file contains a JAR file for that project which has a file name equal to the referenced project’s name ENTIRELY IN LOWERCASE letters.

One would expect to find a JAR file with a file name containing the same combination of uppercase and lowercase letters as in the original project name. 🙄

This doesn’t cause any problems on MS Windows 2000, but does cause EAR deployments to fail on MS Windows 2003 which seems to be case-sensitive (at least when deploying to JBoss AS 4.0.5 GA). The *NIX users will surely suffer from this bug as well.

[Riyad Kalla]

leaked,
If you use the deployment tool from the toolbar, is the deployed EAR correct? We had reports of this a few years back and it ended up being tied to the platform in some manner and was impossible for us to reproduce on our end… a real pain. But if we can reproduce this we’ll dig in and fix it ASAP.

[Author]

Posts