You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Nathan Coast <na...@codeczar.com> on 2006/11/18 14:43:06 UTC

integration-test triggering additional rebuild / reload

Hi,

apologies but if this is a bit of a newbie question....  I have an 
aggregator project.

    <modules>
         <module>../i18n-model</module>
         <module>../i18n-admin</module>
         <module>../i18n-client-jar</module>
         <module>../i18n-client</module>
         <module>../i18n-struts-demo</module>
         <module>../i18n-jstl-demo</module>
     </modules>

when running on unmodified projects:
aggregator>mvn integration-test

all of the artefacts are effectively touched due to a timestamp change
e.g 
i18n-model\target\i18n-model-1.0.jar\META-INF\maven\com.codeczar.i18n\i18n-model\pom.properties

As there are interdependencies between the components, when 
integration-test is executed for the i18n-admin webapp the dependencies 
are re-copied into the WEB-INF/lib.  This in turn kicks off a tomcat 
reload, which is greatly slowing down my integration tests (also causes 
errors as the tests kick in before the reload has completed).  When 
running integration-test directly from the webabpp project, no reload 
occurs as non of the dependencies have been modified.

I guess the problem I'm seeing is that the steps prior to 
integration-test modify files in the jars even if none of the sources 
have changed.

Is there any way to execute the integration tests without all of the 
preceding steps?  Alternatively is it possible to prevent the dependency 
artefacts being modified during the steps preceding integration-test?

cheers
Nathan


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: integration-test triggering additional rebuild / reload

Posted by franz see <fr...@gmail.com>.
Good day to you, Nathan,

Builds in maven are executed by running a phase and / or a goal. When you
execute a phase, all the preceeding phase are executed as well. But when you
execute a goal, only that goal is executed. 

So to execute a phase without executing its preceeding phases, you'd have to
execute the goals on that phase.

For example, if you have a surefire:test in your integration-test, and you
want to execute only the integration-test only and not its preceeding
phases, you should do

mvn surefire:test

Cheers,
Franz


Nathan Coast wrote:
> 
> Hi,
> 
> apologies but if this is a bit of a newbie question....  I have an 
> aggregator project.
> 
>     <modules>
>          <module>../i18n-model</module>
>          <module>../i18n-admin</module>
>          <module>../i18n-client-jar</module>
>          <module>../i18n-client</module>
>          <module>../i18n-struts-demo</module>
>          <module>../i18n-jstl-demo</module>
>      </modules>
> 
> when running on unmodified projects:
> aggregator>mvn integration-test
> 
> all of the artefacts are effectively touched due to a timestamp change
> e.g 
> i18n-model\target\i18n-model-1.0.jar\META-INF\maven\com.codeczar.i18n\i18n-model\pom.properties
> 
> As there are interdependencies between the components, when 
> integration-test is executed for the i18n-admin webapp the dependencies 
> are re-copied into the WEB-INF/lib.  This in turn kicks off a tomcat 
> reload, which is greatly slowing down my integration tests (also causes 
> errors as the tests kick in before the reload has completed).  When 
> running integration-test directly from the webabpp project, no reload 
> occurs as non of the dependencies have been modified.
> 
> I guess the problem I'm seeing is that the steps prior to 
> integration-test modify files in the jars even if none of the sources 
> have changed.
> 
> Is there any way to execute the integration tests without all of the 
> preceding steps?  Alternatively is it possible to prevent the dependency 
> artefacts being modified during the steps preceding integration-test?
> 
> cheers
> Nathan
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/integration-test-triggering-additional-rebuild---reload-tf2659553s177.html#a7430494
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org