Status: Resolved (View Workflow)
Affects Version/s: 4.0.0.Final, 4.1.0.Final
While trying to perform a release (which eventually got stuck while uploading to Nexus) I noticed the following:
- the modeshape binary distribution (zip) does not contain any of the embedded examples (from /demos)
- in order to build the above distribution, each module creates a zip assembly (e.g. component-with-dependencies) which is incorrectly attached as a deploy artifact resulting in Maven trying to upload GB worth of useless data to Nexus.
The correct behavior is that during mvn deploy only relevant Maven artifacts - jars, test-jars, wars - should be uploaded to Nexus and nothing else.
Also, there are a number of modules that should not be deployed:
- demos - This directory in the source code contains Maven modules that are examples. But, they're designed to work only within our binary distribution, so they cannot be used as Maven dependencies
- modeshape-distribution - This creates our ZIP file distributions that are available via the project's download area on jboss.org.
- integration - This directory in the source code contains several Maven modules that are integration tests used during our build to verify functionality. There's no reason outside of the build process (that requires a local codebase) to depend upon or use these tests
- modeshape-performance-tests - These are performance tests that client applications would never use/need
- modeshape-jcr-tck - This is our version of the TCK test. Again, there's no reason any client would need/use these
- deploy - This directory in the source code contain the JBoss/Wildfly module and WARs. These are included in our Wildfly distribution (available on the project's downloads page), and there's no way to really use the artifacts that are in Maven