db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Jefferson (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JDO-634) M2 build process doesn't put correct MANIFEST.MF in jar file
Date Fri, 26 Jun 2009 16:57:47 GMT

     [ https://issues.apache.org/jira/browse/JDO-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andy Jefferson resolved JDO-634.
--------------------------------

    Resolution: Fixed

I simply thought of the fact that the API2.MF was not used as the MANIFEST.MF in the generated
jar (when building using M2) so it was unusable for anything OSGi. Fixed this in SVN trunk
few days ago but forgot to close this

> M2 build process doesn't put correct MANIFEST.MF in jar file
> ------------------------------------------------------------
>
>                 Key: JDO-634
>                 URL: https://issues.apache.org/jira/browse/JDO-634
>             Project: JDO
>          Issue Type: Bug
>          Components: api2
>            Reporter: Andy Jefferson
>            Assignee: Andy Jefferson
>             Fix For: JDO 2 maintenance release 3
>
>
> It doesn't bother specifying the MANIFEST.MF in the pom.xml (whereas with M1 it is defined
in project.properties)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message