Hi,
We will have our regular meeting Friday, June 26 at 9 am PDT to discuss
JDO TCK issues and status.
Dial-in numbers are:
Domestic (toll-free): 866 230-6968
International (caller-paid): +1 213 787-0528
Access code : 294-0479#
Agenda:
1. M2 build process doesn't put correct MANIFEST.MF in
[
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
[
https://issues.apache.org/jira/browse/JDO-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724602#action_12724602
]
Craig Russell commented on JDO-633:
---
Andy commented:
A List has an order (whether it is an
[
https://issues.apache.org/jira/browse/JDO-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724604#action_12724604
]
Craig Russell commented on JDO-633:
---
The specification update is trivial. The RI sounds stra
Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. M2 build process doesn't put correct MANIFEST.MF in jar file
https://issues.apache.org/jira/browse/JDO-634
Looks like it's easy to generate OSGi information in the manifest by
using the felix plugin. Anything besides the
[
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 th