[
https://jira.codehaus.org/browse/MDEPLOY-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Hladky reopened MDEPLOY-184:
----------------------------------
Thank you for checking this issue. Your successful attempt made me test it
again. Please, make sure to use different name for the pom file, such as
mvn deploy:deploy-file -Dfile=download-manager-2.0.8.war
-DrepositoryId=jboss.repo -DpomFile=pom.xml
-Dsources=download-manager-2.0.8-sources.jar
-Djavadoc=download-manager-2.0.8-javadoc.jar
-Durl=http://localhost:8081/content/repositories/releases
That way pom is deployed as it should (as download-manager-2.0.8.pom), but
sources and javadoc are not deployed. If I use download-manager-2.0.8.pom as a
source, javadoc and sources are deployed properly.
> Sources and Javadoc are not added when deploying
> ------------------------------------------------
>
> Key: MDEPLOY-184
> URL: https://jira.codehaus.org/browse/MDEPLOY-184
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy-file
> Affects Versions: 2.8.1
> Environment: Apache Maven 3.1.1
> (NON-CANONICAL_2013-11-08_14-32_mockbuild; 2013-11-08 15:32:41+0100)
> Fedora 20
> Reporter: David Hladky
> Assignee: Robert Scholte
>
> Based on the documentation adding -Dsources=somefile and -Djavadoc=somefile
> the files should be added to the target reposiotry based on the
> documentation. While deploy:deploy deploys the sources and javadoc properly,
> deploy-file ignores the sources.
> Someone complained about this problem here as well:
> http://stackoverflow.com/questions/7487130/deploying-an-artifact-its-sources-and-javadoc-using-mavens-deploydeploy-file
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
