[jira] (MDEPLOY-163) Maven Deploy Plugin Deploys Attached Sources A Second Time
[
https://jira.codehaus.org/browse/MDEPLOY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=332984#comment-332984
]
Jonathon Golden commented on MDEPLOY-163:
-
Hi Robert,
The attach artifact would not work in my case. The artifacts I need to deploy
do not necessarily have the same groupId.
Maven Deploy Plugin Deploys Attached Sources A Second Time
--
Key: MDEPLOY-163
URL: https://jira.codehaus.org/browse/MDEPLOY-163
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy-file
Affects Versions: 2.7
Environment: 64 Bit Linux
Reporter: Jonathon Golden
Assignee: Robert Scholte
This happens in a jar pom where I have attached sources to the jar thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-source-plugin/artifactId
executions
execution
idattach-sources-/id
phasecompile/phase
goals
goaljar-no-fork/goal
/goals
/execution
/executions
/plugin
{code}
When running the deploy phase this will result in the source jar being
deployed to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to
workaround this bug) deployment of additional configuration artifacts thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
iddeploy-REDACTED/id
phasedeploy/phase
configuration
groupIdREDACTED/groupId
artifactIdREDACTED/artifactId
version${project.version}/version
fileREDACTED/file
packagingxml/packaging
generatePomtrue/generatePom
repositoryIdnexus/repositoryId
urlhttp://nexus:8081/content/repositories/${deployment.repository.suffix}/url
/configuration
goals
goaldeploy-file/goal
/goals
/execution
/executions
/plugin
{code}
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEPLOY-163) Maven Deploy Plugin Deploys Attached Sources A Second Time
[
https://jira.codehaus.org/browse/MDEPLOY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MDEPLOY-163.
--
Resolution: Won't Fix
Assignee: Robert Scholte
The {{deploy-file}} is meant for direct invocation, meaning from cmdline and
not as part of the build lifecycle. If you want to add additional artifacts
during deploy, you should use
[build-helper:attach-artifact|http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html].
It binds to the correct phase and requires a minimum of configuration.
Maven Deploy Plugin Deploys Attached Sources A Second Time
--
Key: MDEPLOY-163
URL: https://jira.codehaus.org/browse/MDEPLOY-163
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy-file
Affects Versions: 2.7
Environment: 64 Bit Linux
Reporter: Jonathon Golden
Assignee: Robert Scholte
This happens in a jar pom where I have attached sources to the jar thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-source-plugin/artifactId
executions
execution
idattach-sources-/id
phasecompile/phase
goals
goaljar-no-fork/goal
/goals
/execution
/executions
/plugin
{code}
When running the deploy phase this will result in the source jar being
deployed to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to
workaround this bug) deployment of additional configuration artifacts thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
iddeploy-REDACTED/id
phasedeploy/phase
configuration
groupIdREDACTED/groupId
artifactIdREDACTED/artifactId
version${project.version}/version
fileREDACTED/file
packagingxml/packaging
generatePomtrue/generatePom
repositoryIdnexus/repositoryId
urlhttp://nexus:8081/content/repositories/${deployment.repository.suffix}/url
/configuration
goals
goaldeploy-file/goal
/goals
/execution
/executions
/plugin
{code}
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEPLOY-163) Maven Deploy Plugin Deploys Attached Sources A Second Time
[
https://jira.codehaus.org/browse/MDEPLOY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=332987#comment-332987
]
Robert Scholte commented on MDEPLOY-163:
[~jonathon.golden], in that case it is probably better to make it a multimodule
project.
Maven Deploy Plugin Deploys Attached Sources A Second Time
--
Key: MDEPLOY-163
URL: https://jira.codehaus.org/browse/MDEPLOY-163
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy-file
Affects Versions: 2.7
Environment: 64 Bit Linux
Reporter: Jonathon Golden
Assignee: Robert Scholte
This happens in a jar pom where I have attached sources to the jar thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-source-plugin/artifactId
executions
execution
idattach-sources-/id
phasecompile/phase
goals
goaljar-no-fork/goal
/goals
/execution
/executions
/plugin
{code}
When running the deploy phase this will result in the source jar being
deployed to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to
workaround this bug) deployment of additional configuration artifacts thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
iddeploy-REDACTED/id
phasedeploy/phase
configuration
groupIdREDACTED/groupId
artifactIdREDACTED/artifactId
version${project.version}/version
fileREDACTED/file
packagingxml/packaging
generatePomtrue/generatePom
repositoryIdnexus/repositoryId
urlhttp://nexus:8081/content/repositories/${deployment.repository.suffix}/url
/configuration
goals
goaldeploy-file/goal
/goals
/execution
/executions
/plugin
{code}
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEPLOY-163) Maven Deploy Plugin Deploys Attached Sources A Second Time
Jonathon Golden created MDEPLOY-163:
---
Summary: Maven Deploy Plugin Deploys Attached Sources A Second Time
Key: MDEPLOY-163
URL: https://jira.codehaus.org/browse/MDEPLOY-163
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy-file
Affects Versions: 2.7
Environment: 64 Bit Linux
Reporter: Jonathon Golden
This happens in a jar pom where I have attached sources to the jar thus:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-source-plugin/artifactId
executions
execution
idattach-sources-/id
phasecompile/phase
goals
goaljar-no-fork/goal
/goals
/execution
/executions
/plugin
When running the deploy phase this will result in the source jar being deployed
to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to workaround
this bug) deployment of additional configuration artifacts thus:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
iddeploy-REDACTED/id
phasedeploy/phase
configuration
groupIdREDACTED/groupId
artifactIdREDACTED/artifactId
version${project.version}/version
fileREDACTED/file
packagingxml/packaging
generatePomtrue/generatePom
repositoryIdnexus/repositoryId
urlhttp://nexus:8081/content/repositories/${deployment.repository.suffix}/url
/configuration
goals
goaldeploy-file/goal
/goals
/execution
/executions
/plugin
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEPLOY-163) Maven Deploy Plugin Deploys Attached Sources A Second Time
[
https://jira.codehaus.org/browse/MDEPLOY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathon Golden updated MDEPLOY-163:
Description:
This happens in a jar pom where I have attached sources to the jar thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-source-plugin/artifactId
executions
execution
idattach-sources-/id
phasecompile/phase
goals
goaljar-no-fork/goal
/goals
/execution
/executions
/plugin
{code}
When running the deploy phase this will result in the source jar being deployed
to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to workaround
this bug) deployment of additional configuration artifacts thus:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
iddeploy-REDACTED/id
phasedeploy/phase
configuration
groupIdREDACTED/groupId
artifactIdREDACTED/artifactId
version${project.version}/version
fileREDACTED/file
packagingxml/packaging
generatePomtrue/generatePom
repositoryIdnexus/repositoryId
urlhttp://nexus:8081/content/repositories/${deployment.repository.suffix}/url
/configuration
goals
goaldeploy-file/goal
/goals
/execution
/executions
/plugin
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
was:
This happens in a jar pom where I have attached sources to the jar thus:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-source-plugin/artifactId
executions
execution
idattach-sources-/id
phasecompile/phase
goals
goaljar-no-fork/goal
/goals
/execution
/executions
/plugin
When running the deploy phase this will result in the source jar being deployed
to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to workaround
this bug) deployment of additional configuration artifacts thus:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
iddeploy-REDACTED/id
phasedeploy/phase
configuration
groupIdREDACTED/groupId
artifactIdREDACTED/artifactId
version${project.version}/version
fileREDACTED/file
packagingxml/packaging
generatePomtrue/generatePom
repositoryIdnexus/repositoryId
urlhttp://nexus:8081/content/repositories/${deployment.repository.suffix}/url
/configuration
goals
goaldeploy-file/goal
/goals
/execution
/executions
/plugin
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
Maven Deploy Plugin Deploys Attached Sources A Second Time
--
Key: MDEPLOY-163
URL: https://jira.codehaus.org/browse/MDEPLOY-163
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy-file
Affects Versions: 2.7
Environment: 64 Bit Linux
Reporter: Jonathon Golden
This happens in a jar pom where I have attached sources to the jar thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-source-plugin/artifactId
executions
execution
idattach-sources-/id
phasecompile/phase
goals
goaljar-no-fork/goal
/goals
[jira] (MDEPLOY-163) Maven Deploy Plugin Deploys Attached Sources A Second Time
[
https://jira.codehaus.org/browse/MDEPLOY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathon Golden updated MDEPLOY-163:
Description:
This happens in a jar pom where I have attached sources to the jar thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-source-plugin/artifactId
executions
execution
idattach-sources-/id
phasecompile/phase
goals
goaljar-no-fork/goal
/goals
/execution
/executions
/plugin
{code}
When running the deploy phase this will result in the source jar being deployed
to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to workaround
this bug) deployment of additional configuration artifacts thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
iddeploy-REDACTED/id
phasedeploy/phase
configuration
groupIdREDACTED/groupId
artifactIdREDACTED/artifactId
version${project.version}/version
fileREDACTED/file
packagingxml/packaging
generatePomtrue/generatePom
repositoryIdnexus/repositoryId
urlhttp://nexus:8081/content/repositories/${deployment.repository.suffix}/url
/configuration
goals
goaldeploy-file/goal
/goals
/execution
/executions
/plugin
{code}
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
was:
This happens in a jar pom where I have attached sources to the jar thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-source-plugin/artifactId
executions
execution
idattach-sources-/id
phasecompile/phase
goals
goaljar-no-fork/goal
/goals
/execution
/executions
/plugin
{code}
When running the deploy phase this will result in the source jar being deployed
to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to workaround
this bug) deployment of additional configuration artifacts thus:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
iddeploy-REDACTED/id
phasedeploy/phase
configuration
groupIdREDACTED/groupId
artifactIdREDACTED/artifactId
version${project.version}/version
fileREDACTED/file
packagingxml/packaging
generatePomtrue/generatePom
repositoryIdnexus/repositoryId
urlhttp://nexus:8081/content/repositories/${deployment.repository.suffix}/url
/configuration
goals
goaldeploy-file/goal
/goals
/execution
/executions
/plugin
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
Maven Deploy Plugin Deploys Attached Sources A Second Time
--
Key: MDEPLOY-163
URL: https://jira.codehaus.org/browse/MDEPLOY-163
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy-file
Affects Versions: 2.7
Environment: 64 Bit Linux
Reporter: Jonathon Golden
This happens in a jar pom where I have attached sources to the jar thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-source-plugin/artifactId
executions
execution
idattach-sources-/id
phasecompile/phase
goals
goaljar-no-fork/goal
[jira] (MDEPLOY-163) Maven Deploy Plugin Deploys Attached Sources A Second Time
[
https://jira.codehaus.org/browse/MDEPLOY-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=330737#comment-330737
]
Jonathon Golden commented on MDEPLOY-163:
-
I just ran into the same problem when using deploy-file in a pom that was using
the maven-assembly-plugin. I set the attach to false and the problem went away
(I don't need the assembly deployed to my repository in this case) But i would
say this reveals that the problem is that the deploy-file goal should not
attempt to deploy attached artifacts since it is supposed to be used for
explicitly specified artifacts.
Maven Deploy Plugin Deploys Attached Sources A Second Time
--
Key: MDEPLOY-163
URL: https://jira.codehaus.org/browse/MDEPLOY-163
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy-file
Affects Versions: 2.7
Environment: 64 Bit Linux
Reporter: Jonathon Golden
This happens in a jar pom where I have attached sources to the jar thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-source-plugin/artifactId
executions
execution
idattach-sources-/id
phasecompile/phase
goals
goaljar-no-fork/goal
/goals
/execution
/executions
/plugin
{code}
When running the deploy phase this will result in the source jar being
deployed to the repository (nexus in my case) in the normal fashion.
I also had in the same pom (I've since moved it to another module to
workaround this bug) deployment of additional configuration artifacts thus:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-deploy-plugin/artifactId
executions
execution
iddeploy-REDACTED/id
phasedeploy/phase
configuration
groupIdREDACTED/groupId
artifactIdREDACTED/artifactId
version${project.version}/version
fileREDACTED/file
packagingxml/packaging
generatePomtrue/generatePom
repositoryIdnexus/repositoryId
urlhttp://nexus:8081/content/repositories/${deployment.repository.suffix}/url
/configuration
goals
goaldeploy-file/goal
/goals
/execution
/executions
/plugin
{code}
When the deploy-file goal executes it will succeed to deploy the xml file but
for some reason it is also attempting to upload the jar sources a second time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
