Write your own plugins.... it's not too hard... In the absolute worst case you may end up implementing your own packaging type, that is not too hard either, but slightly more work than implementing your own plugins, and you need to understand the use case that drives needing your own packaging type.
SO START WITH YOUR OWN PLUGIN first The Maven book has at least one chapter on the subject, and covers it quite well -Stephen On 20 February 2012 11:39, ecniv <[email protected]> wrote: > Hi there, > > I'm new to maven, and currently using it for JAVA projects. > > I'm now wondering if I can use maven efficiently for other projects. As an > example, some of my projects contains XML files and other configuration > files, which have a specific folder hierarchy quite different from the usual > src/main/* hierarchy user by maven. > > These files, once modified, must be reloaded in a specific software using > the command line, and some test must also be run before any production > release, still using the command line. They are versionned in a SVN > repository. > > Can maven be used with such projects ? Is there any possibility to customise > the build process so it fits the requirements of non-java projects ? (i.e. > no JAVA compiler) > > Any comment will be apreciated :) > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Maven-for-XML-project-tp5498778p5498778.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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
