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 "Matthew T. Adams (JIRA)" <ji...@apache.org> on 2011/08/30 21:13:42 UTC
[jira] [Created] (JDO-684) Fix OSGi Export-Package entries in
manifest to include version
Fix OSGi Export-Package entries in manifest to include version
--------------------------------------------------------------
Key: JDO-684
URL: https://issues.apache.org/jira/browse/JDO-684
Project: JDO
Issue Type: Bug
Components: api
Affects Versions: JDO 3
Reporter: Matthew T. Adams
The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
Patch to follow bug submission.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in
manifest to include version
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: JDO-684.patch
This patch is relative to branches/3.0. It adds the version specification to the Export-Package manifest entry and revs the JDO version from 3.0 to 3.0.1
> Fix OSGi Export-Package entries in manifest to include version
> --------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: JDO-684.patch
Reviewed JDO-673 on conf call, so reverted JPA dependency range back to [1.0.0,2.0.0).
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Michael Bouschen (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119943#comment-13119943 ]
Michael Bouschen commented on JDO-684:
--------------------------------------
The patch JDO-684.3.patch looks good.
Just come comments:
- The Bundle-Vendor should be Apache Software Foundation
- How about adding a Bundle-Licence entry: Bundle-Licence: Apache Software Licence 2.0
- Does it make sense to mark the follwing imports as optional, since they are provided by the Java runtime system (meaning the system bundle): javax.rmi, javax.xml.parsers, org.w3c.dom, org.xml.sax;
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.3.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: JDO-684.patch
Now using version range "[1.0.0,3.0.0)" for javax.persistence.
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094721#comment-13094721 ]
Andy Jefferson commented on JDO-684:
------------------------------------
Bit like this then
http://www.datanucleus.org/downloads/maven2/javax/jdo/jdo-api/3.0.0/
Judging by time taken to get a release, I knocked that one together back in October last year.
=> Apply it, and arrange a release
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Craig L Russell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122408#comment-13122408 ]
Craig L Russell commented on JDO-684:
-------------------------------------
Looks good. Just one minor question. The patch updates api/API3.MF which looks fine.
But it also updates API3.MF. Is this file obsolete? Most of the changes do not appear in this file...
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122853#comment-13122853 ]
Matthew T. Adams commented on JDO-684:
--------------------------------------
@Craig, I take you meant that it also updates api/../JDO3.MF. I included a change to that file for completeness.
It's used in tck/project.properties, line 21: maven.jar.manifest = ${basedir}/../JDO3.MF
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: (was: JDO-684.patch)
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: (was: JDO-684.patch)
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: JDO-684.patch
Incorporated changes from conf call feedback on 7 Oct '11. Please review. Once approved, I'll commit & begin release process.
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: (was: JDO-684.3.patch)
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-684) Fix OSGi Export-Package entries in
manifest to include version
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094013#comment-13094013 ]
Matthew T. Adams commented on JDO-684:
--------------------------------------
It looks like this has already been fixed in the trunk for JDO 3.1.
> Fix OSGi Export-Package entries in manifest to include version
> --------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: (was: JDO-684.patch)
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.3.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen updated JDO-684:
---------------------------------
Fix Version/s: JDO 3 update 1
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen reassigned JDO-684:
------------------------------------
Assignee: Matthew T. Adams
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Summary: Fix OSGi Export-Package entries in JDO 3.0 manifest to include version (was: Fix OSGi Export-Package entries in manifest to include version)
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: JDO-684.patch
@Michael,
* Bundle-Vendor changed to "Apache Software Foundation"
* Bundle-License added
* javax.rmi, javax.xml.parsers, org.w3c.dom & org.xml.sax are no longer optional
Patch tested & attached.
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: (was: JDO-684.patch)
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Commented] (JDO-684) Fix OSGi Export-Package entries in
JDO 3.0 manifest to include version
Posted by Matthew Adams <ma...@matthewadams.me>.
Sir, yes sir. I will take said steps & correct or report back any errors.
On Mon, Sep 5, 2011 at 12:52 PM, Craig L Russell
<cr...@oracle.com> wrote:
> Hi Matthew,
>
> I'd like to see you take on the role of release manager for your proposed
> 3.0.1 release.
>
> The process is documented at
> http://svn.apache.org/repos/asf/db/jdo/HowToReleaseJDO.html
>
> Let us know if there is anything in the process that doesn't work...
>
> Regards,
>
> Craig
>
> Begin forwarded message:
>
>> From: "Matthew T. Adams (JIRA)" <ji...@apache.org>
>> Date: August 31, 2011 11:23:09 AM PDT
>> To: jdo-dev@db.apache.org
>> Subject: [jira] [Commented] (JDO-684) Fix OSGi Export-Package entries in
>> JDO 3.0 manifest to include version
>> Reply-To: jdo-dev@db.apache.org
>>
>>
>> [
>> https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094746#comment-13094746
>> ]
>>
>> Matthew T. Adams commented on JDO-684:
>> --------------------------------------
>>
>> Yes, Andy. Exactly like that.
>>
>> Everyone else: can we please quickly push a 3.0.1 update to JDO to
>> include the OSGi manifest fix that's in this patch? Long term, it would be
>> nice to come up with some tests to confirm proper OSGi manifests in all JDO
>> artifacts. I feel another issue coming on...and there it is: JDO-685.
>>
>>> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
>>> ----------------------------------------------------------------------
>>>
>>> Key: JDO-684
>>> URL: https://issues.apache.org/jira/browse/JDO-684
>>> Project: JDO
>>> Issue Type: Bug
>>> Components: api
>>> Affects Versions: JDO 3
>>> Reporter: Matthew T. Adams
>>> Labels: export-package, jdo, osgi
>>> Attachments: JDO-684.patch
>>>
>>>
>>> The manifest for the JDO API project fails to specify package versions in
>>> its OSGi Export-Package entry. I've added these & revised the version from
>>> 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the
>>> package-level version specifications, Virgo (Eclipse Equinox + Spring dm
>>> Server additions) reports version 0.0.0 for all packages, causing missing
>>> bundle dependencies downstream, including DataNucleus.
>>> Patch to follow bug submission.
>>
>> --
>> This message is automatically generated by JIRA.
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
>
>
--
@matthewadams12
mailto:matthew@matthewadams.me
skype:matthewadams12
yahoo:matthewadams
aol:matthewadams12
google-talk:matthewadams12@gmail.com
msn:matthew@matthewadams.me
http://matthewadams.me
http://www.linkedin.com/in/matthewadams
Fwd: [jira] [Commented] (JDO-684) Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
Posted by Craig L Russell <cr...@oracle.com>.
Hi Matthew,
I'd like to see you take on the role of release manager for your
proposed 3.0.1 release.
The process is documented at http://svn.apache.org/repos/asf/db/jdo/HowToReleaseJDO.html
Let us know if there is anything in the process that doesn't work...
Regards,
Craig
Begin forwarded message:
> From: "Matthew T. Adams (JIRA)" <ji...@apache.org>
> Date: August 31, 2011 11:23:09 AM PDT
> To: jdo-dev@db.apache.org
> Subject: [jira] [Commented] (JDO-684) Fix OSGi Export-Package
> entries in JDO 3.0 manifest to include version
> Reply-To: jdo-dev@db.apache.org
>
>
> [ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094746
> #comment-13094746 ]
>
> Matthew T. Adams commented on JDO-684:
> --------------------------------------
>
> Yes, Andy. Exactly like that.
>
> Everyone else: can we please quickly push a 3.0.1 update to JDO to
> include the OSGi manifest fix that's in this patch? Long term, it
> would be nice to come up with some tests to confirm proper OSGi
> manifests in all JDO artifacts. I feel another issue coming
> on...and there it is: JDO-685.
>
>> Fix OSGi Export-Package entries in JDO 3.0 manifest to include
>> version
>> ----------------------------------------------------------------------
>>
>> Key: JDO-684
>> URL: https://issues.apache.org/jira/browse/JDO-684
>> Project: JDO
>> Issue Type: Bug
>> Components: api
>> Affects Versions: JDO 3
>> Reporter: Matthew T. Adams
>> Labels: export-package, jdo, osgi
>> Attachments: JDO-684.patch
>>
>>
>> The manifest for the JDO API project fails to specify package
>> versions in its OSGi Export-Package entry. I've added these &
>> revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have
>> already been published. Without the package-level version
>> specifications, Virgo (Eclipse Equinox + Spring dm Server
>> additions) reports version 0.0.0 for all packages, causing missing
>> bundle dependencies downstream, including DataNucleus.
>> Patch to follow bug submission.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!
[jira] [Commented] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094746#comment-13094746 ]
Matthew T. Adams commented on JDO-684:
--------------------------------------
Yes, Andy. Exactly like that.
Everyone else: can we please quickly push a 3.0.1 update to JDO to include the OSGi manifest fix that's in this patch? Long term, it would be nice to come up with some tests to confirm proper OSGi manifests in all JDO artifacts. I feel another issue coming on...and there it is: JDO-685.
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: JDO-684.patch
Removed typo in javax.persistence Import-Package entry.
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: (was: JDO-684.2.patch)
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.3.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: JDO-684.2.patch
After our conf call discussion, I ran bnd against our currently published 3.0 jar (http://repo1.maven.org/maven2/javax/jdo/jdo-api/3.0/jdo-api-3.0.jar) and it's noticing that I missed some other import package statements:
C:\temp\jdo-bnd>java -jar biz.aQute.bnd.jar print -verify jdo-api-3.0.jar
One error
1 : Unresolved references to [javax.naming, javax.rmi, javax.xml.parsers, org.w3c.dom, org.xml.sax] by class(es) on the Bundle-Classpath[Jar:jdo-api-3.0.jar]: [javax/jdo/JDOHelper$12.class, javax
/jdo/spi/JDOImplHelper.class, javax/jdo/JDOHelper.class]
I'm going to add these to the manifest as well. New patch attached with those as well. Please review. If ok, I'll commit then begin release process for JDO 3.0.1.
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.2.patch, JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: JDO-684.3.patch
After our conf call, I found http://java.sun.com/developer/Books/javaprogramming/JAR/basics/manifest.html that discusses "Package Versioning". It's fairly old, and none of the headers specified therein conflict with those specified in the OSGi r4 specification. I have added these headers for completeness with my best guess for their values, although I omitted the "Name:" header, as it was causing bnd to throw errors.
WRT importing exported packages, section 3.6.6 of the OSGi r4 Core specification discusses importing exported packages. That discussion suggests that our bundle is not a candidate for package substitution, as we mix implementation (JDOHelper) classes with API.
WRT Bundle-Version, section 3.2.1.19 also says the "Bundle-Version header specifies the version of this bundle." For this release, then, it's "3.0.1".
WRT singleton bundles, section 3.6.2 says that it "Indicates that the bundle can only have a single version resolved...The Framework must resolve at most one bundle when multiple versions of a singleton bundle with the same symbolic name are installed." I think this means that we should go with the default value, false. It does not address the authoritativeness of a bundle.
Patch attached, relative to branches/3.0 (other patches were accidentally relative to branches/3.0/api); this patch supercedes all other patches. I would have deleted all other patches, but I don't have the ability or couldn't figure out how to delete attached files.
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.2.patch, JDO-684.3.patch, JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-684:
---------------------------------
Attachment: (was: JDO-684.patch)
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (JDO-684) Fix OSGi Export-Package entries in JDO
3.0 manifest to include version
Posted by "Matthew T. Adams (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams resolved JDO-684.
----------------------------------
Resolution: Fixed
> Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
> ----------------------------------------------------------------------
>
> Key: JDO-684
> URL: https://issues.apache.org/jira/browse/JDO-684
> Project: JDO
> Issue Type: Bug
> Components: api
> Affects Versions: JDO 3
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: export-package, jdo, osgi
> Fix For: JDO 3 update 1
>
> Attachments: JDO-684.patch
>
>
> The manifest for the JDO API project fails to specify package versions in its OSGi Export-Package entry. I've added these & revised the version from 3.0 to 3.0.1, as the 3.0 artifacts have already been published. Without the package-level version specifications, Virgo (Eclipse Equinox + Spring dm Server additions) reports version 0.0.0 for all packages, causing missing bundle dependencies downstream, including DataNucleus.
> Patch to follow bug submission.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira