Heather created NETBEANS-1919:
---------------------------------
Summary: Adding new wrapped jars to a netbeans module modifies
existing jars runtime-relative-path in project.xml
Key: NETBEANS-1919
URL: https://issues.apache.org/jira/browse/NETBEANS-1919
Project: NetBeans
Issue Type: New Feature
Reporter: Heather
This is a bug/feature request.
Lets say I create two netbeans modules. Both modules have an external jar
dependency for ex.jar. I add that jar dependency by going into Project
Properties -> Libraries -> Wrapped JARs -> Add JAR. When these modules are both
installed onto the IDE, they both install a ex.jar into the modules/ext folder.
When I uninstall one of those modules, it removes the ex.jar, making the other
module useless. This seems like a bug.
To fix this, I have been modifying the runtime-relative-path for ex.jar in the
project.xml, and I put the jar into a different folder for each module (ex:
ext/module1/ex.jar and ex/module2/ex.jar). This solves the first problem,
however its super annoying if I have to add another jar dependency to my
module, because it will overwrite the runtime-relative-path I wrote for ex.jar
back to ext/ex.jar. If I have a lot of external jars for a module, this can get
really frustrating fast because I always have to go back to the project.xml to
make sure my runtime-relative-path's are correct. I would like to submit a
feature request that allows me to specify this path, so that it wont be
overridden every time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
