[GLASSFISH-18623] server-mgmt.jar is shipped in glassfish-cluster (it should be elsewhere) Created: 12/Apr/12  Updated: 22/Jan/13  Resolved: 22/Jan/13

Status: Resolved
Project: glassfish
Component/s: packaging
Affects Version/s: 4.0_b32_ms1
Fix Version/s: 4.0_b72_EE7MS4

Type: Bug Priority: Major
Reporter: Tom Mueller Assignee: Romain Grécourt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The server-mgmt.cli JAR file is being shipped in the glassfish-cluster package. However, this JAR file is needed even if the glassfish-cluster package is uninstalled.

The server-mgmt.cli JAR file should be shipped in glassfish-common (or some other common place) like it was in 3.1.2.



 Comments   
Comment by Tom Mueller [ 12/Apr/12 ]

From Romain:

server-mgmt was added transitively. Whenever there are some maven changes, some jars might be included in some package.

This is also partly because of how the packager modules are mapping their graph on top of the maven graph.
Each module produces a list of the jars it has (in a property file). Most of the packager modules define a dependency of classifier "properties" in order to get the list of the jars from another module to exclude them from transitive dependencies (maven-dependency-plugin:copy-dependencies). After having excluded the jars, the list will be extended with the list of jars inside the module and then attached as artifact so that other modules could use it for excluding transitive dependencies.
This means that some jar could be included transitively in a wrong package, and then excluded from the right package.

Comment by Romain Grécourt [ 22/Jan/13 ]

as of 58667, server-mgmt.jar is part of nucleus (glassfish-nucleus) package.

Generated at Thu Mar 05 22:45:28 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.