Thanks..
That does make sense. So I'd create a release module that has a client application as dependency, that's what you mean? So one release module for one application. Kind of like an ear packaging a war, in a broad analogy then? In the super pom bundling the modules I then add these modules to the modulelist? Or only in a seperate profile meant for the release? Antonio Petrelli wrote: > > 2010/12/7 fhomasp <[email protected]>: >> I don't quite know how to put this, but I'll give it a shot. >> >> Basically there are 3 client applications with Swing UI that need to get >> released. These have common dependencies bundled in a common dir. For >> this >> part, I don't see much of a problem, I'll get a super pom to get that >> working, however I'm unsure which plugin I should use. The global >> release >> structure should look like this: >> \application 1 >> \application 2 >> \application 3 >> \common >> >> >> However each application also has an internal release structure, which is >> more or less similar for each of them. The client applications all have >> packaging jar. The target release dir structure should go like this: >> >> \bin (holds a service wrapper, and a .bat executable) >> \conf (holds property files) >> \lib (holds the actual application jar, so the actual mvn package target) >> \log (the log files) > > Use the maven-assembly-plugin in a separate module for each assembly > you need to use: > http://maven.apache.org/plugins/maven-assembly-plugin/ > You can still use the appassembler plugin, but it is useful only to > build launch scripts, not to create distributions. > > Antonio > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://maven.40175.n5.nabble.com/Create-complicated-client-jar-release-target-s-tp3295582p3295674.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]
