Hello,
I'm trying to figure out why Maven does not work well for Cocoon project
(see [1] and [2]). I think situation described in [1] is caused by
MNG-2302 bug. So i tried to use Maven 2.0.5-SNAPSHOT version (checked
out today) and it seems still to be buggy. This time Maven fails to
build whole POM depedency graph. Speaking more plainly, parents are
never pointed correctly.
This snippet of DefaultMavenProjectBuilder.java[3] fails:
MavenProject rawParent = project.getParent();
if ( rawParent != null )
{
String cacheKey = createCacheKey( rawParent.getGroupId(),
rawParent.getArtifactId(), rawParent.getVersion() );
MavenProject processedParent = (MavenProject)
processedProjectCache.get( cacheKey );
// yeah, this null check might be a bit paranoid, but better
safe than sorry...
if ( processedParent != null )
{
project.setParent( processedParent );
}
}
In particular situation processedParent *IS* null. Do I think correctly
that this is definitely not expected situation?
[1] https://issues.apache.org/jira/browse/COCOON-1975
[2] http://thread.gmane.org/gmane.text.xml.cocoon.devel/69132/focus=69132
[3]
http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.x/maven-project/src/main/java/org/apache/maven/project/DefaultMavenProjectBuilder.java?view=markup
--
Best regards
Grzegorz Kossakowski
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
