Hi Baptiste, Thank you for your answer. By packaging, I indeed thought about a tar/zip file containing not only the jar produced my the mvn package command but as well a set of other files (documentations, sample data, etc. depending on the project).
I will have a look at maven assembly, exec and antrun plugins. Thank you for the tip Ben Le 3 avr. 2010 à 09:45, Baptiste MATHUS a écrit : > Hi Benoît, > > Answers inline. > > Le 2 avril 2010 23:37, Benoît Thiébault <thieba...@artenum.com> a écrit : > >> >> With Maven, I now successfully manage dependencies, generate the code and >> the javadoc (and even the site). It's a real improvement for me. >> >> There are still the packaging and the running aspects that I am wondering >> how to deal with. >> > > Well, what do you call packaging? Since "mvn package" is the packaging > command. > Maybe you the maven assembly plugin. You might be speaking of some tar/zip > that contains documentation, and so on. > > About running, please see if the maven exec plugin could suit your needs. > > Should I keep an Ant script to perform these tasks ? How would my Ant script >> know how to set the classpath ? Including everything under taget/dependency >> (after the execution of the command "mvn dependency:copy-dependencies") in >> the classpath doesn't look very clean to me... >> > > With the maven antrun plugin, it's possible to propagate the right classpath > for the ant execution. So if maven-exec-plugin doesn't fit you, then you > should read the maven-antrun-plugin doc part about classpath handling ( > http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html > ). > > HTH > Cheers. > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
