This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Netbeans 6.8m2 on Kubuntu Example: Project FooEJB copied to (right click on project -> Copy...) BarEJB On BarEJB, the project.properties file on line 25 = "jar.name=FooEJB.jar", so when it is deployed to the server, it is deployed as FooEJB.jar not as BarEJB.jar. Thanks, Fernando
this should probably be an option... and maybe not even the default option. My reasoning: We do not know why the user is creating the copy... there are a couple possibilities and those possibilities seem to dictate different choices. 1. the user is making a backup copy of the project before they start to do some kind of tricky refactoring... it is unlikely that they want to change the name of the jar file. Should they use a real SCM like cvs, svn, etc. instead? Yes... but we know from numerous surveys that folks do not. 2. The user is creating a versioned 'snapshot' of a project... say taking my-cool-functionality.jar and creating a my-cool-functionality-1.1.1.jar... Same action. Different goal. Neither choice is going to be 'always right'. Another note though: copying a Java Library project does rename the resulting jar.
I am copying the project as it is a "template" for my future projects, and I do it very often. If you copy a Java Application Project, it will change the name of the resulting jar, but the same does not happen when you copy an EJB Project. Regards, Fernando
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss