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.
When we do a blueprint import we need to be able to change the name of the jar file a project (from existing sources) will create.
Would a new parameter to EjbJarProjectGenerator.importProject() do? Its type could be either String, or (maybe better) Properties, which would allow you to override multiple properties.
I guess using the Properties is a better choice. I am already impl dependent, so I can get the property names as needed.... Breaking the impl-dep will imply the need to publish the property names at some point in the future (even if it is only to friends...)
I've been thinking about it... I like the Properties way more, but OTOH if you know you'll only override the jar name, maybe it's overkill. It will also make breaking the impl dependency harder (I don't want the expose a whole package). This hasn't come to my mind when I proposed the Properties parameter. Let's stick to a String for now. If necessary, it shouldn't be difficult to switch to Properties later. Let me know what you think. If you agree, I will add the parameter tomorrow.
having the string should be fine. I added pavel to the CC, so he can chime-in or follow your lead on this. I have a similar enhancement req. on web/project
Fixed. Use the public static AntProjectHelper importProject(final File dir, final String name, final File[] sourceFolders, final File[] testFolders, final File configFilesBase, final File libFolder, final String j2eeLevel, String serverInstanceID, String jarFileName) throws IOException) method in EjbJarProjectGenerator.