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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Convention for shipped artefacts?
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:francois.ma...@gmail.com] Sent: Thursday, November 05, 2015 4:29 PM To: users@maven.apache.org 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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Convention for shipped artefacts?
Two options that I know of: 1) Create a module that creates a single jar containing all of the code to be shipped. 2) If you want to ship a number of jars, create a Maven project using IzPack to create an installer that collects the jars to be shipped and builds an installer that will permit them to be deployed easily. We have done both in different circumstances. Ron On 04/11/2015 4:20 AM, James Green wrote: Open question: I am looking at a project that consists of two or three dozen small maven modules. Out of this we ship maybe six artefacts. Does anyone have experience of managing this? I'm having difficulty locating those projects that actually result in a shipped artefact. Perhaps it's structure, perhaps it's naming. Thanks, James -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
