[mojo-dev] [jira] (MNBMODULE-137) Option to use invariable JAR name for Class-Path extension

[Jesse Glick (JIRA)]

Jesse Glick commented on MNBMODULE-137 Option to use invariable JAR name for Class-Path extension “when performing a release you cannot depend on any snapshots anyway, no matter if coming from reactor or not”—exactly the point; during a release build the library dependency would no longer be a snapshot, so would use the longer Class-Path form, contrary to what you see when building previews of the project using snapshot versions. Yes you could use ext/groupId/artifactId.jar, i.e. omit -version, whenever the version matches that of the owning module. I guess that would be the simplest change which would address this issue. It might even suffice to unconditionally omit -version, which would also be more convenient for library descriptors, though not critical in combination with maven-release-plugin as the stated issue. The reasoning is that there is no chance of conflict within this NBM (a given artifact can only be a dependency of this module in a single version). The risk is that one module bundles ext/asm/asm-3.0.jar while another bundles ext/asm/asm-4.0.jar; they could not then be installed together in a single cluster. (Ideally the NetBeans plugin system would keep a separate installation directory for each NBM but that seems unlikely to happen.) Therefore this strategy would have to be disabled by default, being enabled by the developer only for modules which can ensure that they are the only ones to bundle the library (typically because the library is in the same reactor tree).

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email