I have a simple project which produces a java stand-alone and I need to produce the distribution zip file, and I would like to have a maven goal to do that.
I had a look at maven's built-in dist task, and I can see a broad compatibility there with my aims, but there is a large amount of work that it undertakes which I would like to cut out, and a couple of points that I would like to adapt. Maven's documentation makes several references to the Maven way of doing things, such as 'try not to have a maven.xml' and 'it's not recommended to use maven.junit.skip', and wanting to stay in the same paradigm, rather than just coding a big ant script like the old ant developer I am, I'm asking myself what the best approach is. I want to produce a zip containing a directory structure like so: /lib - dependency jars and my jar /bin - shell scripts to launch java /conf - config & property files /log - for output And I would like to avoid running tests and reports and doing a website xdoc build. Any pointers, anyone? Adam http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this.
