+1
2008/1/27, Brian E. Fox <[EMAIL PROTECTED]>:
>
> +1
>
> -Original Message-
> From: Dan Fabulich [mailto:[EMAIL PROTECTED]
> Sent: Saturday, January 26, 2008 2:53 PM
> To: Maven Developers List
> Subject: [VOTE] Release Maven Surefire plugin version 2.4.1
>
>
> With a change as big as Su
+1
-Original Message-
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 26, 2008 2:53 PM
To: Maven Developers List
Subject: [VOTE] Release Maven Surefire plugin version 2.4.1
With a change as big as Surefire 2.4, there turned out to be a few bugs
still lurking.
We s
With a change as big as Surefire 2.4, there turned out to be a few bugs
still lurking.
We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&styleName=Html&version=14016
There are still 38 issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Carlos,
| great, but
| - who is going to enforce it?
Sorry, I can not tell. Of course this is not easy to do.
But you do have policies for your repository. It seems
that they are not enforced or not strong enough.
The best thing for a formal rule i
> /**
> * @parameter expression="${project.build.outputDirectory}"
>*/
> private File outputDirectory;
>and
> /**
>* @parameter default-value="${project.build.outputDirectory}"
>*/
> private File outputDirectory;
Interesting problem. I usually prefer to use the expression
Hello,
The generated site documentation for many mojo parameters lacks the nice
info "Default value is " in the parameter summary although the
parameter effectively has a default value. Take for instance the site for
the maven-resources-plugin and its "outputDirectory" parameter [0].
This effect
It is a known bug. Use
http://repo1.maven.org/maven2/javax/xml/ws/jaxws-api/2.1-1/ instead.
2008/1/26, Raymond Feng <[EMAIL PROTECTED]>:
> Hi,
>
> Our build has a dependency on javax.xml.ws:jaxws-api:2.1. And we have the
> java.net configured as a maven repo in our pom.xml. The build fails randoml
