maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Ewins <Brian.Ew...@btinternet.com>
Subject Re: proposal to remove test:test dependency
Date Tue, 03 Dec 2002 10:57:55 GMT

Nathan Coast wrote:
> need to take care removing test:test as this is how jar:resources gets 
> called to copy additional resources from the src/java path to the 
> compiled classes
> 
That only happens if /are/ classes. The way things are set up, war:war 
doesn't run tests if there are no sources, which is what would happen if 
you build your jars as a separate project, then in your war just 
assemble pre-existing components. Which makes a kind of sense.

> EPugh@upstate.com wrote:
> 
>> What I would actually like to see is something like a switch passed...
>>
>> maven war:war /notest to turn off tests. 
>> If you are doing lots of wars quickly, running all  the unit tests can be
>> old..
>>
>> Eric
>>
>> -----Original Message-----
>> From: dion@multitask.com.au [mailto:dion@multitask.com.au]
>> Sent: Monday, December 02, 2002 5:21 PM
>> To: Turbine Maven Users List
>> Subject: Re: proposal to remove test:test dependency
>>
>>
>> My take on this is it's the same rationale as a jar. If the tests 
>> don't pass, don't build the deliverable.
>> -- 
>> dIon Gillard, Multitask Consulting
>> Blog:      http://www.freeroller.net/page/dion/Weblog
>> Work:      http://www.multitask.com.au
>>
>>
>> "Matt Ho" <matt@indigoegg.com> wrote on 03/12/2002 06:41:19 AM:
>>
>>
>>> Can I suggest that we remove the
>>>   <attainGoal name="test:test"/>
>>>
>>> task for the war:war target?  It seems inappropriate to force all the
>>> unit tests to be run just to build the war file.  It seems to me that
>>> users are always able to call
>>>   maven test:test
>>>
>>> explicitly.  Having war:war call test:test means that:
>>>
>>>   * if you have a lot of unit tests, this can be an extremely long
>>>
>>>     operation.  This can be especially painful if all you want to
>>> do
>>>     is rebuild the war file after making a minor modification
>>>
>>>   * if the machine you intend to perform builds on is not
>>> configured
>>>     to run the tests, you can't build the war file
>>>
>>> Any comments would be appreciated :)
>>>
>>> -- 
>>> Matt Ho
>>> Principal
>>> Indigo Egg, Inc.
>>> http://www.indigoegg.com/
>>>
>>>
>>>
>>> -- 
>>> To unsubscribe, e-mail:   <mailto:turbine-maven-user-
>>> unsubscribe@jakarta.apache.org>
>>> For additional commands, e-mail: <mailto:turbine-maven-user-
>>> help@jakarta.apache.org>
>>>
>>
>>> ForwardSourceID:NT00094A1A 
>>
>>
>>
>> -- 
>> To unsubscribe, e-mail:
>> <mailto:turbine-maven-user-unsubscribe@jakarta.apache.org>
>> For additional commands, e-mail:
>> <mailto:turbine-maven-user-help@jakarta.apache.org>
>>
> 
> 
> -- 
> To unsubscribe, e-mail:   
> <mailto:turbine-maven-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: 
> <mailto:turbine-maven-user-help@jakarta.apache.org>
> 
> 


Mime
View raw message