No fix version means that it's not scheduled yet.
Plugins follow their own lifecycle, so you'll be able to use it in any
maven2 version

On 2/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Marcin,
>
> I didn't see a fix version.  Do you know if this is going to be fixed in
> Maven-2.0.3?
>
>
> Thanks,
> Ian
>
> It's better to be hated for who you are
> than loved for who you are not
>
> Ian D. Stewart
> Appl Dev Analyst-Advisory, DCS Automation
> JPMorganChase Global Technology Infrastructure
> Phone: (614) 244-2564
> Pager: (888) 260-0078
>
>
>
>                       Marcin Cetnarski
>                       <[EMAIL PROTECTED]        To:       "Maven Users List" 
> <[email protected]>
>                       com.pl>                  cc:
>                                                Subject:  Re: [m2] 
> Surefire-Plugin ignores argLine
>                       02/13/2006 02:15
>                       AM
>                       Please respond to
>                       "Maven Users
>                       List"
>
>
>
>
>
> Hello Jim,
>
> Are you working on Windows? There is a bug in Surefire on Windows platform
> in
> forkMode. See http://jira.codehaus.org/browse/SUREFIRE-30. Maybe this
> will help.
>
>
>
> JB> I am trying to run tests with assertions enabled, but the surefire
> JB> plugin is apparently ignoring the argLine parameter.  If I specify the
> JB> following, assertions are not turned on:
>
> JB> ...
> JB>   <build>
> JB> ...
> JB>     <plugins>
> JB>             <plugin>
> JB>                 <groupId>org.apache.maven.plugins</groupId>
> JB>                 <artifactId>maven-surefire-plugin</artifactId>
> JB>                 <configuration>
> JB>                     <test>**/*TestSuite*</test>
> JB>                     <useFile>false</useFile>
> JB>                     <forkMode>once</forkMode>
> JB>                     <argLine>-ea</argLine>
> JB>                 </configuration>
> JB>             </plugin>
> JB> ...
> JB>     </plugins>
> JB>   </build>
> JB> ...
>
> JB> By the way, I did try this with -enableassertions as well (which is
> what
> JB> is shown in the surefire example doc), and it made no difference.
>
> JB> As a further example, this produces no error at all, even though it
> JB> clearly should, so this argLine parameter is really being ignored:
>
> JB>             <plugin>
> JB>                 <groupId>org.apache.maven.plugins</groupId>
> JB>                 <artifactId>maven-surefire-plugin</artifactId>
> JB>                 <configuration>
> JB>                     <test>**/*TestSuite*</test>
> JB>                     <useFile>false</useFile>
> JB>                     <forkMode>once</forkMode>
> JB>                     <argLine>-xxx</argLine>
> JB>                 </configuration>
> JB>             </plugin>
>
> JB> What is the right way to get surefire to run tests with assertions on?
>
> JB> Jim Babka
> JB> Senior Software Engineer
> JB> Main: (512) 334 3200
> JB> Direct: (512) 334 3237
> JB> Email: [EMAIL PROTECTED]
> JB>
> JB> Webify Solutions
> JB> Enabling the On Demand Enterprise(tm)
> JB> www.webifysolutions.com
>
>
> JB> ---------------------------------------------------------------------
> JB> To unsubscribe, e-mail: [EMAIL PROTECTED]
> JB> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> --
> Pozdrowienia,
>  Marcin Cetnarski
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to