The following comment has been added to this issue:
Author: Brett Porter
Created: Tue, 28 Dec 2004 3:06 AM
Body:
there is more information in MAVEN-1461
Also from the mailing list:
---
I am currently working on a larger project with several subprojects.
For building the whole thing (an ear file by the way) we are using
a reactor to build all subprojects.
On Windows everything works just fine, but if I run the same reactor
on a Linux box it fails. After some investigation I've found that the
processing order under Linux is wrong and it tries to build one of the
subprojects prior to building a dependend subproject. By the way on both
boxes we are using maven 1.0.2.
I started to search Jira and came across this bug:
http://jira.codehaus.org/browse/MAVEN-1461
I've tried to build the project by specifying
-Dmaven.core.dependencyresolver=org.apache.maven.jelly.tags.maven.GraphDependencyResolver
and the processing
order on Linux changes. However, it is still wrong.
Does anyone has an idea? I see if I can get some time to create a test
harness for this behaviour.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MAVEN-1235?page=comments#action_28369
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MAVEN-1235
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1235
Summary: Performance problem with Maven reactor on Solaris
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Versions:
1.0-beta-10
1.0-rc3
1.0-rc1
1.0-rc2
Assignee:
Reporter: Vincent Massol
Created: Wed, 14 Apr 2004 5:01 AM
Updated: Tue, 28 Dec 2004 3:06 AM
Description:
Context:
We have about 58 Maven projects. Each project has about 85 dependencies. About
50 of these are dependencies to external jars. The rest are inter-project
dependencies.
Problem:
When running the Maven reactor on windows machine. The reactor correctly and
relatively quickly (30-40 seconds) finds out the ordered list of projects to
run. However, on Solaris, it takes about 215 minutes (almost 4 hours!) to find
out the ordered list of projects.
Analysis:
It seems the problem is somewhere in the werkz code. When using a profiling
tool, 100% of the time is spent in the Goal.addPrecusor method (which takes as
an average about 1 minute per project per dependency to run). I don't see how
the problem could be in werkz. But still the profiling tool points there.
Could it be the checkForCycle which is somehow having recursivity problems on
Solaris?
Any idea?
Thanks
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
