We use http://www.mojohaus.org/flatten-maven-plugin/ to strip out "development-related" stuff, parent POMs, etc. from our POMs for our "leaf" artifacts so that they have standalone POMs with only their dependencies in them.
-----Original Message----- From: Francois MAROT [mailto:[email protected]] Sent: Thursday, November 05, 2015 4:29 PM To: [email protected] Subject: Re: Convention for shipped artefacts? I have kinda the sae project: 50 or so modules, 3 'leaf' artifacts (I coined the term 'leaf' to designate the artifacts that will actually be shipping outside. For me those 3 artifacts share the fact they are each an obfuscated über-jar, and each composed of a combination of the other artifacts. As they are obfuscated, I created an "obfuscated-parent" module (of type 'pom') to contain the 3 leaf artifacts. So people now know that they find the modules visibles to end-users in the 'obfuscated-parent' directory/module. It's the best I came up with. -- View this message in context: http://maven.40175.n5.nabble.com/Convention-for-shipped-artefacts-tp5851343p5851467.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
