You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2006/01/28 05:07:06 UTC
[jira] Closed: (MPJAR-51) REDUX: Specification-Version and
Implementation-Vendor-Id not being set
[ http://jira.codehaus.org/browse/MPJAR-51?page=all ]
Carlos Sanchez closed MPJAR-51:
-------------------------------
Assign To: Carlos Sanchez
Resolution: Duplicate
Dupe of MPJAR-39
> REDUX: Specification-Version and Implementation-Vendor-Id not being set
> -----------------------------------------------------------------------
>
> Key: MPJAR-51
> URL: http://jira.codehaus.org/browse/MPJAR-51
> Project: maven-jar-plugin
> Type: Bug
> Reporter: Robert Burrell Donkin
> Assignee: Carlos Sanchez
>
>
> http://jira.codehaus.org/browse/MPJAR-7?rc=1 commented out code to set the Specification-Version manifect attribute. There seems to have been quite a bit of debate about that bug. The result seems to be that the code was commented out http://svn.apache.org/viewcvs.cgi/maven/maven-1/plugins/trunk/jar/plugin.jelly?rev=115072&r1=115041&r2=115072&diff_format=h so that the RC3 could ship and a more permenent solution found later. It's still there.
> Specification-Version should really be set for libraries: IIRC there are some fancy EJB library loading routines which rely on it. Personally speaking, I'd be happen to uncomment the commented line.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org