Hey, 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) For this problem someone already did an attempt with the appassembler-maven-plugin with groupId org.codehaus.mojo. Any suggestions on this matter are appreciated. -- View this message in context: http://maven.40175.n5.nabble.com/Create-complicated-client-jar-release-target-s-tp3295582p3295582.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]
