[jira] Commented: (MDEPLOY-112) deployed snapshot name has different build numbers for multiple artifacts of the same build
[ http://jira.codehaus.org/browse/MDEPLOY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=189639#action_189639 ] Gabriel Dogaru commented on MDEPLOY-112: I tried that . if i use MavenProjectHelper.attachArtifact() the artifacts do not have timestamp or build number. They get deployed the same way as using uniqueVersion=false. The reason why I didn't use MavenProjectHelper the first time is that for some projects I needed to create artifacts with a different name than project.name, and there is no MavenProjectHelper.attachArtifact() that would accept artifactId as parameter. Also I couldn't (still can't) use AttachedArtifact in project.addAttachedArtifact(artifact) as it is used in MavenProjectHelper because of some dependency conflict (I use gmaven 1.0-rc-4 and maven 2.2.1) and I used instead DefaultArtifact. I guess that is not a problem since they both implement Artifact. 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 uniqueVersionfalse/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
[jira] Commented: (MDEPLOY-112) deployed snapshot name has different build numbers for multiple artifacts of the same build
[ http://jira.codehaus.org/browse/MDEPLOY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=189541#action_189541 ] Benjamin Bentmann commented on MDEPLOY-112: --- An example POM or at least the relevant lines from the log output where Maven prints what it deploys would be helpful. 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 uniqueVersionfalse/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
[jira] Commented: (MDEPLOY-112) deployed snapshot name has different build numbers for multiple artifacts of the same build
[
http://jira.codehaus.org/browse/MDEPLOY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=189575#action_189575
]
Gabriel Dogaru commented on MDEPLOY-112:
[04:41:21]: [INFO] [deploy:deploy {execution: default-deploy}]
[04:41:21]: [INFO] No primary artifact to deploy, deploy attached artifacts
instead.
[04:41:21]: [INFO] Retrieving previous build number from snapshots_repo
[04:41:21]: Uploading:
file:build/m2repository/snapshots/myapp/testutils/11.6-SNAPSHOT/testutils-11.6-20090902.084121-24.jar
[04:41:21]: 78K uploaded (testutils-11.6-20090902.084121-24.jar)
[04:41:21]: [INFO] Retrieving previous metadata from snapshots_repo
[04:41:21]: [INFO] Uploading repository metadata for: 'artifact myapptestutils'
[04:41:21]: [INFO] Retrieving previous metadata from snapshots_repo
[04:41:21]: [INFO] Uploading repository metadata for: 'snapshot
myapp:testutils:11.6-SNAPSHOT'
[04:41:21]: [INFO] Retrieving previous build number from snapshots_repo
[04:41:21]: Uploading:
file:build/m2repository/snapshots/myapp/testutils/11.6-SNAPSHOT/testutils-11.6-20090902.084121-25.resource
[04:41:21]: 2K uploaded (testutils-11.6-20090902.084121-25.resource)
[04:41:21]: [INFO] Retrieving previous metadata from snapshots_build
[04:41:22]: [INFO] Uploading repository metadata for: 'artifact myapp:testutils'
[04:41:22]: [INFO] Retrieving previous metadata from snapshots_repo
[04:41:22]: [INFO] Uploading repository metadata for: 'snapshot
myapp:testutils:11.6-SNAPSHOT'
[04:41:22]: [INFO]
[04:41:22]: [INFO] BUILD SUCCESSFUL
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 uniqueVersionfalse/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
[jira] Commented: (MDEPLOY-112) deployed snapshot name has different build numbers for multiple artifacts of the same build
[
http://jira.codehaus.org/browse/MDEPLOY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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 uniqueVersionfalse/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
