Maven 1.x Jar Plugin

Manifest file format and POM dependency: Vendor ID

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.8
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    1

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

Activity

Hide
Matt Finn added a comment -

Patch for plugins-build/jar/plugin.jelly to add vendorId to manifest dependencies

Show
Matt Finn added a comment - Patch for plugins-build/jar/plugin.jelly to add vendorId to manifest dependencies
Hide
Lukas Theussl added a comment -

Patch applied with small modification: the vendorId has to be set in the <properties> section of the dependency, so we don't have to modify the v3 pom. Thanks!

Show
Lukas Theussl added a comment - Patch applied with small modification: the vendorId has to be set in the <properties> section of the dependency, so we don't have to modify the v3 pom. Thanks!

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:

Time Tracking

Estimated:
4w
Original Estimate - 4 weeks
Remaining:
4w
Remaining Estimate - 4 weeks
Logged:
Not Specified
Time Spent - Not Specified