You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Benjamin Bentmann <be...@udo.edu> on 2010/09/26 18:24:30 UTC
[PLEASE TEST] Apache Maven 3.0-RC3
Hi,
in preparation for the release of Apache Maven 3.0, the Maven team is
seeking your help to discover regressions since Maven 2.x. Everybody
interested in taking a preview of the upcoming release for a test drive
can get source and binary bundles from this URL:
https://repository.apache.org/content/repositories/maven-014/org/apache/maven/apache-maven/3.0-RC3/
Before reporting any issues found during testing, please be sure to have
a close look at the compatibility notes for Maven 3.x:
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes
If you encounter unexpected build issues, please fill a report in JIRA
that provides sufficient information to reproduce and analyze the issue:
http://jira.codehaus.org/browse/MNG
The fixes contained in this release candidate since the 3.0-beta-3
release and the previous release candidates can be seen in JIRA:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
Thanks,
-The Maven team
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Baptiste MATHUS <ml...@batmat.net>.
Well, I agree that it's basically not a maven specific issue, but the thing
is the build is going completely fine with 2.2.1, but not with 3.0rc3, so
I'm trying to understand where the difference lies.
And for the record, yes, it's a xml parser problem (oracle xmlparserv2 gets
in the way). I just configured exclusions and then it builds fine.
Sure, I could leave this exclusion here and check if it's also ok with mvn2,
but I'm quite reluctant to do that since it might hide a real isolation or
classpath ordering problem imo.
Cheers
2010/10/4 Olivier Lamy <ol...@apache.org>
> Hi,
> Not sure it's a maven issue here.
> You can try changing the sax parser
>
> -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
>
> with a recent xerces version in your classpath (in your pom I mean)
>
> In the gwt plugin configuration use
>
>
> <extraJvmArgs>...-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
> ...</extraJvmArgs>
>
> HTH,
> --
> Olivier
> http://twitter.com/olamy
> http://www.linkedin.com/in/olamy
>
> 2010/10/4 Baptiste MATHUS <ml...@batmat.net>:
> > Hi,
> >
> > I just tested maven3 on a project I hadn't tried before and notice a
> build
> > failure that doesn't happen with mvn2.2.1.
> > It seems to be related to XML parser problem&GWTTestCase.
> > I suspect it might be related to classpath ordering, though I remember
> this
> > order must be guaranteed since 2.0.9.
> >
> > I'd like to use dependency:list to check ordering, but I remember
> (Arnaud's
> > tweet, I'd say) reading that the dependency plugin output is not reliable
> > yet with maven3 execution? Is it?
> >
> > What are the possible ways to be able to debug it?
> >
> > Cheers
> > PS :
> > The full stacktrace:
> > [ERROR] Failure while parsing XML
> > org.xml.sax.SAXNotRecognizedException:
> > http://apache.org/xml/features/nonvalidating/load-external-dtd
> > at
> >
> oracle.xml.jaxp.JXSAXParserFactory.setFeature(JXSAXParserFactory.java:128)
> > at
> >
> com.google.gwt.dev.util.xml.ReflectiveParser$Impl.parse(ReflectiveParser.java:320)
> > at
> >
> com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access$100(ReflectiveParser.java:48)
> > at
> >
> com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:398)
> > at
> >
> com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:257)
> > at
> com.google.gwt.dev.cfg.ModuleDefLoader$2.load(ModuleDefLoader.java:187)
> > at
> >
> com.google.gwt.dev.cfg.ModuleDefLoader.doLoadModule(ModuleDefLoader.java:283)
> > at
> >
> com.google.gwt.dev.cfg.ModuleDefLoader.createSyntheticModule(ModuleDefLoader.java:95)
> > at
> >
> com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl2(CompileStrategy.java:169)
> > at
> >
> com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl(CompileStrategy.java:116)
> > at
> >
> com.google.gwt.junit.SimpleCompileStrategy.maybeCompileModule(CompileStrategy.java:330)
> > at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1296)
> > at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1265)
> > at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:620)
> > at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:456)
> > at junit.framework.TestCase.runBare(TestCase.java:127)
> > at junit.framework.TestResult$1.protect(TestResult.java:106)
> > at junit.framework.TestResult.runProtected(TestResult.java:124)
> > at junit.framework.TestResult.run(TestResult.java:109)
> > at junit.framework.TestCase.run(TestCase.java:118)
> > at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:311)
> > at junit.framework.TestSuite.runTest(TestSuite.java:208)
> > at junit.framework.TestSuite.run(TestSuite.java:203)
> > 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.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
> > at
> >
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115)
> > at
> >
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:140)
> > at org.apache.maven.surefire.Surefire.run(Surefire.java:109)
> > 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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
> > at
> >
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1017)
> > [ERROR] Unexpected error while processing XML
> >
> > 2010/10/2 Benjamin Bentmann <be...@udo.edu>
> >
> >> Robert Scholte wrote:
> >>
> >> [INFO] --- maven-gpg-plugin:1.1:sign (sign-artifacts) @ mojo-parent
> >>> ---
> >>> GPG Passphrase: *
> >>> gpg: can't open
> >>> `D:\java-workspace\helios\mojo-parent\target\mojo-parent-26-site.xml':
> No
> >>> such file or directory
> >>> gpg: signing failed: file open error
> >>>
> >>
> >> This is neither a bug in Maven, the Release Plugin nor the GPG Plugin
> but
> >> the Site Plugin:
> >>
> >> http://jira.codehaus.org/browse/MSITE-508
> >>
> >>
> >> Benjamin
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
> >
> > --
> > Baptiste <Batmat> MATHUS - http://batmat.net
> > Sauvez un arbre,
> > Mangez un castor !
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Re: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Olivier Lamy <ol...@apache.org>.
Hi,
Not sure it's a maven issue here.
You can try changing the sax parser
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
with a recent xerces version in your classpath (in your pom I mean)
In the gwt plugin configuration use
<extraJvmArgs>...-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
...</extraJvmArgs>
HTH,
--
Olivier
http://twitter.com/olamy
http://www.linkedin.com/in/olamy
2010/10/4 Baptiste MATHUS <ml...@batmat.net>:
> Hi,
>
> I just tested maven3 on a project I hadn't tried before and notice a build
> failure that doesn't happen with mvn2.2.1.
> It seems to be related to XML parser problem&GWTTestCase.
> I suspect it might be related to classpath ordering, though I remember this
> order must be guaranteed since 2.0.9.
>
> I'd like to use dependency:list to check ordering, but I remember (Arnaud's
> tweet, I'd say) reading that the dependency plugin output is not reliable
> yet with maven3 execution? Is it?
>
> What are the possible ways to be able to debug it?
>
> Cheers
> PS :
> The full stacktrace:
> [ERROR] Failure while parsing XML
> org.xml.sax.SAXNotRecognizedException:
> http://apache.org/xml/features/nonvalidating/load-external-dtd
> at
> oracle.xml.jaxp.JXSAXParserFactory.setFeature(JXSAXParserFactory.java:128)
> at
> com.google.gwt.dev.util.xml.ReflectiveParser$Impl.parse(ReflectiveParser.java:320)
> at
> com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access$100(ReflectiveParser.java:48)
> at
> com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:398)
> at
> com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:257)
> at com.google.gwt.dev.cfg.ModuleDefLoader$2.load(ModuleDefLoader.java:187)
> at
> com.google.gwt.dev.cfg.ModuleDefLoader.doLoadModule(ModuleDefLoader.java:283)
> at
> com.google.gwt.dev.cfg.ModuleDefLoader.createSyntheticModule(ModuleDefLoader.java:95)
> at
> com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl2(CompileStrategy.java:169)
> at
> com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl(CompileStrategy.java:116)
> at
> com.google.gwt.junit.SimpleCompileStrategy.maybeCompileModule(CompileStrategy.java:330)
> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1296)
> at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1265)
> at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:620)
> at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:456)
> at junit.framework.TestCase.runBare(TestCase.java:127)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:311)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> 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.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:140)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:109)
> 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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
> at
> org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1017)
> [ERROR] Unexpected error while processing XML
>
> 2010/10/2 Benjamin Bentmann <be...@udo.edu>
>
>> Robert Scholte wrote:
>>
>> [INFO] --- maven-gpg-plugin:1.1:sign (sign-artifacts) @ mojo-parent
>>> ---
>>> GPG Passphrase: *
>>> gpg: can't open
>>> `D:\java-workspace\helios\mojo-parent\target\mojo-parent-26-site.xml': No
>>> such file or directory
>>> gpg: signing failed: file open error
>>>
>>
>> This is neither a bug in Maven, the Release Plugin nor the GPG Plugin but
>> the Site Plugin:
>>
>> http://jira.codehaus.org/browse/MSITE-508
>>
>>
>> Benjamin
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Siarhei Dudzin <si...@gmail.com>.
Just fyi, the change in classpah ordering actually helped me to find a
conflict there. Been testing RC3 since its been out - all is good so far.
Regards,
Siarhei
On Oct 4, 2010 3:01 PM, "Benjamin Bentmann" <be...@udo.edu>
wrote:
Re: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Siarhei Dudzin <si...@gmail.com>.
Just fyi, the change in classpah ordering actually helped me to find a
conflict there. Been testing RC3 since its been out - all is good so far.
Regards,
Siarhei
On Oct 4, 2010 3:01 PM, "Benjamin Bentmann" <be...@udo.edu>
wrote:
> Baptiste MATHUS wrote:
>
>> I'd like to use dependency:list to check ordering, but I remember
(Arnaud's
>> tweet, I'd say) reading that the dependency plugin output is not reliable
>> yet with maven3 execution? Is it?
>
> Regardless of the Maven version, dependency:list cannot be used to check
> class path ordering because it sorts its output alphabetically.
>
> I suggest you enable debug logging and check the class path printed to
> the console by the plugin in question, i.e. the Surefire Plugin in your
> case.
>
> In general, you should avoid duplicate classes/dependencies on the class
> path and not rely on any order to solve conflicts.
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Re: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Benjamin Bentmann <be...@udo.edu>.
Baptiste MATHUS wrote:
> I'd like to use dependency:list to check ordering, but I remember (Arnaud's
> tweet, I'd say) reading that the dependency plugin output is not reliable
> yet with maven3 execution? Is it?
Regardless of the Maven version, dependency:list cannot be used to check
class path ordering because it sorts its output alphabetically.
I suggest you enable debug logging and check the class path printed to
the console by the plugin in question, i.e. the Surefire Plugin in your
case.
In general, you should avoid duplicate classes/dependencies on the class
path and not rely on any order to solve conflicts.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Baptiste MATHUS <ml...@batmat.net>.
Hi,
I just tested maven3 on a project I hadn't tried before and notice a build
failure that doesn't happen with mvn2.2.1.
It seems to be related to XML parser problem&GWTTestCase.
I suspect it might be related to classpath ordering, though I remember this
order must be guaranteed since 2.0.9.
I'd like to use dependency:list to check ordering, but I remember (Arnaud's
tweet, I'd say) reading that the dependency plugin output is not reliable
yet with maven3 execution? Is it?
What are the possible ways to be able to debug it?
Cheers
PS :
The full stacktrace:
[ERROR] Failure while parsing XML
org.xml.sax.SAXNotRecognizedException:
http://apache.org/xml/features/nonvalidating/load-external-dtd
at
oracle.xml.jaxp.JXSAXParserFactory.setFeature(JXSAXParserFactory.java:128)
at
com.google.gwt.dev.util.xml.ReflectiveParser$Impl.parse(ReflectiveParser.java:320)
at
com.google.gwt.dev.util.xml.ReflectiveParser$Impl.access$100(ReflectiveParser.java:48)
at
com.google.gwt.dev.util.xml.ReflectiveParser.parse(ReflectiveParser.java:398)
at
com.google.gwt.dev.cfg.ModuleDefLoader.nestedLoad(ModuleDefLoader.java:257)
at com.google.gwt.dev.cfg.ModuleDefLoader$2.load(ModuleDefLoader.java:187)
at
com.google.gwt.dev.cfg.ModuleDefLoader.doLoadModule(ModuleDefLoader.java:283)
at
com.google.gwt.dev.cfg.ModuleDefLoader.createSyntheticModule(ModuleDefLoader.java:95)
at
com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl2(CompileStrategy.java:169)
at
com.google.gwt.junit.CompileStrategy.maybeCompileModuleImpl(CompileStrategy.java:116)
at
com.google.gwt.junit.SimpleCompileStrategy.maybeCompileModule(CompileStrategy.java:330)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1296)
at com.google.gwt.junit.JUnitShell.runTestImpl(JUnitShell.java:1265)
at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:620)
at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:456)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:311)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
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.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:115)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.Surefire.run(Surefire.java:109)
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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1017)
[ERROR] Unexpected error while processing XML
2010/10/2 Benjamin Bentmann <be...@udo.edu>
> Robert Scholte wrote:
>
> [INFO] --- maven-gpg-plugin:1.1:sign (sign-artifacts) @ mojo-parent
>> ---
>> GPG Passphrase: *
>> gpg: can't open
>> `D:\java-workspace\helios\mojo-parent\target\mojo-parent-26-site.xml': No
>> such file or directory
>> gpg: signing failed: file open error
>>
>
> This is neither a bug in Maven, the Release Plugin nor the GPG Plugin but
> the Site Plugin:
>
> http://jira.codehaus.org/browse/MSITE-508
>
>
> Benjamin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Re: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Benjamin Bentmann <be...@udo.edu>.
Robert Scholte wrote:
> [INFO] --- maven-gpg-plugin:1.1:sign (sign-artifacts) @ mojo-parent ---
> GPG Passphrase: *
> gpg: can't open `D:\java-workspace\helios\mojo-parent\target\mojo-parent-26-site.xml': No such file or directory
> gpg: signing failed: file open error
This is neither a bug in Maven, the Release Plugin nor the GPG Plugin
but the Site Plugin:
http://jira.codehaus.org/browse/MSITE-508
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Robert Scholte <rf...@codehaus.org>.
Hi Benjamin,
I've tried to release the mojo-parent with Maven 3.0-RC3, but it failed:
[INFO] --- maven-gpg-plugin:1.1:sign (sign-artifacts) @ mojo-parent ---
GPG Passphrase: *
gpg: can't open `D:\java-workspace\helios\mojo-parent\target\mojo-parent-26-site.xml': No such file or directory
gpg: signing failed: file open error
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
According to the Maven 3.x Plugin Compatibility Matrix, this plugin should be M3 proof.
Running it with Maven 2.2.1 succeeded without any problem.
This parent contains a m3-profile for site-generation.
Also this project doesn't have a site, that's done in a separate project.
- Robert
> Date: Sun, 26 Sep 2010 18:24:30 +0200
> From: benjamin.bentmann@udo.edu
> To: dev@maven.apache.org; users@maven.apache.org
> Subject: [PLEASE TEST] Apache Maven 3.0-RC3
>
> Hi,
>
> in preparation for the release of Apache Maven 3.0, the Maven team is
> seeking your help to discover regressions since Maven 2.x. Everybody
> interested in taking a preview of the upcoming release for a test drive
> can get source and binary bundles from this URL:
>
> https://repository.apache.org/content/repositories/maven-014/org/apache/maven/apache-maven/3.0-RC3/
>
> Before reporting any issues found during testing, please be sure to have
> a close look at the compatibility notes for Maven 3.x:
>
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes
>
> If you encounter unexpected build issues, please fill a report in JIRA
> that provides sufficient information to reproduce and analyze the issue:
>
> http://jira.codehaus.org/browse/MNG
>
> The fixes contained in this release candidate since the 3.0-beta-3
> release and the previous release candidates can be seen in JIRA:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
>
> Thanks,
>
>
> -The Maven team
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
RE: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Ed Staub <es...@comcast.net>.
Stephen,
Thanks for the reply.
Maybe vote every N (3?) weeks on posting the latest RC?
Waiting till you "exhaust this pool of testers" adds unnecessary schedule
risk, doesn't it?
-Ed
-----Original Message-----
From: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
Sent: Sunday, September 26, 2010 5:34 PM
To: Maven Developers List
Subject: Re: [PLEASE TEST] Apache Maven 3.0-RC3
Updating the main page would require a formal vote on the dev list...
IANAL but AFAIK these are not formal releases, but weakly release candidates
and are not officially released by the apache foundation (because an
official release would require a vote and only official releases can be
linked from the home page)
Now just because they are not for4mal releases does not mean that they are
not good enough to try out, as the build process only difference is a 72h
voting period with testing by the maven developers, but we've found most
everything we can and we are now looking for wider feedback... when we
exhaust this pool of testers we'll fall back to voted releases I guess ;-)
-Stephen
On 26 September 2010 22:10, Ed Staub <es...@comcast.net> wrote:
> Just my 2 cents, but I'd think it would be good to get the release
> candidates reviewed publicly. The main page (http://maven.apache.org)
> still
> is at beta-3.
>
> -Ed Staub
>
> -----Original Message-----
> From: Benjamin Bentmann [mailto:benjamin.bentmann@udo.edu]
> Sent: Sunday, September 26, 2010 12:25 PM
> To: Maven Developers List; Maven Users List
> Subject: [PLEASE TEST] Apache Maven 3.0-RC3
>
> Hi,
>
> in preparation for the release of Apache Maven 3.0, the Maven team is
> seeking your help to discover regressions since Maven 2.x.
>
>
>
>
> ---------------------------------------------------------------------
> 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] Apache Maven 3.0-RC3
Posted by Stephen Connolly <st...@gmail.com>.
Updating the main page would require a formal vote on the dev list...
IANAL but AFAIK these are not formal releases, but weakly release candidates
and are not officially released by the apache foundation (because an
official release would require a vote and only official releases can be
linked from the home page)
Now just because they are not for4mal releases does not mean that they are
not good enough to try out, as the build process only difference is a 72h
voting period with testing by the maven developers, but we've found most
everything we can and we are now looking for wider feedback... when we
exhaust this pool of testers we'll fall back to voted releases I guess ;-)
-Stephen
On 26 September 2010 22:10, Ed Staub <es...@comcast.net> wrote:
> Just my 2 cents, but I'd think it would be good to get the release
> candidates reviewed publicly. The main page (http://maven.apache.org)
> still
> is at beta-3.
>
> -Ed Staub
>
> -----Original Message-----
> From: Benjamin Bentmann [mailto:benjamin.bentmann@udo.edu]
> Sent: Sunday, September 26, 2010 12:25 PM
> To: Maven Developers List; Maven Users List
> Subject: [PLEASE TEST] Apache Maven 3.0-RC3
>
> Hi,
>
> in preparation for the release of Apache Maven 3.0, the Maven team is
> seeking your help to discover regressions since Maven 2.x.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
RE: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Ed Staub <es...@comcast.net>.
Just my 2 cents, but I'd think it would be good to get the release
candidates reviewed publicly. The main page (http://maven.apache.org) still
is at beta-3.
-Ed Staub
-----Original Message-----
From: Benjamin Bentmann [mailto:benjamin.bentmann@udo.edu]
Sent: Sunday, September 26, 2010 12:25 PM
To: Maven Developers List; Maven Users List
Subject: [PLEASE TEST] Apache Maven 3.0-RC3
Hi,
in preparation for the release of Apache Maven 3.0, the Maven team is
seeking your help to discover regressions since Maven 2.x.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Benjamin Bentmann <be...@udo.edu>.
Marshall Schor wrote:
> Is a workaround (until Nexus is patched), to use -Dmaven.metadata.legacy=true on
> the maven command line?
Yes.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Marshall Schor <ms...@schor.com>.
thanks! -Marshall
On 10/1/2010 6:31 AM, Benjamin Bentmann wrote:
> Marshall Schor wrote:
>
>> Is a workaround (until Nexus is patched), to use -Dmaven.metadata.legacy=true on
>> the maven command line?
>
> The workaround is no longer necessary to deploy Apache snapshots, r.a.o has
> been updated to Nexus 1.8.0 by now.
>
>
> Benjamin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Benjamin Bentmann <be...@udo.edu>.
Marshall Schor wrote:
> Is a workaround (until Nexus is patched), to use -Dmaven.metadata.legacy=true on
> the maven command line?
The workaround is no longer necessary to deploy Apache snapshots, r.a.o
has been updated to Nexus 1.8.0 by now.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Marshall Schor <ms...@schor.com>.
On 9/30/2010 9:34 AM, Benjamin Bentmann wrote:
> Marshall Schor wrote:
>
>> The file under<version>-SNAPSHOT/maven-metadata.xml can't be read using
>> http://repository.apache.org/snapshots/org/apache/uima/parent-pom-docbook/4-SNAPSHOT/maven-metadata.xml.
>>
>
> r.a.o/snapshots is a group, the actual repository contains the intact file:
>
> https://repository.apache.org/content/repositories/snapshots/org/apache/uima/parent-pom-docbook/4-SNAPSHOT/maven-metadata.xml
>
>
>> So - it looks like RC3 is missing the namespaces declarations?
>
> The namespace declaration isn't relevant (Maven 2.x doesn't specify it
> either), the failure is due to the file's extended format, see also [0].
Is a workaround (until Nexus is patched), to use -Dmaven.metadata.legacy=true on
the maven command line?
-Marshall Schor
>
> I know that Nexus has already been updated to support this, will check whether
> this update/patch can be installed on r.a.o.
>
>
> Benjamin
>
>
>
> [0]
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-UniqueSnapshotVersionsandClassifiers
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Benjamin Bentmann <be...@udo.edu>.
Marshall Schor wrote:
> The file under<version>-SNAPSHOT/maven-metadata.xml can't be read using
> http://repository.apache.org/snapshots/org/apache/uima/parent-pom-docbook/4-SNAPSHOT/maven-metadata.xml.
r.a.o/snapshots is a group, the actual repository contains the intact file:
https://repository.apache.org/content/repositories/snapshots/org/apache/uima/parent-pom-docbook/4-SNAPSHOT/maven-metadata.xml
> So - it looks like RC3 is missing the namespaces declarations?
The namespace declaration isn't relevant (Maven 2.x doesn't specify it
either), the failure is due to the file's extended format, see also [0].
I know that Nexus has already been updated to support this, will check
whether this update/patch can be installed on r.a.o.
Benjamin
[0]
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-UniqueSnapshotVersionsandClassifiers
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [PLEASE TEST] Apache Maven 3.0-RC3
Posted by Marshall Schor <ms...@schor.com>.
Tried building our project (uima) - that works, but the deploy (snapshot)
deploys a broken file.
The file under <version>-SNAPSHOT/maven-metadata.xml can't be read using
http://repository.apache.org/snapshots/org/apache/uima/parent-pom-docbook/4-SNAPSHOT/maven-metadata.xml.
A build referring to this gets:
[DEBUG] Could not find metadata
org.apache.uima:parent-pom-docbook:4-SNAPSHOT/maven-metadata.xml
[DEBUG] Using connector WagonRepositoryConnector with priority 0 for
http://repository.apache.org/snapshots
Downloading:
http://repository.apache.org/snapshots/org/apache/uima/parent-pom-docbook/4-SNAPSHOT/maven-metadata.xml
[DEBUG] Reading resolution tracking file
/home/schor/.m2/repository/org/apache/uima/parent-pom-docbook/4-SNAPSHOT/resolver-status.properties
[DEBUG] Writing resolution tracking file
/home/schor/.m2/repository/org/apache/uima/parent-pom-docbook/4-SNAPSHOT/resolver-status.properties
[DEBUG] Could not find metadata
org.apache.uima:parent-pom-docbook:4-SNAPSHOT/maven-metadata.xml in
apache.snapshots (http://repository.apache.org/snapshots)
If you try that URL in a browser, it returns some message saying the file isn't
there.
(However, if you try the alternative way to get a file in Nexus: going to the url:
http://repository.apache.org , and then clicking on the "snapshot" repositories,
and then navigating to org/apache/uima/parent-pom-docbook/4-SNAPSHOT, you can
right click the maven-metadata.xml file and the repository browser pops up a
"download" button, which does work.)
A workaround is to use mvn 3.0-beta-1 - it doesn't exhibit this problem, and the
deploy to the snapshot works fine; browsing to maven-metadata.xml shows the file
in the browser.
I compared the two files in my local .m2 repos which I'm guessing are the
"local" copies that are copied up to the server: these are named in the local
repo: maven-metadata-apache.snapshots.https.xml
The files differ: the RC3 version's top XML element is:
<metadata modelVersion="1.1.0">
The 3.0-beta-1's top element is:
<metadata xsi:schemaLocation="http://maven.apache.org/METADATA/1.0.0
http://maven.apache.org/xsd/metadata-1.0.0.xsd"
xmlns="http://maven.apache.org/METADATA/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
So - it looks like RC3 is missing the namespaces declarations? (I think this is
also true for RC2).
-Marshall Schor
On 9/26/2010 12:24 PM, Benjamin Bentmann wrote:
> Hi,
>
> in preparation for the release of Apache Maven 3.0, the Maven team is seeking
> your help to discover regressions since Maven 2.x. Everybody interested in
> taking a preview of the upcoming release for a test drive can get source and
> binary bundles from this URL:
>
> https://repository.apache.org/content/repositories/maven-014/org/apache/maven/apache-maven/3.0-RC3/
>
>
> Before reporting any issues found during testing, please be sure to have a
> close look at the compatibility notes for Maven 3.x:
>
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes
>
> If you encounter unexpected build issues, please fill a report in JIRA that
> provides sufficient information to reproduce and analyze the issue:
>
> http://jira.codehaus.org/browse/MNG
>
> The fixes contained in this release candidate since the 3.0-beta-3 release and
> the previous release candidates can be seen in JIRA:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=13142
>
> Thanks,
>
>
> -The Maven team
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org