[
http://jira.codehaus.org/browse/MDEPLOY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189576#action_189576
]
Benjamin Bentmann commented on MDEPLOY-112:
-------------------------------------------
bq. I am using project.addAttachedArtifact(artifact); in my mojo to attach the
artifact
That's a valuable piece of info. Could you try calling
{{MavenProjectHelper.attachArtifact()}} instead of directly mutating the
project? Use something like
{code:java}
/**
* @component
*/
private MavenProjectHelper projectHelper;
{code}
to get the component injected into your mojo.
> deployed snapshot name has different build numbers for multiple artifacts of
> the same build
> -------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-112
> URL: http://jira.codehaus.org/browse/MDEPLOY-112
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
> Affects Versions: 2.2.1
> Environment: windows xp
> Reporter: Gabriel Dogaru
>
> I have a module that deploys 2 artifacts,1 jar and 1 of them is custom type.
> The build number from the snapshot name is different for the 2 (in the
> repository). It get incremented every time an artifact is deployed. When I
> try to make a local build it searches for the highest build number, and tries
> to bring both the artifacts with the latest build number but only one of them
> has that number.
> I found a workaround for this by <uniqueVersion>false</uniqueVersion> for
> the snapshotRepository.
--
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
