You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/11/01 16:59:45 UTC
[jira] Closed: (MNG-1335) Artifact must be cloned too in MavenProject's constructor
[ http://jira.codehaus.org/browse/MNG-1335?page=all ]
John Casey closed MNG-1335:
---------------------------
Resolution: Fixed
MavenProject now calls:
new DefaultArtifactFactory().cloneArtifact( project.artifact )
to make a copy of the project artifact. This (obviously) involved putting in the cloneArtifact(..) method (ArtifactFactory, DefaultArtifactFactory), implementing VersionRange.cloneOf(), and finally putting the aforementioned line of code into MavenProject.
> Artifact must be cloned too in MavenProject's constructor
> ---------------------------------------------------------
>
> Key: MNG-1335
> URL: http://jira.codehaus.org/browse/MNG-1335
> Project: Maven 2
> Type: Bug
> Components: maven-project
> Versions: 2.0
> Reporter: Vincent Massol
> Assignee: John Casey
> Fix For: 2.0.1
>
> Original Estimate: 30 minutes
> Time Spent: 30 minutes
> Remaining: 0 minutes
>
> In MavenProject.java, line 189 there is:
> // TODO: need to clone this too?
> this.artifact = project.artifact;
> The answer is yes. It seems that without the clone it is causing an issue when the clover plugin is used. After the clover mojos return the install phase fails to deploy the artifact as it points to some invalid location. That's probbaly because it's been overwritten by the clover mojos during the forked lifecycle.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org