defining goals that aggregate other maven goals

2007-12-14 Thread Pete Aykroyd
Hi all, I've been searching for any easy way to do this and haven't found one yet. I want to create a plugin that handles the deployment details for our webapps for integration testing. The actual how of deploying the webapps has been completed already using a combination of the dependency, antrun,

Re: svn commit: r604271 - /maven/resources/trunk/apache-jar-resource-bundle/src/main/resources/META-INF/NOTICE.vm

2007-12-14 Thread Dennis Lundberg
*&#¤%#¤ those EOL setting... Should I change the EOL setting in subversion for NOTICE.vm and LICENSE.vm to "native", or will that mess things up? Here's a more readable diff for those that are interested: https://svn.apache.org/viewvc/maven/resources/trunk/apache-jar-resource-bundle/src/main/

[MECLIPSE] how to bypass dependency resolution ?

2007-12-14 Thread nicolas de loof
Hello, some MECLIPSE issues are related to the phase executed by the eclipse plugin to collect generated-* folders. Here is a simple example of the side-effect of this strategy pom.xml |_ ear project |_ jar project |_ war project Lets supose the jar project is broken and can't compile. Checki

RE: maven-scm-providers-git initial version

2007-12-14 Thread Mark Struberg
Hi! Just want to give a short update: 1.) almost all TCK tests are now implemented and pass 2.) The maven-release-plugin works fine now. Full release cycles with both release:prepare and release:perform executed successfully. This is currently still all done under Linux only, but Siegi Goeschl

Re: Surefire 2.4 is coming

2007-12-14 Thread Jerome Lacoste
On Dec 11, 2007 12:25 AM, Dan Fabulich <[EMAIL PROTECTED]> wrote: > > Surefire trunk currently depends on a couple of SNAPSHOT versions that we > expect to be released in the next couple of days, but other than that, as > far as I know, there's nothing else standing in the way of a Surefire 2.4 > r

Re: [MECLIPSE] refactor IT tests to use shitty maven plugin ?

2007-12-14 Thread nicolas de loof
Not sure to understand, maybe I miss-used testing-harness : I set a test POM with just the plugin configuration, so that I can run : File testPom = new File( getBasedir(), "src/test/resources/compile.pom" ); Mojo mojo = (Mojo) lookupMojo( "compile", testPom ); assertNotNul