You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jdo-dev@db.apache.org by "Michelle Caisse (JIRA)" <ji...@apache.org> on 2006/03/01 02:00:40 UTC

[jira] Updated: (JDO-312) manifest.mf must include Specification-Version

     [ http://issues.apache.org/jira/browse/JDO-312?page=all ]

Michelle Caisse updated JDO-312:
--------------------------------

    Attachment: JDO-312.patch

This patch adds two files to trunk: JDO20.MF and JDO11.MF.  These are manifest files that will be merged with the additional information that maven's jar plugin automatically adds to the manifest.  Each project's project.properties file sets maven.jar.manifest  to the .MF file with the appropriate Specification-Release. Note that the tck20 project.properties diff in this patch also contains the changes for JDO-316.

> manifest.mf must include Specification-Version
> ----------------------------------------------
>
>          Key: JDO-312
>          URL: http://issues.apache.org/jira/browse/JDO-312
>      Project: JDO
>         Type: Bug
>   Components: api20
>     Versions: JDO 2 beta
>     Reporter: Erik Bengtson
>     Assignee: Michelle Caisse
>     Priority: Trivial
>      Fix For: JDO 2 final
>  Attachments: JDO-312.patch
>
> the manifest.mf generated file does not include Specification-Version

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira