Hi Kevin! This is either achievable by using the maven-dependency-plugin unpack-dependencies + maven-assembly-plugin for re-packaging it again or by using the maven-shade-plugin.
The more 'modern' way is to use the maven-shade-plugin. This would also allow you to 'shade' artifacts to different packages (e.g. org.apache.commons.logging would become my.private.org.apache.commons.logging) so it helps you with preventing classloader problems. LieGrue, strub --- On Thu, 1/13/11, Kevin Meyer - KMZ <[email protected]> wrote: > From: Kevin Meyer - KMZ <[email protected]> > Subject: Seperating into archives... > To: [email protected] > Date: Thursday, January 13, 2011, 8:25 AM > Hello all, > > Happy new year, Sylvester, and all that! > > I've been very quiet recently - taking a (well deserved) > break after > much activity last year. > > Anyway - I just wanted to check with you people, who have > more > experience with this... > > A few years ago I provided a few business solutions based > on the > Naked Objects Framework (java, at the time) to a few > clients. The > deliverables effectively consisted of 3 parts: > a) The client solution application (jars, images, etc), > b) the NOF framework, > c) other dependencies required by the NOF. > > For space reasons (I had and still have very limited > bandwidth), > I wanted to separate these three (so I could independently > update and > replace 1 of the three "libraries"). > > Most of the day-to-day changes affected only the client > application, > which was also conveniently, the smallest. > > Now, I return to my question: How difficult is it to create > 3 (for > example, jars), that neatly contain only 1 of the three > deliverables, as > mentioned above? > > I can see that the application archives can be built > extracted as part of > the standard "mvn install". The same is also true of the > individual > components that make up the (Isis) framework - but it would > be > convenient to be able to aggregate the required framework > archives > into a single archive, and do the same again (i.e. a single > archive) for > the framework dependencies (e.g. all the other components > managed > by maven). > > Comments? > > Regards, > Kevin > >
