I had a chat with Vincent Massol yesterday at the server side symposium about documenting relevant goals in the project.xml. The aim here is to make ant like integration with IDE's and making it easier to find out what goals are relevant for a project. I personally find it a problem that when I checkout a module I need to find tips on build in readme files in various places.
The goals could be put in maven.xml and you could use the description on these to make them more accessible but maven.xml should not be required on all projects - that would be going back to ant in my opinion..
In a current project I can use a database maven plugin to build the database and jboss plugin to launch this app in the container. But I don't want this to happen as the default goal which just builds the application as an ear. A new developer would have to read the how-to-build file in order to find out what goals can be used. F.ex. the war goal doesn't make sense in this context but ear does.
Any thoughts on this?
Thomas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
