ext:
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 additiona
[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 shipp
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
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
