Gabriele Catania created MECLIPSE-719:
-----------------------------------------
Summary: to-maven mojo does not handle source bundles correctly
Key: MECLIPSE-719
URL: https://jira.codehaus.org/browse/MECLIPSE-719
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Affects Versions: 2.9
Environment: Any eclipse SDK version
Reporter: Gabriele Catania
Priority: Minor
Attachments: handle-sources.patch
the to-maven mojo does not install source bundles according to maven
conventions. For example, the following plugins:
# {{org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar}}
# {{org.eclipse.osgi.source_3.4.3.R34x_v20081215-1030.jar}}
should be deployed respectively to:
#
{{M2_REPO/org/eclipse/osgi/3.4.3-R34x_v20081215-1030/osgi-3.4.3-R34x_v20081215-1030.jar}}
#
{{M2_REPO/org/eclipse/osgi/3.4.3-R34x_v20081215-1030/osgi-3.4.3-R34x_v20081215-1030-sources.jar}}
instead, they are deployed here:
#
{{M2_REPO/org/eclipse/osgi/3.4.3-R34x_v20081215-1030/osgi-3.4.3-R34x_v20081215-1030.jar}}
#
{{M2_REPO/org/eclipse/osgi/}}{color:red}{{source/}}{color}{{3.4.3-R34x_v20081215-1030/}}{color:red}{{source}}{color}{{-3.4.3-R34x_v20081215-1030.jar}}
To test this behaviour, I downloaded an eclipse sdk and ran the to-maven mojo
in its unpacked installation directory
I am attaching a quick patch I devised to set the "sources" classifier on
plugins whose name ends with ".source". I tried to minimize code changes, a
revised implementation should probably modify {{createGroupId()}} and
{{createArtifactId()}}, and avoid installing the pom for the sources jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
