[#MNG-2061] DistributionManagement properties don't get copied in cloned executionProject while lifecycle fork - jira.codehaus.org

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 2.0.2
Fix Version/s: 2.0.8
Component/s: Plugins and Lifecycle
Labels:
None

Complexity:
Intermediate
Number of attachments :
1

Description

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.

More Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

MNG-2061-maven-project.patch

28/Aug/07 6:34 AM

3 kB

jan ancajas

Activity

Hide

Permalink

jan ancajas added a comment - 28/Aug/07 6:34 AM

attached patch and unit test.

releaseArtifactRepository and snapshotArtifactRepository fields are not copied to the cloned MavenProject object when the project lifecycle is forked.

(thanks brett.

Show

jan ancajas added a comment - 28/Aug/07 6:34 AM attached patch and unit test. releaseArtifactRepository and snapshotArtifactRepository fields are not copied to the cloned MavenProject object when the project lifecycle is forked. (thanks brett.

People

Assignee:

Brett Porter

Reporter:

Max Feldman

Vote (0)

Watch (2)

Dates

Created:

10/Feb/06 11:04 AM

Updated:

06/Sep/07 8:39 PM

Resolved:

06/Sep/07 8:39 PM

Maven 2 & 3

DistributionManagement properties don't get copied in cloned executionProject while lifecycle fork