facebook

Configuring resulting name of ear, war and jar files

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #198679 Reply

    Hello support team,

    is there a way to configure the resulting name of a ear, war of jar file geenrated by the J2EE project types? Currently the use by default the name of the poroject itself.

    Regards,
    Jörg

    #198681 Reply

    support-michael
    Keymaster

    Presently the convention for naming exploded or packaged archives during deployment is as follows:

    EAR = project name
    EJB JAR = project name
    Web = context-root name

    We have a planned archive export feature that will allow users to explicitly name the archive. The current convention were put in place purely for deployment support. Will the export feature work for your purposes or do you need the deployment engine to use a different naming convention?

    Michael
    MyEclipse Support

    #198686 Reply

    @support wrote:

    Presently the convention for naming exploded or packaged archives during deployment is as follows:

    EAR = project name
    EJB JAR = project name
    Web = context-root name

    We have a planned archive export feature that will allow users to explicitly name the archive. The current convention were put in place purely for deployment support. Will the export feature work for your purposes or do you need the deployment engine to use a different naming convention?

    Michael
    MyEclipse Support

    Hi michael

    Web = context-root name

    Hmmm. According to my experience this also correlates with the project name, but thinking about it, it sould have been the context-root …

    I’ve managed to change the name of the embedded EJB jar and Web module by modifying “.mymetadata”, but the resulting ear’s name could not be changed with this trick…

    We have a planned archive export feature that will allow users to explicitly name the archive. The current convention were put in place purely for deployment support. Will the export feature work for your purposes or do you need the deployment engine to use a different naming convention?

    Since I am currently evaluating MyEclipse, I am not really sure, if I understand the implication of the proposal. My intention was just to define the name of the resulting archive of each project type on my own. Clearly I will thihnk next time more about the project’s name, but is there currently a good way to rename it? A simple Eclipse project can be renamed just by changing the name in the “.project”.

    Regards,
    Jörg

    #198695 Reply

    Scott Anderson
    Participant

    Jorg,

    Clearly I will thihnk next time more about the project’s name, but is there currently a good way to rename it? A simple Eclipse project can be renamed just by changing the name in the “.project”.

    Renaming the projects should only be done by right clicking on them and selecting ‘Refactor > Rename…’ from the context menu since this will kick off the workspace builders and enable us and all other plugins to reconcile any metadata. Manually editing of the .project file should definately be avoided and will be problematic.

    –Scott
    MyEclipse Support

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Configuring resulting name of ear, war and jar files

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