You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/02/10 18:49:47 UTC
[jira] Updated: (MNG-2061) DistributionManagement properties don't
get copied in cloned executionProject while lifecycle fork
[ http://jira.codehaus.org/browse/MNG-2061?page=all ]
Brett Porter updated MNG-2061:
------------------------------
Fix Version: 2.0.3
> DistributionManagement properties don't get copied in cloned executionProject while lifecycle fork
> --------------------------------------------------------------------------------------------------
>
> Key: MNG-2061
> URL: http://jira.codehaus.org/browse/MNG-2061
> Project: Maven 2
> Type: Bug
> Components: Plugins and Lifecycle
> Versions: 2.0.2
> Reporter: Max Feldman
> Fix For: 2.0.3
>
>
> Define a new Maven plugin with the goal described like this:
> /**
> * @execute phase="deploy"
> * @goal deploy-custom
> */
> When running 'mvn deploy-custom', deploy phase execution fails with 'Class 'org.apache.maven.artifact.repository.ArtifactRepository' cannot be instantiated'.
> It seems the problem raises from the fact that releaseArtifactRepository/snapshotArtifactRepository don't get copied in the cloned executionProject while lifecycle fork.
--
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