Release plugin deprecated?

Hi, I notice on the maven website that the release plugin has been deprecated (http://maven.apache.org/reference/plugins/release). What should we be using instead? Cheers, Charles -- http://www.eb2.com Charles Blaxland — Solutions Engineer EB2 International Limited (London & Sydney) Grd F

nested plugin housings?

Hi, I got an error "nested plugin housings" while running the maven torque plugin. Does anyone know what this means and how I can go about fixing it? Many Thanks, Charles - To unsubscribe, e-mail: [EMAIL PROTECTED] For additiona

Re: Overriding properties for different build configurations

ould load your property file using Jelly, which will overwrite any previously defined properties with the same name. Jeff On Tue, 28 Sep 2004, at 11:42:35 [GMT +0200] Gisbert Amm wrote: Charles Blaxland wrote: Hi all, As I understand it, maven loads its properties from project.properties, buil

Overriding properties for different build configurations

Hi all, As I understand it, maven loads its properties from project.properties, build.properties, $HOME/build.properties and the "-D" defines on the command line, in that order, where the last definition wins. However I find myself frequently in the situation where I want another level of prop

Re: How we handle multiple versions of Maven and Maven plugins

Thanks for sharing this info Brian. I've been grappling with this very issue myself, and your solution sounds pretty good. I think this is an area that maven needs to address - ie: how to maintain multiple builds that have different maven/plugin version requirements, or how to build a previou

Inconsistent artifact deployment method across plugins

Hi, The various maven plugins are inconsistent in the way they deploy artifacts to the remote repository. They use, variously, artifact:deploy or deply:artifact, for example: war:deploy -> artifact:deploy ejb:deploy -> artifact:deploy jar:deploy -> deploy:artifact dist:deploy -> deploy:arti