It seems from the list archvies that I'm not the only one coming here with such questions. 'dist' is a popular token. Have the committers thought about expanding the maven dist plugin to give more flexibility?
Or is it seen as potential trouble-spot that's best kept nailed down to the config it has now? The number of different factors that could be considered when opening up dist is large: file type, project type, internal directory structure, inclusion of dependency jars etc are just a couple that interested me. -----Original Message----- From: Adam Hardy Sent: 23 March 2005 12:57 To: 'Maven Users List' Subject: RE: Best approach to job It takes so long on my old 700MHz machine! Later on admittedly I can foresee not doing distributions very often at all so it wouldn't be an issue, but at the moment I might want to try it 5 times in a row. I can easily take out all the reports from my project.xml. Perhaps setting up goals to run them individually would be an alternative, but I've got the website up already (although mostly for my own use). Is there any documentation on the built-in dependencies between goals? I didn't see (or perhaps better said, recognise) any on the maven website. How would I go about stripping out the reports generation then? -----Original Message----- From: Eric Pugh [mailto:[EMAIL PROTECTED] Sent: 23 March 2005 12:26 To: 'Maven Users List' Subject: RE: Best approach to job What is your objection to doing the tests, reports, and website? Howe often do you expect to do a distribution? You could code around it, but yes, it would be easier to just go with the flow.. You could run the default dist goal, and then add your own logic after that to stip out the parts you don't need/want... -----Original Message----- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 23, 2005 12:20 PM To: Maven Users List Subject: Best approach to job 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
