Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.8
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
Hi,
I would like to continue the discussion about the extension versioning formatting in the manifest. I am using turbine2-dev and tomcat, and when tomcat attempts the match required optional packages to available packages, it requires the Implementation-Vendor-Id attribute in the manifest to match. This is in accordance with the java extension versioning specification at
http://java.sun.com/j2se/1.3/docs/guide/extensions/versioning.html
Correcting this problem would involve moving toward requiring a <vendorId> element within the dependency element in project.xml files.
Then in the jar/plugin.jelly you would add the vendor id attribute when it generates the manifest.
I have attached a patch for the plugin.jelly, and I hope we can move toward adding the vendorId element to the POM.
Thanks,
matt
Patch for plugins-build/jar/plugin.jelly to add vendorId to manifest dependencies