I did it now with working with profiles and profile-activation by env-var. So
I don't have to give a -P option but can use the -Dskip.integration.test
parameter to activate the profile, this way I don't mess around with
multiple -P and -D options:
------------------------------------
<profile>
....
<activation>
<property>
<!-- trigger profile if value is false -->
<name>skip.integration.test</name>
<value>false</value>
</property>
</activation>
...
</profile>
---------------------------------
aldana wrote:
>
>
>
> Wendy Smoak-3 wrote:
>>
>> On Thu, Jun 25, 2009 at 7:41 AM, aldana<[email protected]> wrote:
>>
>>> I am controlling running integration-tests by setting a property
>>> skip.integration.test (easier as setting up an integration test
>>> profile).
>>>
>>> problem is that I also want to skip the pre-integration and
>>> post-integration
>>> phase for that (jetty start/stop plugin runs under this phases).
>>> unfortunately jetty plugin does not offer a skip parameter itself.
>>>
>>
>> You can't skip phases, but you can put the Jetty plugin executions
>> into a profile, and activate that with a property.
>>
>> --
>> Wendy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>>
>
> I know that profiles would work for that, but I wanted to avoid all these
> extra verbose profile definitions for this little skip distinction.... But
> I guess I have to go this path :(
>
-----
manuel aldana
aldana((at))gmx.de
software-engineering blog: http://www.aldana-online.de
--
View this message in context:
http://www.nabble.com/how-to-generally-skip-pre-and-post-integration-test-phase-tp24204569p24217268.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
