Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 2.9
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Any eclipse SDK version
-
Patch Submitted:Yes
-
Number of attachments :
Description
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/source/3.4.3-R34x_v20081215-1030/source-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.
I reworked my previous patch to use the correct method layout, adding createClassifier(), reworking createGroupId() and createArtifactId() and adding to the unit tests.
I am attaching the following:
the command I executed to produce the two outputs is:
(Please discard the first upload of MECLIPSE-719.patch since it contains incorrect formatting of the unit tests file)