You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brian E. Fox" <br...@reply.infinity.nu> on 2008/04/03 21:51:47 UTC
[2.0.9 RC8] Release Candidate testing
RC8 posted to solve this regression.
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/
-----Original Message-----
From: Kaizer H. Sogiawala [mailto:kaizers@gmail.com]
Sent: Thursday, April 03, 2008 2:51 PM
To: Maven Users List
Subject: Re: [2.0.9 RC7] Release Candidate testing
I debugged through the source and can confirm
"<directory>${basedir}</directory>" is the issue.
On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jd...@commonjava.org>
wrote:
> FWIW, using:
>
> <build>
> <directory>${basedir}</directory>
> </build>
>
> will express this error. See http://jira.codehaus.org/browse/MNG-3498
>
> I have the fix, just need to get it cleaned up and committed.
>
> -john
>
>
>
> On Apr 3, 2008, at 11:23 AM, Brett Porter wrote:
>
>
> > -1 could be empty string, and there were some hacks in the project
> > builder that set expressions to that. I know that the path
translator
> > was effected by interpolation changes, even though indirectly,
because
> > the values got interpolated after instead of before.
> >
> > I'd look at those changes - though a POM that reproduces it is
> > probably necessary to do so.
> >
> > - Brett
> >
> > On 04/04/2008, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > > 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:kaizers@gmail.com]
> > > 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.alignToBaseDirectory
> > > (DefaultPathTranslator.java:82)
> > > at
> > >
>
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(
> > > DefaultMavenProjectBuilder.java:992)
> > > at
> > >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul
> > > tMavenProjectBuilder.java:867)
> > > at
> > >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI
> > > 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
<br...@reply.infinity.nu>
> > > 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: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > + Kaizer H. Sogiawala +
> > >
> > >
---------------------------------------------------------------------
> > > 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
> > >
> > >
> > >
> >
> >
> > --
> > Brett Porter
> > Blog: http://blogs.exist.com/bporter/
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> ---
> John Casey
> Committer and PMC Member, Apache Maven
> mail: jdcasey at commonjava dot org
> blog: http://www.ejlife.net/blogs/john
> rss: http://feeds.feedburner.com/ejlife/john
>
>
>
--
+ Kaizer H. Sogiawala +
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [2.0.9 RC8] Release Candidate testing
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Yeah! Someone who locks them down!
Summary of what I sent to the user list: If you're locking them down
yourself, this will have no effect. It will also not affect the enforcer
plugin output.
-----Original Message-----
From: Jason Chaffee [mailto:jason_chaffee@tvworks.com]
Sent: Thursday, April 03, 2008 10:54 PM
To: Maven Developers List
Subject: RE: [2.0.9 RC8] Release Candidate testing
This is exactly why we lock down plugins ourself. However, I was just
curious to know how it would impact that and how it would impact the use
of the enforcer plugin to catch plugins not locked down.
Thanks.
-----Original Message-----
From: Sejal Patel [mailto:sepatel@gmail.com]
Sent: Thursday, April 03, 2008 3:54 PM
To: Maven Developers List
Subject: Re: [2.0.9 RC8] Release Candidate testing
Hmm, well jason, it really is as simple as the super pom (that pom-4.0.0
thingy) listing out all of the plugins and specifying a specific version
number on them. I'm taking a peek at the RC5 version of the superpom
(havn't
gotten around to 6, 7, or 8 now) and it looks like it is using the most
recent version (at least according to the plugins page) of a lot of
different plugins.
So what it means is that if you specify in your pom a different version,
yours will take precendence over the locked down versions.
The whole purpose of the lockdown is simply so that a project you are
working on today will still work 3 years later and not break because
suddenly a new version of a plugin was made within the next 3 years and
you
forgot to lock it to the older version and so it pulled down the
latest/greated automagically and broke everything that you had in
production
:)
On Thu, Apr 3, 2008 at 4:23 PM, Jason Chaffee
<ja...@tvworks.com>
wrote:
> Brian,
>
> Is there any documentation about the new "locked down" plugin in
feature
> in 2.0.9?
>
> I would like to know how it works, how it impacts not having plugins
> locked vs. having them locked down already in your pom and how it
would
> impact the enforcer plugin as well.
>
> Thanks.
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Thursday, April 03, 2008 12:52 PM
> To: Maven Users List
> Cc: Maven Developers List
> Subject: [2.0.9 RC8] Release Candidate testing
>
> RC8 posted to solve this regression.
>
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
>
che-maven/<http://people.apache.org/%7Ebrianf/staging-repository/org/apa
che/maven/apache-maven/>
>
> -----Original Message-----
> From: Kaizer H. Sogiawala [mailto:kaizers@gmail.com]
> Sent: Thursday, April 03, 2008 2:51 PM
> To: Maven Users List
> Subject: Re: [2.0.9 RC7] Release Candidate testing
>
> I debugged through the source and can confirm
> "<directory>${basedir}</directory>" is the issue.
>
> On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jd...@commonjava.org>
> wrote:
> > FWIW, using:
> >
> > <build>
> > <directory>${basedir}</directory>
> > </build>
> >
> > will express this error. See
http://jira.codehaus.org/browse/MNG-3498
> >
> > I have the fix, just need to get it cleaned up and committed.
> >
> > -john
> >
> >
> >
> > On Apr 3, 2008, at 11:23 AM, Brett Porter wrote:
> >
> >
> > > -1 could be empty string, and there were some hacks in the project
> > > builder that set expressions to that. I know that the path
> translator
> > > was effected by interpolation changes, even though indirectly,
> because
> > > the values got interpolated after instead of before.
> > >
> > > I'd look at those changes - though a POM that reproduces it is
> > > probably necessary to do so.
> > >
> > > - Brett
> > >
> > > On 04/04/2008, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > > 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:kaizers@gmail.com]
> > > > 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.alignToBaseDirectory
> > > > (DefaultPathTranslator.java:82)
> > > > at
> > > >
> >
>
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(
> > > > DefaultMavenProjectBuilder.java:992)
> > > > at
> > > >
> >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul
> > > > tMavenProjectBuilder.java:867)
> > > > at
> > > >
> >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI
> > > > 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
> <br...@reply.infinity.nu>
> > > > 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
<http://people.apache.org/%7Ebrianf/staging-repository/org/apache/maven/
apa>
> > > >
> > > > > che-maven/
> > > > >
> > > > >
> > > > > Thank you for your assistance in testing the RCs.
> > > > >
> > > > > --Brian
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > >
> > > > >
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > + Kaizer H. Sogiawala +
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > 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
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Brett Porter
> > > Blog: http://blogs.exist.com/bporter/
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > ---
> > John Casey
> > Committer and PMC Member, Apache Maven
> > mail: jdcasey at commonjava dot org
> > blog: http://www.ejlife.net/blogs/john
> > rss: http://feeds.feedburner.com/ejlife/john
> >
> >
> >
>
>
>
> --
> + Kaizer H. Sogiawala +
>
> ---------------------------------------------------------------------
> 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
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Justice is nothing more than that which is in the greatest self-interest
of
the largest portion of the population.
---------------------------------------------------------------------
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: [2.0.9 RC8] Release Candidate testing
Posted by Jason Chaffee <ja...@tvworks.com>.
This is exactly why we lock down plugins ourself. However, I was just
curious to know how it would impact that and how it would impact the use
of the enforcer plugin to catch plugins not locked down.
Thanks.
-----Original Message-----
From: Sejal Patel [mailto:sepatel@gmail.com]
Sent: Thursday, April 03, 2008 3:54 PM
To: Maven Developers List
Subject: Re: [2.0.9 RC8] Release Candidate testing
Hmm, well jason, it really is as simple as the super pom (that pom-4.0.0
thingy) listing out all of the plugins and specifying a specific version
number on them. I'm taking a peek at the RC5 version of the superpom
(havn't
gotten around to 6, 7, or 8 now) and it looks like it is using the most
recent version (at least according to the plugins page) of a lot of
different plugins.
So what it means is that if you specify in your pom a different version,
yours will take precendence over the locked down versions.
The whole purpose of the lockdown is simply so that a project you are
working on today will still work 3 years later and not break because
suddenly a new version of a plugin was made within the next 3 years and
you
forgot to lock it to the older version and so it pulled down the
latest/greated automagically and broke everything that you had in
production
:)
On Thu, Apr 3, 2008 at 4:23 PM, Jason Chaffee
<ja...@tvworks.com>
wrote:
> Brian,
>
> Is there any documentation about the new "locked down" plugin in
feature
> in 2.0.9?
>
> I would like to know how it works, how it impacts not having plugins
> locked vs. having them locked down already in your pom and how it
would
> impact the enforcer plugin as well.
>
> Thanks.
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Thursday, April 03, 2008 12:52 PM
> To: Maven Users List
> Cc: Maven Developers List
> Subject: [2.0.9 RC8] Release Candidate testing
>
> RC8 posted to solve this regression.
>
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
>
che-maven/<http://people.apache.org/%7Ebrianf/staging-repository/org/apa
che/maven/apache-maven/>
>
> -----Original Message-----
> From: Kaizer H. Sogiawala [mailto:kaizers@gmail.com]
> Sent: Thursday, April 03, 2008 2:51 PM
> To: Maven Users List
> Subject: Re: [2.0.9 RC7] Release Candidate testing
>
> I debugged through the source and can confirm
> "<directory>${basedir}</directory>" is the issue.
>
> On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jd...@commonjava.org>
> wrote:
> > FWIW, using:
> >
> > <build>
> > <directory>${basedir}</directory>
> > </build>
> >
> > will express this error. See
http://jira.codehaus.org/browse/MNG-3498
> >
> > I have the fix, just need to get it cleaned up and committed.
> >
> > -john
> >
> >
> >
> > On Apr 3, 2008, at 11:23 AM, Brett Porter wrote:
> >
> >
> > > -1 could be empty string, and there were some hacks in the project
> > > builder that set expressions to that. I know that the path
> translator
> > > was effected by interpolation changes, even though indirectly,
> because
> > > the values got interpolated after instead of before.
> > >
> > > I'd look at those changes - though a POM that reproduces it is
> > > probably necessary to do so.
> > >
> > > - Brett
> > >
> > > On 04/04/2008, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > > 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:kaizers@gmail.com]
> > > > 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.alignToBaseDirectory
> > > > (DefaultPathTranslator.java:82)
> > > > at
> > > >
> >
>
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(
> > > > DefaultMavenProjectBuilder.java:992)
> > > > at
> > > >
> >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul
> > > > tMavenProjectBuilder.java:867)
> > > > at
> > > >
> >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI
> > > > 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
> <br...@reply.infinity.nu>
> > > > 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
<http://people.apache.org/%7Ebrianf/staging-repository/org/apache/maven/
apa>
> > > >
> > > > > che-maven/
> > > > >
> > > > >
> > > > > Thank you for your assistance in testing the RCs.
> > > > >
> > > > > --Brian
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > >
> > > > >
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > + Kaizer H. Sogiawala +
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > 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
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Brett Porter
> > > Blog: http://blogs.exist.com/bporter/
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > ---
> > John Casey
> > Committer and PMC Member, Apache Maven
> > mail: jdcasey at commonjava dot org
> > blog: http://www.ejlife.net/blogs/john
> > rss: http://feeds.feedburner.com/ejlife/john
> >
> >
> >
>
>
>
> --
> + Kaizer H. Sogiawala +
>
> ---------------------------------------------------------------------
> 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
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Justice is nothing more than that which is in the greatest self-interest
of
the largest portion of the population.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [2.0.9 RC8] Release Candidate testing
Posted by Sejal Patel <se...@gmail.com>.
Hmm, well jason, it really is as simple as the super pom (that pom-4.0.0
thingy) listing out all of the plugins and specifying a specific version
number on them. I'm taking a peek at the RC5 version of the superpom (havn't
gotten around to 6, 7, or 8 now) and it looks like it is using the most
recent version (at least according to the plugins page) of a lot of
different plugins.
So what it means is that if you specify in your pom a different version,
yours will take precendence over the locked down versions.
The whole purpose of the lockdown is simply so that a project you are
working on today will still work 3 years later and not break because
suddenly a new version of a plugin was made within the next 3 years and you
forgot to lock it to the older version and so it pulled down the
latest/greated automagically and broke everything that you had in production
:)
On Thu, Apr 3, 2008 at 4:23 PM, Jason Chaffee <ja...@tvworks.com>
wrote:
> Brian,
>
> Is there any documentation about the new "locked down" plugin in feature
> in 2.0.9?
>
> I would like to know how it works, how it impacts not having plugins
> locked vs. having them locked down already in your pom and how it would
> impact the enforcer plugin as well.
>
> Thanks.
>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Thursday, April 03, 2008 12:52 PM
> To: Maven Users List
> Cc: Maven Developers List
> Subject: [2.0.9 RC8] Release Candidate testing
>
> RC8 posted to solve this regression.
> http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
> che-maven/<http://people.apache.org/%7Ebrianf/staging-repository/org/apache/maven/apache-maven/>
>
> -----Original Message-----
> From: Kaizer H. Sogiawala [mailto:kaizers@gmail.com]
> Sent: Thursday, April 03, 2008 2:51 PM
> To: Maven Users List
> Subject: Re: [2.0.9 RC7] Release Candidate testing
>
> I debugged through the source and can confirm
> "<directory>${basedir}</directory>" is the issue.
>
> On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jd...@commonjava.org>
> wrote:
> > FWIW, using:
> >
> > <build>
> > <directory>${basedir}</directory>
> > </build>
> >
> > will express this error. See http://jira.codehaus.org/browse/MNG-3498
> >
> > I have the fix, just need to get it cleaned up and committed.
> >
> > -john
> >
> >
> >
> > On Apr 3, 2008, at 11:23 AM, Brett Porter wrote:
> >
> >
> > > -1 could be empty string, and there were some hacks in the project
> > > builder that set expressions to that. I know that the path
> translator
> > > was effected by interpolation changes, even though indirectly,
> because
> > > the values got interpolated after instead of before.
> > >
> > > I'd look at those changes - though a POM that reproduces it is
> > > probably necessary to do so.
> > >
> > > - Brett
> > >
> > > On 04/04/2008, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > > 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:kaizers@gmail.com]
> > > > 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.alignToBaseDirectory
> > > > (DefaultPathTranslator.java:82)
> > > > at
> > > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(
> > > > DefaultMavenProjectBuilder.java:992)
> > > > at
> > > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul
> > > > tMavenProjectBuilder.java:867)
> > > > at
> > > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI
> > > > 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
> <br...@reply.infinity.nu>
> > > > 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<http://people.apache.org/%7Ebrianf/staging-repository/org/apache/maven/apa>
> > > >
> > > > > che-maven/
> > > > >
> > > > >
> > > > > Thank you for your assistance in testing the RCs.
> > > > >
> > > > > --Brian
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > >
> > > > >
> > > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > + Kaizer H. Sogiawala +
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > 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
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Brett Porter
> > > Blog: http://blogs.exist.com/bporter/
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > ---
> > John Casey
> > Committer and PMC Member, Apache Maven
> > mail: jdcasey at commonjava dot org
> > blog: http://www.ejlife.net/blogs/john
> > rss: http://feeds.feedburner.com/ejlife/john
> >
> >
> >
>
>
>
> --
> + Kaizer H. Sogiawala +
>
> ---------------------------------------------------------------------
> 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
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Justice is nothing more than that which is in the greatest self-interest of
the largest portion of the population.
RE: [2.0.9 RC8] Release Candidate testing
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Jason, nothing written yet. The effect is the same as putting the
versions in the pluginManagement of your corp pom. If you have defined
them in your poms then those will override the superpom.
The enforcer rule walks the tree and does not look at the super pom so
it will still tell you which plugins are not defined in your pom
hierarchy.
-----Original Message-----
From: Jason Chaffee [mailto:jason_chaffee@tvworks.com]
Sent: Thursday, April 03, 2008 4:23 PM
To: Maven Users List
Cc: Maven Developers List
Subject: RE: [2.0.9 RC8] Release Candidate testing
Brian,
Is there any documentation about the new "locked down" plugin in feature
in 2.0.9?
I would like to know how it works, how it impacts not having plugins
locked vs. having them locked down already in your pom and how it would
impact the enforcer plugin as well.
Thanks.
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Thursday, April 03, 2008 12:52 PM
To: Maven Users List
Cc: Maven Developers List
Subject: [2.0.9 RC8] Release Candidate testing
RC8 posted to solve this regression.
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/
-----Original Message-----
From: Kaizer H. Sogiawala [mailto:kaizers@gmail.com]
Sent: Thursday, April 03, 2008 2:51 PM
To: Maven Users List
Subject: Re: [2.0.9 RC7] Release Candidate testing
I debugged through the source and can confirm
"<directory>${basedir}</directory>" is the issue.
On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jd...@commonjava.org>
wrote:
> FWIW, using:
>
> <build>
> <directory>${basedir}</directory>
> </build>
>
> will express this error. See http://jira.codehaus.org/browse/MNG-3498
>
> I have the fix, just need to get it cleaned up and committed.
>
> -john
>
>
>
> On Apr 3, 2008, at 11:23 AM, Brett Porter wrote:
>
>
> > -1 could be empty string, and there were some hacks in the project
> > builder that set expressions to that. I know that the path
translator
> > was effected by interpolation changes, even though indirectly,
because
> > the values got interpolated after instead of before.
> >
> > I'd look at those changes - though a POM that reproduces it is
> > probably necessary to do so.
> >
> > - Brett
> >
> > On 04/04/2008, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > > 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:kaizers@gmail.com]
> > > 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.alignToBaseDirectory
> > > (DefaultPathTranslator.java:82)
> > > at
> > >
>
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(
> > > DefaultMavenProjectBuilder.java:992)
> > > at
> > >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul
> > > tMavenProjectBuilder.java:867)
> > > at
> > >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI
> > > 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
<br...@reply.infinity.nu>
> > > 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: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > + Kaizer H. Sogiawala +
> > >
> > >
---------------------------------------------------------------------
> > > 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
> > >
> > >
> > >
> >
> >
> > --
> > Brett Porter
> > Blog: http://blogs.exist.com/bporter/
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> ---
> John Casey
> Committer and PMC Member, Apache Maven
> mail: jdcasey at commonjava dot org
> blog: http://www.ejlife.net/blogs/john
> rss: http://feeds.feedburner.com/ejlife/john
>
>
>
--
+ Kaizer H. Sogiawala +
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: [2.0.9 RC8] Release Candidate testing
Posted by Jason Chaffee <ja...@tvworks.com>.
Brian,
Is there any documentation about the new "locked down" plugin in feature
in 2.0.9?
I would like to know how it works, how it impacts not having plugins
locked vs. having them locked down already in your pom and how it would
impact the enforcer plugin as well.
Thanks.
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Thursday, April 03, 2008 12:52 PM
To: Maven Users List
Cc: Maven Developers List
Subject: [2.0.9 RC8] Release Candidate testing
RC8 posted to solve this regression.
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/
-----Original Message-----
From: Kaizer H. Sogiawala [mailto:kaizers@gmail.com]
Sent: Thursday, April 03, 2008 2:51 PM
To: Maven Users List
Subject: Re: [2.0.9 RC7] Release Candidate testing
I debugged through the source and can confirm
"<directory>${basedir}</directory>" is the issue.
On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jd...@commonjava.org>
wrote:
> FWIW, using:
>
> <build>
> <directory>${basedir}</directory>
> </build>
>
> will express this error. See http://jira.codehaus.org/browse/MNG-3498
>
> I have the fix, just need to get it cleaned up and committed.
>
> -john
>
>
>
> On Apr 3, 2008, at 11:23 AM, Brett Porter wrote:
>
>
> > -1 could be empty string, and there were some hacks in the project
> > builder that set expressions to that. I know that the path
translator
> > was effected by interpolation changes, even though indirectly,
because
> > the values got interpolated after instead of before.
> >
> > I'd look at those changes - though a POM that reproduces it is
> > probably necessary to do so.
> >
> > - Brett
> >
> > On 04/04/2008, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > > 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:kaizers@gmail.com]
> > > 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.alignToBaseDirectory
> > > (DefaultPathTranslator.java:82)
> > > at
> > >
>
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(
> > > DefaultMavenProjectBuilder.java:992)
> > > at
> > >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul
> > > tMavenProjectBuilder.java:867)
> > > at
> > >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI
> > > 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
<br...@reply.infinity.nu>
> > > 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: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > + Kaizer H. Sogiawala +
> > >
> > >
---------------------------------------------------------------------
> > > 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
> > >
> > >
> > >
> >
> >
> > --
> > Brett Porter
> > Blog: http://blogs.exist.com/bporter/
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> ---
> John Casey
> Committer and PMC Member, Apache Maven
> mail: jdcasey at commonjava dot org
> blog: http://www.ejlife.net/blogs/john
> rss: http://feeds.feedburner.com/ejlife/john
>
>
>
--
+ Kaizer H. Sogiawala +
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: [2.0.9 RC8] Release Candidate testing
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Thanks everyone for the testing. Nothing has turned up in several days
so we'll move forward with the official release.
--Brian
-----Original Message-----
From: Erez Nahir [mailto:erez.nahir@gmail.com]
Sent: Monday, April 07, 2008 1:51 AM
To: Maven Users List
Subject: Re: [2.0.9 RC8] Release Candidate testing
Just additinal confirmation - 2.0.9-RC7 works fine for our team.
Erez.
On Fri, Apr 4, 2008 at 1:46 AM, Kaizer H. Sogiawala <ka...@gmail.com>
wrote:
> +1
>
> I can confirm that the issue
> (http://jira.codehaus.org/browse/MNG-3498) is resolved in RC8. My
> projects are building fine. Thanks!
>
> On Thu, Apr 3, 2008 at 12:51 PM, Brian E. Fox
<br...@reply.infinity.nu>
> wrote:
> > RC8 posted to solve this regression.
> >
> >
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
> > che-maven/
> >
> >
> > -----Original Message-----
> > From: Kaizer H. Sogiawala [mailto:kaizers@gmail.com]
> >
> >
> > Sent: Thursday, April 03, 2008 2:51 PM
> > To: Maven Users List
> > Subject: Re: [2.0.9 RC7] Release Candidate testing
> >
> > I debugged through the source and can confirm
> > "<directory>${basedir}</directory>" is the issue.
> >
> > On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jd...@commonjava.org>
> > wrote:
> > > FWIW, using:
> > >
> > > <build>
> > > <directory>${basedir}</directory>
> > > </build>
> > >
> > > will express this error. See
> http://jira.codehaus.org/browse/MNG-3498
> > >
> > > I have the fix, just need to get it cleaned up and committed.
> > >
> > > -john
> > >
> > >
> > >
> > > On Apr 3, 2008, at 11:23 AM, Brett Porter wrote:
> > >
> > >
> > > > -1 could be empty string, and there were some hacks in the
project
> > > > builder that set expressions to that. I know that the path
> > translator
> > > > was effected by interpolation changes, even though indirectly,
> > because
> > > > the values got interpolated after instead of before.
> > > >
> > > > I'd look at those changes - though a POM that reproduces it is
> > > > probably necessary to do so.
> > > >
> > > > - Brett
> > > >
> > > > On 04/04/2008, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > >
> > > > > 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:kaizers@gmail.com]
> > > > > 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.alignToBaseDirectory
> > > > > (DefaultPathTranslator.java:82)
> > > > > at
> > > > >
> > >
> >
>
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(
> > > > > DefaultMavenProjectBuilder.java:992)
> > > > > at
> > > > >
> > >
> >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul
> > > > > tMavenProjectBuilder.java:867)
> > > > > at
> > > > >
> > >
> >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI
> > > > > 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
> > <br...@reply.infinity.nu>
> > > > > 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: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail:
users-help@maven.apache.org
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > + Kaizer H. Sogiawala +
> > > > >
> > > > >
> >
---------------------------------------------------------------------
> > > > > 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
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Brett Porter
> > > > Blog: http://blogs.exist.com/bporter/
> > > >
> > > >
> >
---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> > > ---
> > > John Casey
> > > Committer and PMC Member, Apache Maven
> > > mail: jdcasey at commonjava dot org
> > > blog: http://www.ejlife.net/blogs/john
> > > rss: http://feeds.feedburner.com/ejlife/john
> > >
> > >
> > >
> >
> >
> >
> > --
> > + Kaizer H. Sogiawala +
> >
> >
---------------------------------------------------------------------
> > 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
> >
> >
>
>
>
> --
> + Kaizer H. Sogiawala +
>
> ---------------------------------------------------------------------
> 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: [2.0.9 RC8] Release Candidate testing
Posted by Erez Nahir <er...@gmail.com>.
Just additinal confirmation - 2.0.9-RC7 works fine for our team.
Erez.
On Fri, Apr 4, 2008 at 1:46 AM, Kaizer H. Sogiawala <ka...@gmail.com>
wrote:
> +1
>
> I can confirm that the issue
> (http://jira.codehaus.org/browse/MNG-3498) is resolved in RC8. My
> projects are building fine. Thanks!
>
> On Thu, Apr 3, 2008 at 12:51 PM, Brian E. Fox <br...@reply.infinity.nu>
> wrote:
> > RC8 posted to solve this regression.
> >
> > http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
> > che-maven/
> >
> >
> > -----Original Message-----
> > From: Kaizer H. Sogiawala [mailto:kaizers@gmail.com]
> >
> >
> > Sent: Thursday, April 03, 2008 2:51 PM
> > To: Maven Users List
> > Subject: Re: [2.0.9 RC7] Release Candidate testing
> >
> > I debugged through the source and can confirm
> > "<directory>${basedir}</directory>" is the issue.
> >
> > On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jd...@commonjava.org>
> > wrote:
> > > FWIW, using:
> > >
> > > <build>
> > > <directory>${basedir}</directory>
> > > </build>
> > >
> > > will express this error. See
> http://jira.codehaus.org/browse/MNG-3498
> > >
> > > I have the fix, just need to get it cleaned up and committed.
> > >
> > > -john
> > >
> > >
> > >
> > > On Apr 3, 2008, at 11:23 AM, Brett Porter wrote:
> > >
> > >
> > > > -1 could be empty string, and there were some hacks in the project
> > > > builder that set expressions to that. I know that the path
> > translator
> > > > was effected by interpolation changes, even though indirectly,
> > because
> > > > the values got interpolated after instead of before.
> > > >
> > > > I'd look at those changes - though a POM that reproduces it is
> > > > probably necessary to do so.
> > > >
> > > > - Brett
> > > >
> > > > On 04/04/2008, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > > >
> > > > > 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:kaizers@gmail.com]
> > > > > 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.alignToBaseDirectory
> > > > > (DefaultPathTranslator.java:82)
> > > > > at
> > > > >
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(
> > > > > DefaultMavenProjectBuilder.java:992)
> > > > > at
> > > > >
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul
> > > > > tMavenProjectBuilder.java:867)
> > > > > at
> > > > >
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI
> > > > > 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
> > <br...@reply.infinity.nu>
> > > > > 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: users-unsubscribe@maven.apache.org
> > > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > + Kaizer H. Sogiawala +
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > 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
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Brett Porter
> > > > Blog: http://blogs.exist.com/bporter/
> > > >
> > > >
> > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> > > ---
> > > John Casey
> > > Committer and PMC Member, Apache Maven
> > > mail: jdcasey at commonjava dot org
> > > blog: http://www.ejlife.net/blogs/john
> > > rss: http://feeds.feedburner.com/ejlife/john
> > >
> > >
> > >
> >
> >
> >
> > --
> > + Kaizer H. Sogiawala +
> >
> > ---------------------------------------------------------------------
> > 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
> >
> >
>
>
>
> --
> + Kaizer H. Sogiawala +
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [2.0.9 RC8] Release Candidate testing
Posted by "Kaizer H. Sogiawala" <ka...@gmail.com>.
+1
I can confirm that the issue
(http://jira.codehaus.org/browse/MNG-3498) is resolved in RC8. My
projects are building fine. Thanks!
On Thu, Apr 3, 2008 at 12:51 PM, Brian E. Fox <br...@reply.infinity.nu> wrote:
> RC8 posted to solve this regression.
>
> http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
> che-maven/
>
>
> -----Original Message-----
> From: Kaizer H. Sogiawala [mailto:kaizers@gmail.com]
>
>
> Sent: Thursday, April 03, 2008 2:51 PM
> To: Maven Users List
> Subject: Re: [2.0.9 RC7] Release Candidate testing
>
> I debugged through the source and can confirm
> "<directory>${basedir}</directory>" is the issue.
>
> On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jd...@commonjava.org>
> wrote:
> > FWIW, using:
> >
> > <build>
> > <directory>${basedir}</directory>
> > </build>
> >
> > will express this error. See http://jira.codehaus.org/browse/MNG-3498
> >
> > I have the fix, just need to get it cleaned up and committed.
> >
> > -john
> >
> >
> >
> > On Apr 3, 2008, at 11:23 AM, Brett Porter wrote:
> >
> >
> > > -1 could be empty string, and there were some hacks in the project
> > > builder that set expressions to that. I know that the path
> translator
> > > was effected by interpolation changes, even though indirectly,
> because
> > > the values got interpolated after instead of before.
> > >
> > > I'd look at those changes - though a POM that reproduces it is
> > > probably necessary to do so.
> > >
> > > - Brett
> > >
> > > On 04/04/2008, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > >
> > > > 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:kaizers@gmail.com]
> > > > 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.alignToBaseDirectory
> > > > (DefaultPathTranslator.java:82)
> > > > at
> > > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(
> > > > DefaultMavenProjectBuilder.java:992)
> > > > at
> > > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul
> > > > tMavenProjectBuilder.java:867)
> > > > at
> > > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI
> > > > 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
> <br...@reply.infinity.nu>
> > > > 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: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > + Kaizer H. Sogiawala +
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > 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
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Brett Porter
> > > Blog: http://blogs.exist.com/bporter/
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > ---
> > John Casey
> > Committer and PMC Member, Apache Maven
> > mail: jdcasey at commonjava dot org
> > blog: http://www.ejlife.net/blogs/john
> > rss: http://feeds.feedburner.com/ejlife/john
> >
> >
> >
>
>
>
> --
> + Kaizer H. Sogiawala +
>
> ---------------------------------------------------------------------
> 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
>
>
--
+ Kaizer H. Sogiawala +
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: [2.0.9 RC8] Release Candidate testing
Posted by Jason Chaffee <ja...@tvworks.com>.
Brian,
Is there any documentation about the new "locked down" plugin in feature
in 2.0.9?
I would like to know how it works, how it impacts not having plugins
locked vs. having them locked down already in your pom and how it would
impact the enforcer plugin as well.
Thanks.
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Thursday, April 03, 2008 12:52 PM
To: Maven Users List
Cc: Maven Developers List
Subject: [2.0.9 RC8] Release Candidate testing
RC8 posted to solve this regression.
http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa
che-maven/
-----Original Message-----
From: Kaizer H. Sogiawala [mailto:kaizers@gmail.com]
Sent: Thursday, April 03, 2008 2:51 PM
To: Maven Users List
Subject: Re: [2.0.9 RC7] Release Candidate testing
I debugged through the source and can confirm
"<directory>${basedir}</directory>" is the issue.
On Thu, Apr 3, 2008 at 8:42 AM, John Casey <jd...@commonjava.org>
wrote:
> FWIW, using:
>
> <build>
> <directory>${basedir}</directory>
> </build>
>
> will express this error. See http://jira.codehaus.org/browse/MNG-3498
>
> I have the fix, just need to get it cleaned up and committed.
>
> -john
>
>
>
> On Apr 3, 2008, at 11:23 AM, Brett Porter wrote:
>
>
> > -1 could be empty string, and there were some hacks in the project
> > builder that set expressions to that. I know that the path
translator
> > was effected by interpolation changes, even though indirectly,
because
> > the values got interpolated after instead of before.
> >
> > I'd look at those changes - though a POM that reproduces it is
> > probably necessary to do so.
> >
> > - Brett
> >
> > On 04/04/2008, Brian E. Fox <br...@reply.infinity.nu> wrote:
> >
> > > 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:kaizers@gmail.com]
> > > 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.alignToBaseDirectory
> > > (DefaultPathTranslator.java:82)
> > > at
> > >
>
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(
> > > DefaultMavenProjectBuilder.java:992)
> > > at
> > >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Defaul
> > > tMavenProjectBuilder.java:867)
> > > at
> > >
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileI
> > > 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
<br...@reply.infinity.nu>
> > > 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: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > + Kaizer H. Sogiawala +
> > >
> > >
---------------------------------------------------------------------
> > > 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
> > >
> > >
> > >
> >
> >
> > --
> > Brett Porter
> > Blog: http://blogs.exist.com/bporter/
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> ---
> John Casey
> Committer and PMC Member, Apache Maven
> mail: jdcasey at commonjava dot org
> blog: http://www.ejlife.net/blogs/john
> rss: http://feeds.feedburner.com/ejlife/john
>
>
>
--
+ Kaizer H. Sogiawala +
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org