facebook

[Closed] Problem with utility Library Pakaging

💡
Our Forums Have Moved

For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub

  1. MyEclipse IDE
  2.  > 
  3. Java EE Development (EJB, JSP, Struts, XDoclet, etc.)
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #279965 Reply

    ibrahim_theo
    Member

    Dear All,

    I am using Myeclipse for my J2EE development and I am having pakaging problem of the java utility project. Below are the details of my configuration:

    2 EJB projects (EJBHome1 and EJBHome2)
    1 Web project (WEBHome)
    1 java utility project that contains libraries and common classes (COMMONHome).
    1 Enterprise project (Home) that have the 2 EJB modules and 1 Web module.

    I have the constraint of naming convention meaning that these names need to be kept as is. I have followed the instructions from Myeclipse for the packaging of the utility project on the root of the ear. This works fine but the generated jar file name for the utility project (only) is lowercase (commonhome.jar instead of COMMONHome.jar) this makes the generated ear to fail on UNIX platforms. How can this be solved in MyEclipse.
    I am using Myeclipse 5.5 eclipse 3.2.2 with jdk1.4.2.

    Could you please help me on that. Thanks.

    #279980

    Loyal Water
    Member

    Can you go to MyEclipse > Installation Summary > Installation Details and paste the information here for me.

    Can you please switch to a new workspace, create a new ear project and check if this problem persists.

    #279991

    ibrahim_theo
    Member

    Dear Nipun,

    Below are the details of my installation:

    ================

    *** Date:
    Wednesday, December 26, 2007 9:52:09 AM EST

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

    *** MyEclipse details:
    MyEclipse Enterprise Workbench
    Version: 5.5.1 GA
    Build id: 20070521-5.5.1-GA

    *** Eclipse details:
    Eclipse SDK

    Version: 3.2.2
    Build id: M20070212-1330

    Eclipse Project SDK

    Version: 3.2.2.r322_v20070104-dCGKm0Ln38lm-8s
    Build id: M20070212-1330

    Eclipse Platform

    Version: 3.2.2.r322_v20070119-RQghndJN8IM0MsK
    Build id: M20070212-1330

    Eclipse Java Development Tools

    Version: 3.2.2.r322_v20070104-R4CR0Znkvtfjv9-
    Build id: M20070212-1330

    Eclipse RCP

    Version: 3.2.2.r322_v20070104-8pcviKVqd8J7C1U
    Build id: M20070212-1330

    Eclipse Plug-in Development Environment

    Version: 3.2.1.r321_v20060823-6vYLLdQ3Nk8DrFG
    Build id: M20070212-1330

    Eclipse Graphical Editing Framework

    Version: 3.2.2.v20070208
    Build id: 20070208-1315

    Eclipse startup command=-os
    win32
    -ws
    win32
    -arch
    x86
    -launcher
    C:\eclipse\eclipse.exe
    -name
    Eclipse
    -showsplash
    600
    -exitdata
    6a8_74
    -vm
    C:\WINNT\system32\javaw.exe

    ========================

    I have also tried on another installation (with a different workspace then) under XP the same problem happens.

    #280003

    Loyal Water
    Member

    ibrahim_theo,
    Instead of trying another installation of the same version, can you download MyEclipse 6.0.1 and try this out on the latest version of MyEclipse.

    #280008

    ibrahim_theo
    Member

    Nipun,

    I solved partly the problem by keeping the “lower case” generated utility project and updating my respective manifest files for each module. This works on the UNIX platforms. I’ve tried Myeclipse 6.0.1 earlier and I am having the same behaviour.

    #280035

    Loyal Water
    Member

    ibrahim_theo,
    I just checked with my team and what you are getting is expected behavior. When you add a dependent java project and if you set the EAR project preference to deploy dependent java projects, then there is an additional step that you have to do before deployment. You have to rightclick the EAR project and under MyEclipse menu there is a New Module manifest option. This will regenerate the /META-INF/manifest.mf files for both the dependent EJB and WEb module. So in your deployment when you inspect the manifest files you will see that they make a reference to the “commonhome.jar” file. So yes it does lowercase the filename but it also makes it consistent in the corresponding manifest.mf files.

    #280052

    ibrahim_theo
    Member

    Nipun,

    Many thanks I got it working now. Thanks for the help.

    #280176

    Loyal Water
    Member

    This message has not been recovered.

Viewing 8 posts - 1 through 8 (of 8 total)
Reply To: [Closed] Problem with utility Library Pakaging

You must be logged in to post in the forum log in