You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by John Casey <jd...@commonjava.org> on 2009/03/09 17:00:13 UTC
[PLEASE TEST] Maven 2.1.0-RC1
Hi everyone,
I've rolled the first release candidate for Maven 2.1.0. It's available at:
http://tinyurl.com/maven-2-1-0-RC1
(https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
The staging repository root is at:
https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
If you have time, please take a look and see if you can break it!
BTW, the JIRA version notes for this release are at:
http://tinyurl.com/maven-2-1-0-jira
(http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587)
If we can't find anything wrong with this release candidate after maybe
four or five days at most, I'll call the vote for a release. Hopefully
we can coast in on the effort we put forth in the last release, at least
to some extent! :-)
Thanks,
-john
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Arnaud HERITIER <ah...@gmail.com>.
Now it passes and I didn't change my code :-(I have to test it a little bit
more to see if there's an issue or not.
On Mon, Mar 9, 2009 at 11:50 PM, Arnaud HERITIER <ah...@gmail.com>wrote:
> Hi,
> I tried to build the maven-eclipse-plugin with its integration tests but it
> fails.I'm opening an issue
> Everything is building fine with 2.0.10
>
> cheers
>
> Arnaud
>
>
>
> On Mon, Mar 9, 2009 at 5:00 PM, John Casey <jd...@commonjava.org> wrote:
>
>> Hi everyone,
>>
>> I've rolled the first release candidate for Maven 2.1.0. It's available
>> at:
>>
>> http://tinyurl.com/maven-2-1-0-RC1
>> (
>> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/
>> )
>>
>> The staging repository root is at:
>>
>>
>> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>>
>> If you have time, please take a look and see if you can break it!
>>
>> BTW, the JIRA version notes for this release are at:
>>
>> http://tinyurl.com/maven-2-1-0-jira
>> (
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587
>> )
>>
>> If we can't find anything wrong with this release candidate after maybe
>> four or five days at most, I'll call the vote for a release. Hopefully we
>> can coast in on the effort we put forth in the last release, at least to
>> some extent! :-)
>>
>> Thanks,
>>
>> -john
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> Arnaud
>
--
Arnaud
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Arnaud HERITIER <ah...@gmail.com>.
Hi,
I tried to build the maven-eclipse-plugin with its integration tests but it
fails.I'm opening an issue
Everything is building fine with 2.0.10
cheers
Arnaud
On Mon, Mar 9, 2009 at 5:00 PM, John Casey <jd...@commonjava.org> wrote:
> Hi everyone,
>
> I've rolled the first release candidate for Maven 2.1.0. It's available at:
>
> http://tinyurl.com/maven-2-1-0-RC1
> (
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/
> )
>
> The staging repository root is at:
>
>
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>
> If you have time, please take a look and see if you can break it!
>
> BTW, the JIRA version notes for this release are at:
>
> http://tinyurl.com/maven-2-1-0-jira
> (
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587
> )
>
> If we can't find anything wrong with this release candidate after maybe
> four or five days at most, I'll call the vote for a release. Hopefully we
> can coast in on the effort we put forth in the last release, at least to
> some extent! :-)
>
> Thanks,
>
> -john
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Arnaud
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Stephane Nicoll <st...@gmail.com>.
Working fine on our corporate builds (custom plugins & al).
Thanks,
Stéphane
On Mon, Mar 9, 2009 at 5:00 PM, John Casey <jd...@commonjava.org> wrote:
> Hi everyone,
>
> I've rolled the first release candidate for Maven 2.1.0. It's available at:
>
> http://tinyurl.com/maven-2-1-0-RC1
> (
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/
> )
>
> The staging repository root is at:
>
>
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>
> If you have time, please take a look and see if you can break it!
>
> BTW, the JIRA version notes for this release are at:
>
> http://tinyurl.com/maven-2-1-0-jira
> (
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587
> )
>
> If we can't find anything wrong with this release candidate after maybe
> four or five days at most, I'll call the vote for a release. Hopefully we
> can coast in on the effort we put forth in the last release, at least to
> some extent! :-)
>
> Thanks,
>
> -john
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Large Systems Suck: This rule is 100% transitive. If you build one, you
suck" -- S.Yegge
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Christian Edward Gruber <ch...@gmail.com>.
WFM
I just built tapestry5.0.x branch, plus a bunch of my own projects.
It seems to work just fine. Only one problem, which I think is a
selenium-on-Mac issue, not a maven one. I kept having to manually
kill firefox before it could continue.
Christian
On Mar 10, 2009, at 8:47 AM, Fabrice Bellingard wrote:
> Hi John,
>
> everything's building fine here! Great :-)
>
>
> - Fabrice
> bellingard@apache.org
>
>
> On Mon, Mar 9, 2009 at 5:00 PM, John Casey <jd...@commonjava.org>
> wrote:
>
>> Hi everyone,
>>
>> I've rolled the first release candidate for Maven 2.1.0. It's
>> available at:
>>
>> http://tinyurl.com/maven-2-1-0-RC1
>> (
>> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/
>> )
>>
>> The staging repository root is at:
>>
>>
>> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>>
>> If you have time, please take a look and see if you can break it!
>>
>> BTW, the JIRA version notes for this release are at:
>>
>> http://tinyurl.com/maven-2-1-0-jira
>> (
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587
>> )
>>
>> If we can't find anything wrong with this release candidate after
>> maybe
>> four or five days at most, I'll call the vote for a release.
>> Hopefully we
>> can coast in on the effort we put forth in the last release, at
>> least to
>> some extent! :-)
>>
>> Thanks,
>>
>> -john
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Fabrice Bellingard <be...@gmail.com>.
Hi John,
everything's building fine here! Great :-)
- Fabrice
bellingard@apache.org
On Mon, Mar 9, 2009 at 5:00 PM, John Casey <jd...@commonjava.org> wrote:
> Hi everyone,
>
> I've rolled the first release candidate for Maven 2.1.0. It's available at:
>
> http://tinyurl.com/maven-2-1-0-RC1
> (
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/
> )
>
> The staging repository root is at:
>
>
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>
> If you have time, please take a look and see if you can break it!
>
> BTW, the JIRA version notes for this release are at:
>
> http://tinyurl.com/maven-2-1-0-jira
> (
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587
> )
>
> If we can't find anything wrong with this release candidate after maybe
> four or five days at most, I'll call the vote for a release. Hopefully we
> can coast in on the effort we put forth in the last release, at least to
> some extent! :-)
>
> Thanks,
>
> -john
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Re : Re : [PLEASE TEST] Maven 2.1.0-RC1
Posted by John Casey <jd...@commonjava.org>.
FWIW, 2.1.0-RC* aren't releases, so we don't need them reflected in
JIRA. We can set Affected Version == Fix-For Version == 2.1.0 for these
issues.
Thanks,
-john
Julien HENRY wrote:
> Hi John,
>
> I've submitted MNG-4079. Tell me if you need additional informations.
>
> Thanks for the good job!
>
> Julien
>
>
>
> ----- Message d'origine ----
> De : John Casey <jd...@commonjava.org>
> À : Maven Developers List <de...@maven.apache.org>
> Envoyé le : Mardi, 10 Mars 2009, 17h15mn 49s
> Objet : Re: Re : [PLEASE TEST] Maven 2.1.0-RC1
>
> Could you file that in JIRA, and I'll take a look? If possible, please include the -e option so I can try to figure out where the different traces are being produced...it *might* be difficult to trace.
>
> -john
>
> Julien HENRY wrote:
>> Works fine and quickly, but here is a small question. In case of error, is it possible to avoid duplication of the error message?
>>
>> Example:
>> [ERROR] BUILD FAILURE
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Compilation failure
>> Failure executing javac, but could not parse the error:
>> javac: invalid target release: 1.5
>> Usage: javac <options> <source files>
>> where possible options include:
>> -g Generate all debugging info
>> -g:none Generate no debugging info
>> -g:{lines,vars,source} Generate only some debugging info
>> -nowarn Generate no warnings
>> -verbose Output messages about what the compiler is doing
>> -deprecation Output source locations where deprecated APIs are used
>> -classpath <path> Specify where to find user class files
>> -sourcepath <path> Specify where to find input source files
>> -bootclasspath <path> Override location of bootstrap class files
>> -extdirs <dirs> Override location of installed extensions
>> -d <directory> Specify where to place generated class files
>> -encoding <encoding> Specify character encoding used by source files
>> -source <release> Provide source compatibility with specified release
>> -target <release> Generate class files for specific VM version
>> -help Print a synopsis of standard options
>>
>>
>>
>>
>> Failure executing javac, but could not parse the error:
>> javac: invalid target release: 1.5
>> Usage: javac <options> <source files>
>> where possible options include:
>> -g Generate all debugging info
>> -g:none Generate no debugging info
>> -g:{lines,vars,source} Generate only some debugging info
>> -nowarn Generate no warnings
>> -verbose Output messages about what the compiler is doing
>> -deprecation Output source locations where deprecated APIs are used
>> -classpath <path> Specify where to find user class files
>> -sourcepath <path> Specify where to find input source files
>> -bootclasspath <path> Override location of bootstrap class files
>> -extdirs <dirs> Override location of installed extensions
>> -d <directory> Specify where to place generated class files
>> -encoding <encoding> Specify character encoding used by source files
>> -source <release> Provide source compatibility with specified release
>> -target <release> Generate class files for specific VM version
>> -help Print a synopsis of standard options
>>
>>
>>
>> [INFO] ------------------------------------------------------------------------
>>
>>
>>
>>
>> ----- Message d'origine ----
>> De : John Casey <jd...@commonjava.org>
>> À : Maven Developers List <de...@maven.apache.org>
>> Envoyé le : Lundi, 9 Mars 2009, 17h00mn 13s
>> Objet : [PLEASE TEST] Maven 2.1.0-RC1
>>
>> Hi everyone,
>>
>> I've rolled the first release candidate for Maven 2.1.0. It's available at:
>>
>> http://tinyurl.com/maven-2-1-0-RC1
>> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
>>
>> The staging repository root is at:
>>
>> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>>
>> If you have time, please take a look and see if you can break it!
>>
>> BTW, the JIRA version notes for this release are at:
>>
>> http://tinyurl..com/maven-2-1-0-jira
>> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587)
>>
>> If we can't find anything wrong with this release candidate after maybe four or five days at most, I'll call the vote for a release. Hopefully we can coast in on the effort we put forth in the last release, at least to some extent! :-)
>>
>> Thanks,
>>
>> -john
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re : Re : [PLEASE TEST] Maven 2.1.0-RC1
Posted by Julien HENRY <he...@yahoo.fr>.
Hi John,
I've submitted MNG-4079. Tell me if you need additional informations.
Thanks for the good job!
Julien
----- Message d'origine ----
De : John Casey <jd...@commonjava.org>
À : Maven Developers List <de...@maven.apache.org>
Envoyé le : Mardi, 10 Mars 2009, 17h15mn 49s
Objet : Re: Re : [PLEASE TEST] Maven 2.1.0-RC1
Could you file that in JIRA, and I'll take a look? If possible, please include the -e option so I can try to figure out where the different traces are being produced...it *might* be difficult to trace.
-john
Julien HENRY wrote:
> Works fine and quickly, but here is a small question. In case of error, is it possible to avoid duplication of the error message?
>
> Example:
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Compilation failure
> Failure executing javac, but could not parse the error:
> javac: invalid target release: 1.5
> Usage: javac <options> <source files>
> where possible options include:
> -g Generate all debugging info
> -g:none Generate no debugging info
> -g:{lines,vars,source} Generate only some debugging info
> -nowarn Generate no warnings
> -verbose Output messages about what the compiler is doing
> -deprecation Output source locations where deprecated APIs are used
> -classpath <path> Specify where to find user class files
> -sourcepath <path> Specify where to find input source files
> -bootclasspath <path> Override location of bootstrap class files
> -extdirs <dirs> Override location of installed extensions
> -d <directory> Specify where to place generated class files
> -encoding <encoding> Specify character encoding used by source files
> -source <release> Provide source compatibility with specified release
> -target <release> Generate class files for specific VM version
> -help Print a synopsis of standard options
>
>
>
>
> Failure executing javac, but could not parse the error:
> javac: invalid target release: 1.5
> Usage: javac <options> <source files>
> where possible options include:
> -g Generate all debugging info
> -g:none Generate no debugging info
> -g:{lines,vars,source} Generate only some debugging info
> -nowarn Generate no warnings
> -verbose Output messages about what the compiler is doing
> -deprecation Output source locations where deprecated APIs are used
> -classpath <path> Specify where to find user class files
> -sourcepath <path> Specify where to find input source files
> -bootclasspath <path> Override location of bootstrap class files
> -extdirs <dirs> Override location of installed extensions
> -d <directory> Specify where to place generated class files
> -encoding <encoding> Specify character encoding used by source files
> -source <release> Provide source compatibility with specified release
> -target <release> Generate class files for specific VM version
> -help Print a synopsis of standard options
>
>
>
> [INFO] ------------------------------------------------------------------------
>
>
>
>
> ----- Message d'origine ----
> De : John Casey <jd...@commonjava.org>
> À : Maven Developers List <de...@maven.apache.org>
> Envoyé le : Lundi, 9 Mars 2009, 17h00mn 13s
> Objet : [PLEASE TEST] Maven 2.1.0-RC1
>
> Hi everyone,
>
> I've rolled the first release candidate for Maven 2.1.0. It's available at:
>
> http://tinyurl.com/maven-2-1-0-RC1
> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
>
> The staging repository root is at:
>
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>
> If you have time, please take a look and see if you can break it!
>
> BTW, the JIRA version notes for this release are at:
>
> http://tinyurl..com/maven-2-1-0-jira
> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587)
>
> If we can't find anything wrong with this release candidate after maybe four or five days at most, I'll call the vote for a release. Hopefully we can coast in on the effort we put forth in the last release, at least to some extent! :-)
>
> Thanks,
>
> -john
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Re : [PLEASE TEST] Maven 2.1.0-RC1
Posted by John Casey <jd...@commonjava.org>.
Could you file that in JIRA, and I'll take a look? If possible, please
include the -e option so I can try to figure out where the different
traces are being produced...it *might* be difficult to trace.
-john
Julien HENRY wrote:
> Works fine and quickly, but here is a small question. In case of error, is it possible to avoid duplication of the error message?
>
> Example:
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Compilation failure
> Failure executing javac, but could not parse the error:
> javac: invalid target release: 1.5
> Usage: javac <options> <source files>
> where possible options include:
> -g Generate all debugging info
> -g:none Generate no debugging info
> -g:{lines,vars,source} Generate only some debugging info
> -nowarn Generate no warnings
> -verbose Output messages about what the compiler is doing
> -deprecation Output source locations where deprecated APIs are used
> -classpath <path> Specify where to find user class files
> -sourcepath <path> Specify where to find input source files
> -bootclasspath <path> Override location of bootstrap class files
> -extdirs <dirs> Override location of installed extensions
> -d <directory> Specify where to place generated class files
> -encoding <encoding> Specify character encoding used by source files
> -source <release> Provide source compatibility with specified release
> -target <release> Generate class files for specific VM version
> -help Print a synopsis of standard options
>
>
>
>
> Failure executing javac, but could not parse the error:
> javac: invalid target release: 1.5
> Usage: javac <options> <source files>
> where possible options include:
> -g Generate all debugging info
> -g:none Generate no debugging info
> -g:{lines,vars,source} Generate only some debugging info
> -nowarn Generate no warnings
> -verbose Output messages about what the compiler is doing
> -deprecation Output source locations where deprecated APIs are used
> -classpath <path> Specify where to find user class files
> -sourcepath <path> Specify where to find input source files
> -bootclasspath <path> Override location of bootstrap class files
> -extdirs <dirs> Override location of installed extensions
> -d <directory> Specify where to place generated class files
> -encoding <encoding> Specify character encoding used by source files
> -source <release> Provide source compatibility with specified release
> -target <release> Generate class files for specific VM version
> -help Print a synopsis of standard options
>
>
>
> [INFO] ------------------------------------------------------------------------
>
>
>
>
> ----- Message d'origine ----
> De : John Casey <jd...@commonjava.org>
> À : Maven Developers List <de...@maven.apache.org>
> Envoyé le : Lundi, 9 Mars 2009, 17h00mn 13s
> Objet : [PLEASE TEST] Maven 2.1.0-RC1
>
> Hi everyone,
>
> I've rolled the first release candidate for Maven 2.1.0. It's available at:
>
> http://tinyurl.com/maven-2-1-0-RC1
> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
>
> The staging repository root is at:
>
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>
> If you have time, please take a look and see if you can break it!
>
> BTW, the JIRA version notes for this release are at:
>
> http://tinyurl..com/maven-2-1-0-jira
> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587)
>
> If we can't find anything wrong with this release candidate after maybe four or five days at most, I'll call the vote for a release. Hopefully we can coast in on the effort we put forth in the last release, at least to some extent! :-)
>
> Thanks,
>
> -john
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re : [PLEASE TEST] Maven 2.1.0-RC1
Posted by Julien HENRY <he...@yahoo.fr>.
Works fine and quickly, but here is a small question. In case of error, is it possible to avoid duplication of the error message?
Example:
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
Failure executing javac, but could not parse the error:
javac: invalid target release: 1.5
Usage: javac <options> <source files>
where possible options include:
-g Generate all debugging info
-g:none Generate no debugging info
-g:{lines,vars,source} Generate only some debugging info
-nowarn Generate no warnings
-verbose Output messages about what the compiler is doing
-deprecation Output source locations where deprecated APIs are used
-classpath <path> Specify where to find user class files
-sourcepath <path> Specify where to find input source files
-bootclasspath <path> Override location of bootstrap class files
-extdirs <dirs> Override location of installed extensions
-d <directory> Specify where to place generated class files
-encoding <encoding> Specify character encoding used by source files
-source <release> Provide source compatibility with specified release
-target <release> Generate class files for specific VM version
-help Print a synopsis of standard options
Failure executing javac, but could not parse the error:
javac: invalid target release: 1.5
Usage: javac <options> <source files>
where possible options include:
-g Generate all debugging info
-g:none Generate no debugging info
-g:{lines,vars,source} Generate only some debugging info
-nowarn Generate no warnings
-verbose Output messages about what the compiler is doing
-deprecation Output source locations where deprecated APIs are used
-classpath <path> Specify where to find user class files
-sourcepath <path> Specify where to find input source files
-bootclasspath <path> Override location of bootstrap class files
-extdirs <dirs> Override location of installed extensions
-d <directory> Specify where to place generated class files
-encoding <encoding> Specify character encoding used by source files
-source <release> Provide source compatibility with specified release
-target <release> Generate class files for specific VM version
-help Print a synopsis of standard options
[INFO] ------------------------------------------------------------------------
----- Message d'origine ----
De : John Casey <jd...@commonjava.org>
À : Maven Developers List <de...@maven.apache.org>
Envoyé le : Lundi, 9 Mars 2009, 17h00mn 13s
Objet : [PLEASE TEST] Maven 2.1.0-RC1
Hi everyone,
I've rolled the first release candidate for Maven 2.1.0. It's available at:
http://tinyurl.com/maven-2-1-0-RC1
(https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
The staging repository root is at:
https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
If you have time, please take a look and see if you can break it!
BTW, the JIRA version notes for this release are at:
http://tinyurl..com/maven-2-1-0-jira
(http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587)
If we can't find anything wrong with this release candidate after maybe four or five days at most, I'll call the vote for a release. Hopefully we can coast in on the effort we put forth in the last release, at least to some extent! :-)
Thanks,
-john
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Christian Edward Gruber <ch...@gmail.com>.
And tapestry trunk is building nicely.
Christian.
Oh, MacBook Pro with 2G RAM, Java 1.5
On Mar 9, 2009, at 12:00 PM, John Casey wrote:
> Hi everyone,
>
> I've rolled the first release candidate for Maven 2.1.0. It's
> available at:
>
> http://tinyurl.com/maven-2-1-0-RC1
> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/
> )
>
> The staging repository root is at:
>
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>
> If you have time, please take a look and see if you can break it!
>
> BTW, the JIRA version notes for this release are at:
>
> http://tinyurl.com/maven-2-1-0-jira
> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587
> )
>
> If we can't find anything wrong with this release candidate after
> maybe four or five days at most, I'll call the vote for a release.
> Hopefully we can coast in on the effort we put forth in the last
> release, at least to some extent! :-)
>
> Thanks,
>
> -john
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Petar Tahchiev <pa...@gmail.com>.
Hi John,
here are my results:
- Cactus buils fine.
- Cargo builds fine.
- Felix builds fine.
Cheers, Petar.
2009/3/10 Paul <pa...@nosphere.org>
> Everything is working nicely with this rc at my shop (lots of projects,
> lots
> of plugins several being custom ones etc...).
>
> I do get warnings about non activated profiles and the build is quicker,
> especially regarding artifact download.
>
> /Paul
>
>
--
Regards, Petar!
Karlovo, Bulgaria.
- - - - - - - -
| Author @ Manning Publications.
| Senior Solution Architect @ Unic
| BGJUG-Bulgarian Java User Group Leader.
| Apache Maven Developer.
| Apache Jakarta PMC member.
| Jakarta Cactus Lead Developer.
| Codehaus Plexus Developer
| Blogger: http://weblogs.java.net/blog/paranoiabla/
- - - - - - - -
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Paul <pa...@nosphere.org>.
Everything is working nicely with this rc at my shop (lots of projects, lots
of plugins several being custom ones etc...).
I do get warnings about non activated profiles and the build is quicker,
especially regarding artifact download.
/Paul
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Jorg Heymans <jo...@gmail.com>.
On Mon, Mar 9, 2009 at 5:00 PM, John Casey <jd...@commonjava.org> wrote:
> Hi everyone,
>
> I've rolled the first release candidate for Maven 2.1.0. It's available at:
>
> http://tinyurl.com/maven-2-1-0-RC1
> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
Works fine (and a tad bit faster) for my project builds. FWIW I don't
see any of the [WARNING] messages Daniel is seeing.
Regards,
Jorg Heymans
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Brett Porter <br...@apache.org>.
On 12/03/2009, at 2:22 AM, John Casey wrote:
> Mistake on my part. I realized it when I started working on the
> bugfixes described in this thread. Sorry for the confusion. I'll
> amend the tag, too, if you want...just so it's not sitting out there
> as 2.1.0.
I don't think that matters too much, as long as each RC isn't the
same, since that'll get confusing :)
- Brett
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Christian Edward Gruber <ch...@gmail.com>.
Please. 2.1.0-RC1 is ideal. Most people will interpret a 2.1.0 as a
release.
Christian
On Mar 11, 2009, at 11:45 AM, Brian E. Fox wrote:
> I would change the tag.
>
> -----Original Message-----
> From: John Casey [mailto:jdcasey@commonjava.org]
> Sent: Wednesday, March 11, 2009 8:22 AM
> To: Maven Developers List
> Subject: Re: [PLEASE TEST] Maven 2.1.0-RC1
>
> Mistake on my part. I realized it when I started working on the
> bugfixes
>
> described in this thread. Sorry for the confusion. I'll amend the tag,
> too, if you want...just so it's not sitting out there as 2.1.0.
>
> -john
>
> Brett Porter wrote:
>> Just been generally using it and no additional problems.
>>
>> Just curious - why 2.1.0 in the version that was released instead of
>> 2.1.0-RC1? Though we now have the SVN Rev # in there, it could prove
>> confusing for anyone that holds on to it.
>>
>> Cheers,
>> Brett
>>
>> On 10/03/2009, at 3:00 AM, John Casey wrote:
>>
>>> Hi everyone,
>>>
>>> I've rolled the first release candidate for Maven 2.1.0. It's
>>> available at:
>>>
>>> http://tinyurl.com/maven-2-1-0-RC1
>>>
> (https://repository.apache.org/content/repositories/maven-staging-4e4fa4
> 8c70323f/org/apache/maven/apache-maven/2.1.0/)
>>>
>>>
>>> The staging repository root is at:
>>>
>>>
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48
> c70323f
>>>
>>>
>>> If you have time, please take a look and see if you can break it!
>>>
>>> BTW, the JIRA version notes for this release are at:
>>>
>>> http://tinyurl.com/maven-2-1-0-jira
>>>
> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleN
> ame=Html&version=14587)
>>>
>>>
>>> If we can't find anything wrong with this release candidate after
>>> maybe four or five days at most, I'll call the vote for a release.
>>> Hopefully we can coast in on the effort we put forth in the last
>>> release, at least to some extent! :-)
>>>
>>> Thanks,
>>>
>>> -john
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://blogs.exist.com/bporter/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [PLEASE TEST] Maven 2.1.0-RC1
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
I would change the tag.
-----Original Message-----
From: John Casey [mailto:jdcasey@commonjava.org]
Sent: Wednesday, March 11, 2009 8:22 AM
To: Maven Developers List
Subject: Re: [PLEASE TEST] Maven 2.1.0-RC1
Mistake on my part. I realized it when I started working on the bugfixes
described in this thread. Sorry for the confusion. I'll amend the tag,
too, if you want...just so it's not sitting out there as 2.1.0.
-john
Brett Porter wrote:
> Just been generally using it and no additional problems.
>
> Just curious - why 2.1.0 in the version that was released instead of
> 2.1.0-RC1? Though we now have the SVN Rev # in there, it could prove
> confusing for anyone that holds on to it.
>
> Cheers,
> Brett
>
> On 10/03/2009, at 3:00 AM, John Casey wrote:
>
>> Hi everyone,
>>
>> I've rolled the first release candidate for Maven 2.1.0. It's
>> available at:
>>
>> http://tinyurl.com/maven-2-1-0-RC1
>>
(https://repository.apache.org/content/repositories/maven-staging-4e4fa4
8c70323f/org/apache/maven/apache-maven/2.1.0/)
>>
>>
>> The staging repository root is at:
>>
>>
https://repository.apache.org/content/repositories/maven-staging-4e4fa48
c70323f
>>
>>
>> If you have time, please take a look and see if you can break it!
>>
>> BTW, the JIRA version notes for this release are at:
>>
>> http://tinyurl.com/maven-2-1-0-jira
>>
(http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleN
ame=Html&version=14587)
>>
>>
>> If we can't find anything wrong with this release candidate after
>> maybe four or five days at most, I'll call the vote for a release.
>> Hopefully we can coast in on the effort we put forth in the last
>> release, at least to some extent! :-)
>>
>> Thanks,
>>
>> -john
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by John Casey <jd...@commonjava.org>.
Mistake on my part. I realized it when I started working on the bugfixes
described in this thread. Sorry for the confusion. I'll amend the tag,
too, if you want...just so it's not sitting out there as 2.1.0.
-john
Brett Porter wrote:
> Just been generally using it and no additional problems.
>
> Just curious - why 2.1.0 in the version that was released instead of
> 2.1.0-RC1? Though we now have the SVN Rev # in there, it could prove
> confusing for anyone that holds on to it.
>
> Cheers,
> Brett
>
> On 10/03/2009, at 3:00 AM, John Casey wrote:
>
>> Hi everyone,
>>
>> I've rolled the first release candidate for Maven 2.1.0. It's
>> available at:
>>
>> http://tinyurl.com/maven-2-1-0-RC1
>> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
>>
>>
>> The staging repository root is at:
>>
>> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>>
>>
>> If you have time, please take a look and see if you can break it!
>>
>> BTW, the JIRA version notes for this release are at:
>>
>> http://tinyurl.com/maven-2-1-0-jira
>> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587)
>>
>>
>> If we can't find anything wrong with this release candidate after
>> maybe four or five days at most, I'll call the vote for a release.
>> Hopefully we can coast in on the effort we put forth in the last
>> release, at least to some extent! :-)
>>
>> Thanks,
>>
>> -john
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> --
> Brett Porter
> brett@apache.org
> http://blogs.exist.com/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Brett Porter <br...@apache.org>.
Just been generally using it and no additional problems.
Just curious - why 2.1.0 in the version that was released instead of
2.1.0-RC1? Though we now have the SVN Rev # in there, it could prove
confusing for anyone that holds on to it.
Cheers,
Brett
On 10/03/2009, at 3:00 AM, John Casey wrote:
> Hi everyone,
>
> I've rolled the first release candidate for Maven 2.1.0. It's
> available at:
>
> http://tinyurl.com/maven-2-1-0-RC1
> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/
> )
>
> The staging repository root is at:
>
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>
> If you have time, please take a look and see if you can break it!
>
> BTW, the JIRA version notes for this release are at:
>
> http://tinyurl.com/maven-2-1-0-jira
> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587
> )
>
> If we can't find anything wrong with this release candidate after
> maybe four or five days at most, I'll call the vote for a release.
> Hopefully we can coast in on the effort we put forth in the last
> release, at least to some extent! :-)
>
> Thanks,
>
> -john
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Mark Hobson <ma...@gmail.com>.
2009/3/11 Brett Porter <br...@apache.org>:
> I wouldn't think so. Can you file it as an issue (probably not a blocker...)
Done: http://jira.codehaus.org/browse/MNG-4082
> Yep, definitely, though be aware they won't work with older versions of
> Maven if you intend to switch.
>
> http://maven.apache.org/guides/mini/guide-encryption.html
Thanks, I'll try to have a go sometime.
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Brett Porter <br...@apache.org>.
On 11/03/2009, at 10:24 PM, Mark Hobson wrote:
> 2009/3/11 Brett Porter <br...@apache.org>:
>> It looks like this occurs when a password matches the definition of
>> an
>> encrpyted password (I believe anything wrapped in { ... }), and you
>> do not
>> have a master password configured. I'll improve the error message.
>>
>> Did you already have a password like this, or were you testing the
>> encrypted
>> passwords before?
>
> Ah ha, that'll be the curly braces in my password then. Note that the
> password doesn't start and end with curly braces, so should it have
> even been picked up?
I wouldn't think so. Can you file it as an issue (probably not a
blocker...)
>
> Can I work around this by using encrypted passwords? Any pointers to
> docs would be appreciated.
Yep, definitely, though be aware they won't work with older versions
of Maven if you intend to switch.
http://maven.apache.org/guides/mini/guide-encryption.html
Cheers,
Brett
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Mark Hobson <ma...@gmail.com>.
2009/3/11 Brett Porter <br...@apache.org>:
> It looks like this occurs when a password matches the definition of an
> encrpyted password (I believe anything wrapped in { ... }), and you do not
> have a master password configured. I'll improve the error message.
>
> Did you already have a password like this, or were you testing the encrypted
> passwords before?
Ah ha, that'll be the curly braces in my password then. Note that the
password doesn't start and end with curly braces, so should it have
even been picked up?
Can I work around this by using encrypted passwords? Any pointers to
docs would be appreciated.
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Brett Porter <br...@apache.org>.
It looks like this occurs when a password matches the definition of an
encrpyted password (I believe anything wrapped in { ... }), and you do
not have a master password configured. I'll improve the error message.
Did you already have a password like this, or were you testing the
encrypted passwords before?
Cheers,
Brett
On 11/03/2009, at 9:31 PM, Mark Hobson wrote:
> Just tried upgrading from 2.0.10 and get this:
>
> [mark@mark]$ mvn clean install
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to configure Maven for execution
> org.sonatype.plexus.components.sec.dispatcher.SecDispatcherException:
> java.io.FileNotFoundException: C:\Documents and
> Settings\mark\.m2\settings-security.xml (The system cannot find the
> file specified)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Unable to configure
> Maven for execution
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
> 289)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun
> .reflect
> .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun
> .reflect
> .DelegatingMethodAccessorImpl
> .invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.SettingsConfigurationException:
> org.sonatype.plexus.components.sec.dispatcher.SecDispatcherException:
> java.io.FileNotFoundException: C:\Documents and
> Settings\mark\.m2\settings-security.xml (The system cannot find the
> file specified)
> at
> org.apache.maven.DefaultMaven.resolveParameters(DefaultMaven.java:756)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
> 277)
> ... 10 more
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: < 1 second
> [INFO] Finished at: Wed Mar 11 10:29:14 GMT 2009
> [INFO] Final Memory: 1M/2M
> [INFO]
> ------------------------------------------------------------------------
>
> Should it really bomb if settings-security.xml is missing? Is there
> any doc regarding this config file?
>
> Mark
>
> 2009/3/11 Paul Gier <pg...@redhat.com>:
>> Seems to work fine for the JBoss app server :)
>>
>> John Casey wrote:
>>>
>>> Hi everyone,
>>>
>>> I've rolled the first release candidate for Maven 2.1.0. It's
>>> available
>>> at:
>>>
>>> http://tinyurl.com/maven-2-1-0-RC1
>>>
>>> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/
>>> )
>>>
>>> The staging repository root is at:
>>>
>>>
>>> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>>>
>>> If you have time, please take a look and see if you can break it!
>>>
>>> BTW, the JIRA version notes for this release are at:
>>>
>>> http://tinyurl.com/maven-2-1-0-jira
>>>
>>> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587
>>> )
>>>
>>> If we can't find anything wrong with this release candidate after
>>> maybe
>>> four or five days at most, I'll call the vote for a release.
>>> Hopefully we
>>> can coast in on the effort we put forth in the last release, at
>>> least to
>>> some extent! :-)
>>>
>>> Thanks,
>>>
>>> -john
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Mark Hobson <ma...@gmail.com>.
Just tried upgrading from 2.0.10 and get this:
[mark@mark]$ mvn clean install
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Unable to configure Maven for execution
org.sonatype.plexus.components.sec.dispatcher.SecDispatcherException:
java.io.FileNotFoundException: C:\Documents and
Settings\mark\.m2\settings-security.xml (The system cannot find the
file specified)
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Unable to configure
Maven for execution
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:289)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:136)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.SettingsConfigurationException:
org.sonatype.plexus.components.sec.dispatcher.SecDispatcherException:
java.io.FileNotFoundException: C:\Documents and
Settings\mark\.m2\settings-security.xml (The system cannot find the
file specified)
at org.apache.maven.DefaultMaven.resolveParameters(DefaultMaven.java:756)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:277)
... 10 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Wed Mar 11 10:29:14 GMT 2009
[INFO] Final Memory: 1M/2M
[INFO] ------------------------------------------------------------------------
Should it really bomb if settings-security.xml is missing? Is there
any doc regarding this config file?
Mark
2009/3/11 Paul Gier <pg...@redhat.com>:
> Seems to work fine for the JBoss app server :)
>
> John Casey wrote:
>>
>> Hi everyone,
>>
>> I've rolled the first release candidate for Maven 2.1.0. It's available
>> at:
>>
>> http://tinyurl.com/maven-2-1-0-RC1
>>
>> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
>>
>> The staging repository root is at:
>>
>>
>> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>>
>> If you have time, please take a look and see if you can break it!
>>
>> BTW, the JIRA version notes for this release are at:
>>
>> http://tinyurl.com/maven-2-1-0-jira
>>
>> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587)
>>
>> If we can't find anything wrong with this release candidate after maybe
>> four or five days at most, I'll call the vote for a release. Hopefully we
>> can coast in on the effort we put forth in the last release, at least to
>> some extent! :-)
>>
>> Thanks,
>>
>> -john
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Paul Gier <pg...@redhat.com>.
Seems to work fine for the JBoss app server :)
John Casey wrote:
> Hi everyone,
>
> I've rolled the first release candidate for Maven 2.1.0. It's available at:
>
> http://tinyurl.com/maven-2-1-0-RC1
> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
>
>
> The staging repository root is at:
>
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>
>
> If you have time, please take a look and see if you can break it!
>
> BTW, the JIRA version notes for this release are at:
>
> http://tinyurl.com/maven-2-1-0-jira
> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587)
>
>
> If we can't find anything wrong with this release candidate after maybe
> four or five days at most, I'll call the vote for a release. Hopefully
> we can coast in on the effort we put forth in the last release, at least
> to some extent! :-)
>
> Thanks,
>
> -john
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Daniel Kulp <dk...@apache.org>.
I'm playing around with this a bit. It's definitely faster than 2.0.10 for
my "fastinstall" cases. From 36 seconds down to 27 seconds. That's good.
However, with "mvn clean", I'm getting a LOT of warning spit out:
NOTE: You may need to run this build to the 'compile' lifecycle phase, or
farther, in order to build the dependency artifact.
[WARNING] A dependency of the current project (or of one the plugins used in
its build) was found in the reactor, but had not been built at the time it
was requested. It will be resolved from the repository instead.
That's definitely disconcerting to the users. Could they get toned down to
DEBUG level or something?
I also ran into a failure with CXF. With a trunk checkout of CXF, if I run:
mvn -Psetup.eclipse
to setup the eclipse stuff, I get:
[INFO] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='org.apache.cxf:cxf'}' and 'Vertex{label='org.apache.cxf:cxf-
buildtools'}' introduces to cycle in the graph org.apache.cxf:cxf-buildtools
--> org.apache.cxf:cxf --> org.apache.cxf:cxf-buildtools
which doesn't occur with 2.0.x.
Dan
On Mon March 9 2009 12:00:13 pm John Casey wrote:
> Hi everyone,
>
> I've rolled the first release candidate for Maven 2.1.0. It's available at:
>
> http://tinyurl.com/maven-2-1-0-RC1
> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c7
>0323f/org/apache/maven/apache-maven/2.1.0/)
>
> The staging repository root is at:
>
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70
>323f
>
> If you have time, please take a look and see if you can break it!
>
> BTW, the JIRA version notes for this release are at:
>
> http://tinyurl.com/maven-2-1-0-jira
> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName
>=Html&version=14587)
>
> If we can't find anything wrong with this release candidate after maybe
> four or five days at most, I'll call the vote for a release. Hopefully
> we can coast in on the effort we put forth in the last release, at least
> to some extent! :-)
>
> Thanks,
>
> -john
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Olivier Lamy <ol...@apache.org>.
Here the fault : http://repo1.maven.org/maven2/bcel/bcel/5.1/bcel-5.1.pom
--
Olivier
2009/3/11 John Casey <jd...@commonjava.org>:
> Could it be that the gwt-maven-plugin has a block that looks like this:
>
> <dependencies>
> <groupId>blah</groupId>
> ...
>
> It looks like a groupId nested immediately inside the dependencies
> collection element...that would be an invalid structure.
>
> -john
>
> Olivier Lamy wrote:
>>
>> Hi,
>> No issue here with company builds.
>>
>> But I can't build the gwt-maven-plugin
>> (https://svn.codehaus.org/mojo/trunk/mojo/gwt-maven-plugin)
>> mvn clean install -Prun-its
>>
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Failed to install project dependencies: MavenProject:
>> org.codehaus.mojo:gwt-maven-plugin:1.1-SNAPSHOT @
>> /local/olamy/open-source/mojo/gwt-maven-plugin/pom.xml
>>
>> Embedded error: Failed to install artifact: bcel:bcel:pom:5.1
>> Unrecognised association: 'groupId' (position: START_TAG seen
>> ...<dependencies>\n <groupId>... @7:14)
>>
>>
>> --
>> Olivier
>>
>> 2009/3/9 John Casey <jd...@commonjava.org>:
>>>
>>> Hi everyone,
>>>
>>> I've rolled the first release candidate for Maven 2.1.0. It's available
>>> at:
>>>
>>> http://tinyurl.com/maven-2-1-0-RC1
>>>
>>> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
>>>
>>> The staging repository root is at:
>>>
>>>
>>> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>>>
>>> If you have time, please take a look and see if you can break it!
>>>
>>> BTW, the JIRA version notes for this release are at:
>>>
>>> http://tinyurl.com/maven-2-1-0-jira
>>>
>>> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587)
>>>
>>> If we can't find anything wrong with this release candidate after maybe
>>> four
>>> or five days at most, I'll call the vote for a release. Hopefully we can
>>> coast in on the effort we put forth in the last release, at least to some
>>> extent! :-)
>>>
>>> Thanks,
>>>
>>> -john
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by John Casey <jd...@commonjava.org>.
Could it be that the gwt-maven-plugin has a block that looks like this:
<dependencies>
<groupId>blah</groupId>
...
It looks like a groupId nested immediately inside the dependencies
collection element...that would be an invalid structure.
-john
Olivier Lamy wrote:
> Hi,
> No issue here with company builds.
>
> But I can't build the gwt-maven-plugin
> (https://svn.codehaus.org/mojo/trunk/mojo/gwt-maven-plugin)
> mvn clean install -Prun-its
>
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to install project dependencies: MavenProject:
> org.codehaus.mojo:gwt-maven-plugin:1.1-SNAPSHOT @
> /local/olamy/open-source/mojo/gwt-maven-plugin/pom.xml
>
> Embedded error: Failed to install artifact: bcel:bcel:pom:5.1
> Unrecognised association: 'groupId' (position: START_TAG seen
> ...<dependencies>\n <groupId>... @7:14)
>
>
> --
> Olivier
>
> 2009/3/9 John Casey <jd...@commonjava.org>:
>> Hi everyone,
>>
>> I've rolled the first release candidate for Maven 2.1.0. It's available at:
>>
>> http://tinyurl.com/maven-2-1-0-RC1
>> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
>>
>> The staging repository root is at:
>>
>> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>>
>> If you have time, please take a look and see if you can break it!
>>
>> BTW, the JIRA version notes for this release are at:
>>
>> http://tinyurl.com/maven-2-1-0-jira
>> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587)
>>
>> If we can't find anything wrong with this release candidate after maybe four
>> or five days at most, I'll call the vote for a release. Hopefully we can
>> coast in on the effort we put forth in the last release, at least to some
>> extent! :-)
>>
>> Thanks,
>>
>> -john
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Maven 2.1.0-RC1
Posted by Olivier Lamy <ol...@apache.org>.
Hi,
No issue here with company builds.
But I can't build the gwt-maven-plugin
(https://svn.codehaus.org/mojo/trunk/mojo/gwt-maven-plugin)
mvn clean install -Prun-its
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to install project dependencies: MavenProject:
org.codehaus.mojo:gwt-maven-plugin:1.1-SNAPSHOT @
/local/olamy/open-source/mojo/gwt-maven-plugin/pom.xml
Embedded error: Failed to install artifact: bcel:bcel:pom:5.1
Unrecognised association: 'groupId' (position: START_TAG seen
...<dependencies>\n <groupId>... @7:14)
--
Olivier
2009/3/9 John Casey <jd...@commonjava.org>:
> Hi everyone,
>
> I've rolled the first release candidate for Maven 2.1.0. It's available at:
>
> http://tinyurl.com/maven-2-1-0-RC1
> (https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f/org/apache/maven/apache-maven/2.1.0/)
>
> The staging repository root is at:
>
> https://repository.apache.org/content/repositories/maven-staging-4e4fa48c70323f
>
> If you have time, please take a look and see if you can break it!
>
> BTW, the JIRA version notes for this release are at:
>
> http://tinyurl.com/maven-2-1-0-jira
> (http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=14587)
>
> If we can't find anything wrong with this release candidate after maybe four
> or five days at most, I'll call the vote for a release. Hopefully we can
> coast in on the effort we put forth in the last release, at least to some
> extent! :-)
>
> Thanks,
>
> -john
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org