But if you have the problem with the bandwidth so why you wanna make all in one archive ? IMHO I think you should make it in separate archives and update only the archives you need to update.
On Thu, Jan 13, 2011 at 8:25 AM, Kevin Meyer - KMZ <[email protected]> wrote: > 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 > > -- Thanks - Mohammad Nour Author of (WebSphere Application Server Community Edition 2.0 User Guide) http://www.redbooks.ibm.com/abstracts/sg247585.html - LinkedIn: http://www.linkedin.com/in/mnour - Blog: http://tadabborat.blogspot.com ---- "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein "Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best." - Clean Code: A Handbook of Agile Software Craftsmanship "Stay hungry, stay foolish." - Steve Jobs
