What's wrong with making them an integration test? Eric
On 1/16/06, dan tran <[EMAIL PROTECTED]> wrote: > > Folks, The native-plugin redefine build lifecycle as > > <component> > > <role>org.apache.maven.lifecycle.mapping.LifecycleMapping</role> > > <role-hint>dll</role-hint> > > <implementation> > org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping > </implementation> > > <configuration> > > <phases> > > <initialize></initialize> > > <generate-sources></generate-sources> > > <compile>org.codehaus.mojo:native-maven-plugin:compile</compile> > > <package>org.codehaus.mojo:native-maven-plugin:link</package> > > <process-test-resources> > org.apache.maven.plugins:maven-resources-plugin:testResources > </process-test-resources> > > <test-compile> > org.apache.maven.plugins:maven-compiler-plugin:testCompile > </test-compile> > > <test>org.apache.maven.plugins:maven-surefire-plugin:test</test> > > <install>org.apache.maven.plugins:maven-install-plugin:install > </install> > > <deploy>org.apache.maven.plugins:maven-deploy-plugin:deploy</deploy> > > </phases> > > </configuration> > > </component> > > > > Where I would like run my junit test after package phase. However, maven > invokes my test right after compile phase. > > Is it allowed to change the order of phases? > > -D >