@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