Do you have a way to reproduce this? The DefaultPathTranslator class
hasn't changed since 2.0.6 so it must be a higher level change we're
looking for.
-----Original Message-----
From: Kaizer H. Sogiawala [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2008 12:49 AM
To: Maven Users List
Subject: Re: [2.0.9 RC7] Release Candidate testing
I am getting a strange behavior with apache-maven-2.0.9-RC* (all RC)
builds. Here is what I see-
--- SNIP ---
+ Error stacktraces are turned on.
Maven version: 2.0.9-RC7
Java version: 1.5.0_12
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
[DEBUG] Building Maven user-level plugin registry from: 'C:
\Documents
and Settings\blip\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from: 'C:
\Program
Files\maven\bin\..\conf\plugin-registry.xml'
[INFO] Scanning for projects...
:
: *blip blip*
:
[INFO]
---------------------------------------------------------------------
---
[ERROR] FATAL ERROR
[INFO]
---------------------------------------------------------------------
---
[INFO] String index out of range: -1
[INFO]
---------------------------------------------------------------------
---
[DEBUG] Trace
java.lang.StringIndexOutOfBoundsException: String index out of
range: -1
at java.lang.String.substring(String.java:1768)
at java.lang.String.substring(String.java:1735)
at
org.apache.maven.project.path.DefaultPathTranslator.stripBasedirToken
(De
faultPathTranslator.java:101)
at
org.apache.maven.project.path.DefaultPathTranslator.alignToBaseDirect
ory
(DefaultPathTranslator.java:82)
at
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLog
ic(
DefaultMavenProjectBuilder.java:992)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal
(Defaul
tMavenProjectBuilder.java:867)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi
leI
nternal(DefaultMavenProjectBuilder.java:495)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build
(DefaultMavenPr
ojectBuilder.java:198)
at
org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessor
Impl.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)
[INFO]
---------------------------------------------------------------------
---
[INFO] Total time: < 1 second
[INFO] Finished at: Wed Apr 02 21:40:25 PDT 2008
[INFO] Final Memory: 1M/2M
[INFO]
---------------------------------------------------------------------
---
--- SNIP ---
This project is working fine with a 2.0.9-SNAPSHOT build with
following date/time stamp-
#Generated by Maven
#Thu Feb 21 21:53:42 PST 2008
version=2.0.9-SNAPSHOT
groupId=org.apache.maven
artifactId=maven-core
--
Our build system uses multiple plugins developed inhouse with
packaging type and forked lifecycle.
On Wed, Apr 2, 2008 at 2:52 PM, Brian E. Fox
<[EMAIL PROTECTED]>
wrote:
Thank you everyone for the testing and confirmatory responses so
far.
It
helps to gauge the progress. There was one regression identified in
2.0.9 RC6: (MNG-3495: NPE at
org.apache.maven.wagon.repository.Repository.hashCode). This has
been
fixed and RC7 posted.
Various users have identified some issues with the site plugin that
seem
to occur when switching to 2.0.9. This can happen because we
started
locking down versions in 2.0.9. This is so if you haven't
specified a
version in your poms, it won't change on you going forward. This
means
that you will get upgraded to the latest site plugin (2.0-beta-6)
just
like you would if you did mvn -U on your build. If you have trouble
with
site after using 2.0.9, try specifying maven-site-plugin 2.0-beta-5
in
your pom (we recommend locking your versions anyway). This is
preferable
to locking 2.0.9 to beta-5 for everyone and potentially forcing
some
people's versions backwards.
In the future, only the most stable versions will be locked in the
super
pom and usually this will not be the most recent release. Since
2.0.9
was the first time we did this, we had to go with the current
versions
as the baseline.
RC7 is available for download here:
http://people.apache.org/~brianf/staging-repository/org/apache/
maven/apa
che-maven/
Thank you for your assistance in testing the RCs.
--Brian
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
+ Kaizer H. Sogiawala +
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
