[ http://jira.codehaus.org/browse/MPJAR-15?page=all ]
Lukas Theussl closed MPJAR-15:
------------------------------
Assign To: Lukas Theussl
Resolution: Fixed
Fix Version: 1.8
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!
> Manifest file format and POM dependency: Vendor ID
> --------------------------------------------------
>
> Key: MPJAR-15
> URL: http://jira.codehaus.org/browse/MPJAR-15
> Project: maven-jar-plugin
> Type: Improvement
> Reporter: Matt Finn
> Assignee: Lukas Theussl
> Priority: Minor
> Fix For: 1.8
> Attachments: plugin.jelly.patch.txt
>
> Original Estimate: 4 weeks
> Remaining: 4 weeks
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
