Well, I'm not really sure if it might just be my env - would want
confirmation from someone else first.
Here it is anyway...
[INFO]
------------------------------------------------------------------------
[INFO] Building Unnamed - org.apache.maven.its.mng3694:project:jar:1
[INFO] task-segment: [clean:clean, validate]
[INFO]
------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] [mng3694:check {execution: test}]
Compile-source roots for project: MavenProject:
org.apache.maven.its.mng3694:not-used:1 @ /Users/brett/scm/maven/
maven-2.0.10-RC/maven-core-it-runner
/target/it-working-folder/mng-3694-reactorProjectsDynamism/projects/
not-used/pom.xml are: [${project.basedir}/src/main/java]
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Source root: ${project.basedir}/src/main/java doesn't begin
with project basedir: /Users/brett/scm/maven/maven-2.0.10-RC/maven-
core-it-runner/target/it-working-folder/mng-3694-
reactorProjectsDynamism/projects/not-used
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Source root: $
{project.basedir}/src/main/java doesn't begin with project basedir: /
Users/brett/scm/maven/maven-2.0.10-RC/maven-core-it-runner/target/it-
working-folder/mng-3694-reactorProjectsDynamism/projects/not-used
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
651)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor
.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:532)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:511)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor
.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:363)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor
.executeTaskSegments(DefaultLifecycleExecutor.java:324)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:175)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:302)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun
.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
39)
at
sun
.reflect
.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Source
root: ${project.basedir}/src/main/java doesn't begin with project
basedir: /Users/brett/scm/maven/maven-2.0.10-RC/maven-core-it-runner/
target/it-working-folder/mng-3694-reactorProjectsDynamism/projects/not-
used
at plugin.MyMojo.execute(MyMojo.java:56)
at
org
.apache
.maven
.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:461)
at
org
.apache
.maven
.lifecycle
.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
626)
... 16 more
On 09/08/2008, at 1:03 AM, John Casey wrote:
I guess reopen that issue, and I'll have a look. If you have a
stacktrace or the log.txt from the IT run that you could post, it'd
probably help.
Thanks,
-john
Brett Porter wrote:
I am still getting a failure from
MavenITmng3694ReactorProjectsDynamismTest though - is that known?
Cheers,
Brett
On 08/08/2008, at 2:08 PM, Brett Porter wrote:
On 08/08/2008, at 8:33 AM, [EMAIL PROTECTED] wrote:
Author: jdcasey
Date: Thu Aug 7 15:33:15 2008
New Revision: 683740
URL: http://svn.apache.org/viewvc?rev=683740&view=rev
Log:
[MNG-3698] Moved concrete/dynamic transitions out to the
lifecycle executor to make them happen less often, and added code
to check whether reactorProjects are used or reachable (via
session parameter) before calculating their concrete state
blindly. Also, conserving the RegexBasedInterpolator (the class
from plexus-interpolator) to keep from reconstructing the Pattern
instance inside it repeatedly. Added a buffer size to the
StringWriter used in the interpolator, and finally changed the
concrete calculation to avoid some needless project-instance
cloning (which as it turns out is wrong...see MNG-3700).
Performance is significantly improved, and memory usage has been
cut from what it used in 2.0.9.
Very nicely done John!
This has fixed the OOME problems I was having with 2.0.9, as well
as taking >2 minutes off my 2.0.9 build.
I've put MNG-3584 back into 2.0.10 so you can mark it fixed - it
might be good to reach out to the poster in the issue to see if it
works in his env too.
Thanks!
Cheers,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
