[jira] Created: (JDO-634) M2 build process doesn't put correct MANIFEST.MF in jar file

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.

    [ https://issues.apache.org/jira/browse/JDO-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724593#action_12724593 ]

Craig Russell commented on JDO-634:
-----------------------------------

Might be that you just need a felix plugin to generate the OSGi information.

Were you thinking of another process? Besides the OSGI, what is desired?

> 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.

     [ 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.