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 (Created) (JIRA)" <ji...@apache.org> on 2011/09/27 19:39:45 UTC
[jira] [Created] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
Automate OSGi bundling in JDO 3.1+ build
----------------------------------------
Key: JDO-694
URL: https://issues.apache.org/jira/browse/JDO-694
Project: JDO
Issue Type: Improvement
Components: api
Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
Reporter: Matthew T. Adams
Assignee: Matthew T. Adams
Fix For: JDO 3 maintenance release 1
Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
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] [Issue Comment Edited] (JDO-694) Automate OSGi bundling in
JDO 3.1+ build
Posted by "Matthew T. Adams (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116791#comment-13116791 ]
Matthew T. Adams edited comment on JDO-694 at 9/28/11 8:58 PM:
---------------------------------------------------------------
JDO-694.2.patch is a better version. Removes API2.MF & API3.MF, centralizing all manifest information in the pom.
was (Author: matthewadams):
This is a better version. Removes API2.MF & API3.MF, centralizing all manifest information in the pom.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1
>
> Attachments: JDO-694.2.patch, JDO-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
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-694) Automate OSGi bundling in JDO 3.1+
build
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455765#comment-13455765 ]
Matthew T. Adams commented on JDO-694:
--------------------------------------
Patch just added produces the following MANIFEST.MF:
Manifest-Version: 1.0
Bnd-LastModified: 1347625699352
Build-Jdk: 1.6.0_35
Built-By: matthew
Bundle-Description: The Java Data Objects (JDO) API is a standard interf
ace-based Java model abstraction of persistence, developed as Java Spec
ification Request 243 under the auspices of the Java Community Process.
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-Localization: plugin
Bundle-ManifestVersion: 2
Bundle-Name: JDO API
Bundle-SymbolicName: javax.jdo
Bundle-Vendor: Apache Software Foundation
Bundle-Version: 3.1.0.SNAPSHOT
Created-By: Apache Maven Bundle Plugin
Export-Package: javax.jdo;uses:="javax.jdo.spi,javax.jdo.listener,javax.
jdo.metadata,org.xml.sax,javax.naming,javax.xml.parsers,org.w3c.dom,jav
ax.rmi,javax.jdo.datastore,javax.transaction";version="3.1.0.SNAPSHOT",
javax.jdo.annotations;version="3.1.0.SNAPSHOT",javax.jdo.datastore;vers
ion="3.1.0.SNAPSHOT",javax.jdo.identity;uses:="javax.jdo.spi,javax.jdo"
;version="3.1.0.SNAPSHOT",javax.jdo.listener;uses:="javax.jdo.spi";vers
ion="3.1.0.SNAPSHOT",javax.jdo.metadata;uses:="javax.jdo.annotations";v
ersion="3.1.0.SNAPSHOT",javax.jdo.spi;uses:="javax.jdo,javax.xml.parser
s,org.xml.sax";version="3.1.0.SNAPSHOT"
Implementation-Title: JDO API
Implementation-Vendor: Apache Software Foundation
Implementation-Vendor-Id: javax.jdo
Implementation-Version: 3.1-SNAPSHOT
Import-Package: javax.naming,javax.rmi,javax.transaction;resolution:=opt
ional,javax.xml.parsers,org.w3c.dom,org.xml.sax
Specification-Title: JDO API
Specification-Vendor: Apache Software Foundation
Specification-Version: 3.1-SNAPSHOT
Tool: Bnd-1.50.0
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+
build
Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455187#comment-13455187 ]
Andy Jefferson commented on JDO-694:
------------------------------------
FYI The "javax.transaction" included in JRE is not full "javax.transaction", it's some very minimal set of exceptions only. Such as "Synchronization", "Transaction", "TransactionManager" aren't there.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-694:
---------------------------------
Attachment: (was: JDO-694.2.patch)
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1
>
> Attachments: JDO-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
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-694) Automate OSGi bundling in JDO 3.1+ build
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-694:
---------------------------------
Attachment: jdo-694.patch
Patch now makes javax.transaction optional.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (JDO-694) Automate OSGi bundling in JDO
3.1+ build
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454931#comment-13454931 ]
Matthew T. Adams edited comment on JDO-694 at 9/14/12 2:02 AM:
---------------------------------------------------------------
[~clr]
> The notation that the javax.transaction package is optional was not captured in the resulting MANIFEST.MF.
IIRC, our minimum supported Java version was 1.5. If that's correct, then javax.transaction and javax.naming are included in the JSE, so making them required shouldn't be an issue.
> There is no reference to the optional javax.persistence package. Perhaps this is because we don't have an explicit reference to it.
I didn't understand that this was still needed in JDO 3.1. Please clarify.
> The comment lines are broken in awkward places. Maybe we should update the project description in trunk/pom.xml to avoid this?
The manifest isn't intended for the convenience of human readability; it has a fixed maximum line length of 72 characters. When viewed using a utility like bnd, the description is rendered without the awkward line breaks. We could add them, but I think that would make readability where it's defined (${pom.description}) awkward.
was (Author: matthewadams):
[~clr]:
> The notation that the javax.transaction package is optional was not captured in the resulting MANIFEST.MF.
IIRC, our minimum supported Java version was 1.5. If that's correct, then javax.transaction and javax.naming are included in the JSE, so making them required shouldn't be an issue.
> There is no reference to the optional javax.persistence package. Perhaps this is because we don't have an explicit reference to it.
I didn't understand that this was still needed in JDO 3.1. Please clarify.
> The comment lines are broken in awkward places. Maybe we should update the project description in trunk/pom.xml to avoid this?
The manifest isn't intended for the convenience of human readability; it has a fixed maximum line length of 72 characters. When viewed using a utility like bnd, the description is rendered without the awkward line breaks. We could add them, but I think that would make readability where it's defined (${pom.description}) awkward.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-694:
---------------------------------
Attachment: (was: JDO-694.patch)
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+
build
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450925#comment-13450925 ]
Michael Bouschen commented on JDO-694:
--------------------------------------
I removed an outdated NOTICE.txt file under api/src/main/resources as part of this JIRA (Committed revision 1382137).
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+
build
Posted by "Craig L Russell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450795#comment-13450795 ]
Craig L Russell commented on JDO-694:
-------------------------------------
The notation that the javax.transaction package is optional was not captured in the resulting MANIFEST.MF.
There is no reference to the optional javax.persistence package. Perhaps this is because we don't have an explicit reference to it.
The comment lines are broken in awkward places. Maybe we should update the project description in trunk/pom.xml to avoid this?
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+
build
Posted by "Matthew T. Adams (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148599#comment-13148599 ]
Matthew T. Adams commented on JDO-694:
--------------------------------------
javax.naming.* should not be optional
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1
>
> Attachments: JDO-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
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-694) Automate OSGi bundling in JDO 3.1+
build
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456029#comment-13456029 ]
Matthew T. Adams commented on JDO-694:
--------------------------------------
Committed revision 1384880.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+
build
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455260#comment-13455260 ]
Matthew T. Adams commented on JDO-694:
--------------------------------------
You're right, Andy. I saw the package and quickly assumed that everything was there. I'll set the javax.transaction package as optional, then. It looks like all of javax.naming is there.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+
build
Posted by "Craig L Russell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455892#comment-13455892 ]
Craig L Russell commented on JDO-694:
-------------------------------------
I think that if we verify that with this manifest, the package loads in an OSGi environment, we're done for now.
Ship it.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (JDO-694) Automate OSGi bundling in JDO 3.1+
build
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams resolved JDO-694.
----------------------------------
Resolution: Fixed
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-694:
---------------------------------
Attachment: (was: JDO-694.patch)
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1
>
> Attachments: JDO-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
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] [Comment Edited] (JDO-694) Automate OSGi bundling in JDO
3.1+ build
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448003#comment-13448003 ]
Matthew T. Adams edited comment on JDO-694 at 9/5/12 7:01 AM:
--------------------------------------------------------------
Attached patch replaces prior patch. Bundle loads properly in Virgo 3.5.0.RELEASE. Produces output below.
Manifest-Version: 1.0
Bnd-LastModified: 1346788585621
Build-Jdk: 1.6.0_33
Built-By: matthew
Bundle-Description: The Java Data Objects (JDO) API is a standard interf
ace-based Java model abstraction of persistence, developed as Java Spec
ification Request 243 under the auspices of the Java Community Process.
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-Localization: plugin
Bundle-ManifestVersion: 2
Bundle-Name: JDO API
Bundle-SymbolicName: javax.jdo
Bundle-Vendor: Apache Software Foundation
Bundle-Version: 3.1.0.SNAPSHOT
Created-By: Apache Maven Bundle Plugin
Export-Package: javax.jdo;uses:="javax.jdo.spi,javax.jdo.listener,javax.
jdo.metadata,org.xml.sax,javax.naming,javax.xml.parsers,org.w3c.dom,jav
ax.rmi,javax.jdo.datastore,javax.transaction";version="3.1.0.SNAPSHOT",
javax.jdo.annotations;version="3.1.0.SNAPSHOT",javax.jdo.datastore;vers
ion="3.1.0.SNAPSHOT",javax.jdo.identity;uses:="javax.jdo.spi,javax.jdo"
;version="3.1.0.SNAPSHOT",javax.jdo.listener;uses:="javax.jdo.spi";vers
ion="3.1.0.SNAPSHOT",javax.jdo.metadata;uses:="javax.jdo.annotations";v
ersion="3.1.0.SNAPSHOT",javax.jdo.spi;uses:="javax.jdo,javax.xml.parser
s,org.xml.sax";version="3.1.0.SNAPSHOT"
Implementation-Title: JDO API
Implementation-Vendor: Apache Software Foundation
Implementation-Vendor-Id: javax.jdo
Implementation-Version: 3.1-SNAPSHOT
Import-Package: javax.naming,javax.rmi,javax.transaction,javax.xml.parse
rs,org.w3c.dom,org.xml.sax
Specification-Title: JDO API
Specification-Vendor: Apache Software Foundation
Specification-Version: 3.1-SNAPSHOT
Tool: Bnd-1.50.0
was (Author: matthewadams):
Attached patch replaces prior patch. Bundle loads properly in Virgo 3.5.0.RELEASE. Produces output below, which may be jacked due to JIRA comment formatting upon upload. It's correctly formatted in the jar's manifest file.
Manifest-Version: 1.0
Bnd-LastModified: 1346788585621
Build-Jdk: 1.6.0_33
Built-By: matthew
Bundle-Description: The Java Data Objects (JDO) API is a standard interf
ace-based Java model abstraction of persistence, developed as Java Spec
ification Request 243 under the auspices of the Java Community Process.
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-Localization: plugin
Bundle-ManifestVersion: 2
Bundle-Name: JDO API
Bundle-SymbolicName: javax.jdo
Bundle-Vendor: Apache Software Foundation
Bundle-Version: 3.1.0.SNAPSHOT
Created-By: Apache Maven Bundle Plugin
Export-Package: javax.jdo;uses:="javax.jdo.spi,javax.jdo.listener,javax.
jdo.metadata,org.xml.sax,javax.naming,javax.xml.parsers,org.w3c.dom,jav
ax.rmi,javax.jdo.datastore,javax.transaction";version="3.1.0.SNAPSHOT",
javax.jdo.annotations;version="3.1.0.SNAPSHOT",javax.jdo.datastore;vers
ion="3.1.0.SNAPSHOT",javax.jdo.identity;uses:="javax.jdo.spi,javax.jdo"
;version="3.1.0.SNAPSHOT",javax.jdo.listener;uses:="javax.jdo.spi";vers
ion="3.1.0.SNAPSHOT",javax.jdo.metadata;uses:="javax.jdo.annotations";v
ersion="3.1.0.SNAPSHOT",javax.jdo.spi;uses:="javax.jdo,javax.xml.parser
s,org.xml.sax";version="3.1.0.SNAPSHOT"
Implementation-Title: JDO API
Implementation-Vendor: Apache Software Foundation
Implementation-Vendor-Id: javax.jdo
Implementation-Version: 3.1-SNAPSHOT
Import-Package: javax.naming,javax.rmi,javax.transaction,javax.xml.parse
rs,org.w3c.dom,org.xml.sax
Specification-Title: JDO API
Specification-Vendor: Apache Software Foundation
Specification-Version: 3.1-SNAPSHOT
Tool: Bnd-1.50.0
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-694:
---------------------------------
Attachment: jdo-694.patch
Attached patch replaces prior patch. Bundle loads properly in Virgo 3.5.0.RELEASE. Produces output below, which may be jacked due to JIRA comment formatting upon upload. It's correctly formatted in the jar's manifest file.
Manifest-Version: 1.0
Bnd-LastModified: 1346788585621
Build-Jdk: 1.6.0_33
Built-By: matthew
Bundle-Description: The Java Data Objects (JDO) API is a standard interf
ace-based Java model abstraction of persistence, developed as Java Spec
ification Request 243 under the auspices of the Java Community Process.
Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
Bundle-Localization: plugin
Bundle-ManifestVersion: 2
Bundle-Name: JDO API
Bundle-SymbolicName: javax.jdo
Bundle-Vendor: Apache Software Foundation
Bundle-Version: 3.1.0.SNAPSHOT
Created-By: Apache Maven Bundle Plugin
Export-Package: javax.jdo;uses:="javax.jdo.spi,javax.jdo.listener,javax.
jdo.metadata,org.xml.sax,javax.naming,javax.xml.parsers,org.w3c.dom,jav
ax.rmi,javax.jdo.datastore,javax.transaction";version="3.1.0.SNAPSHOT",
javax.jdo.annotations;version="3.1.0.SNAPSHOT",javax.jdo.datastore;vers
ion="3.1.0.SNAPSHOT",javax.jdo.identity;uses:="javax.jdo.spi,javax.jdo"
;version="3.1.0.SNAPSHOT",javax.jdo.listener;uses:="javax.jdo.spi";vers
ion="3.1.0.SNAPSHOT",javax.jdo.metadata;uses:="javax.jdo.annotations";v
ersion="3.1.0.SNAPSHOT",javax.jdo.spi;uses:="javax.jdo,javax.xml.parser
s,org.xml.sax";version="3.1.0.SNAPSHOT"
Implementation-Title: JDO API
Implementation-Vendor: Apache Software Foundation
Implementation-Vendor-Id: javax.jdo
Implementation-Version: 3.1-SNAPSHOT
Import-Package: javax.naming,javax.rmi,javax.transaction,javax.xml.parse
rs,org.w3c.dom,org.xml.sax
Specification-Title: JDO API
Specification-Vendor: Apache Software Foundation
Specification-Version: 3.1-SNAPSHOT
Tool: Bnd-1.50.0
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+
build
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454931#comment-13454931 ]
Matthew T. Adams commented on JDO-694:
--------------------------------------
[~clr]:
> The notation that the javax.transaction package is optional was not captured in the resulting MANIFEST.MF.
IIRC, our minimum supported Java version was 1.5. If that's correct, then javax.transaction and javax.naming are included in the JSE, so making them required shouldn't be an issue.
> There is no reference to the optional javax.persistence package. Perhaps this is because we don't have an explicit reference to it.
I didn't understand that this was still needed in JDO 3.1. Please clarify.
> The comment lines are broken in awkward places. Maybe we should update the project description in trunk/pom.xml to avoid this?
The manifest isn't intended for the convenience of human readability; it has a fixed maximum line length of 72 characters. When viewed using a utility like bnd, the description is rendered without the awkward line breaks. We could add them, but I think that would make readability where it's defined (${pom.description}) awkward.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-694:
---------------------------------
Attachment: JDO-694.patch
This patch removes API2.MF, modifies API3.MF, and uses Apache Felix maven-bundle-plugin to automate OSGi-related manifest information in the JDO API jar.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1
>
> Attachments: JDO-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
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-694) Automate OSGi bundling in JDO 3.1+ build
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-694:
---------------------------------
Attachment: JDO-694.2.patch
This is a better version. Removes API2.MF & API3.MF, centralizing all manifest information in the pom.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1
>
> Attachments: JDO-694.2.patch, JDO-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
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-694) Automate OSGi bundling in JDO 3.1+ build
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-694:
---------------------------------
Attachment: (was: JDO-694.patch)
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1
>
> Attachments: JDO-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
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] [Issue Comment Edited] (JDO-694) Automate OSGi bundling in
JDO 3.1+ build
Posted by "Matthew T. Adams (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115745#comment-13115745 ]
Matthew T. Adams edited comment on JDO-694 at 9/28/11 8:58 PM:
---------------------------------------------------------------
JDO-694.patch removes API2.MF, modifies API3.MF, and uses Apache Felix maven-bundle-plugin to automate OSGi-related manifest information in the JDO API jar.
was (Author: matthewadams):
This patch removes API2.MF, modifies API3.MF, and uses Apache Felix maven-bundle-plugin to automate OSGi-related manifest information in the JDO API jar.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1
>
> Attachments: JDO-694.2.patch, JDO-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
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-694) Automate OSGi bundling in JDO 3.1+
build
Posted by "Matthew T. Adams (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148639#comment-13148639 ]
Matthew T. Adams commented on JDO-694:
--------------------------------------
I'll defer to bnd's expertise as to what should be listed in the Import-Package header (bnd is the tool that underlies maven-bundle-plugin). For example, we depend on javax.security, yet bnd does not add an import for that package, but it does add an import for javax.naming. Best Craig & I could figure is that bnd knows what should & shouldn't be listed in Import-Package. We're going with everything as optional because javax.naming & javax.rmi are used only if JNDI is used and the XML APIs are used only if a jdoconfig.xml is parsed.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1
>
> Attachments: JDO-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
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-694) Automate OSGi bundling in JDO 3.1+ build
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-694:
---------------------------------
Attachment: JDO-694.patch
Proposed fix. Sorry about the whitespace.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1
>
> Attachments: JDO-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
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-694) Automate OSGi bundling in JDO 3.1+
build
Posted by "Matthew T. Adams (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123053#comment-13123053 ]
Matthew T. Adams commented on JDO-694:
--------------------------------------
Please review patch. Upon successful review, I'll commit.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1
>
> Attachments: JDO-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
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-694) Automate OSGi bundling in JDO 3.1+ build
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-694:
---------------------------------
Attachment: (was: jdo-694.patch)
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (JDO-694) Automate OSGi bundling in JDO 3.1+
build
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455904#comment-13455904 ]
Matthew T. Adams commented on JDO-694:
--------------------------------------
Verified that the bundle loads in Virgo. I'll apply the patch.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1 (3.1), JDO 3 maintenance release 2 (3.2)
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> Attachments: jdo-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JDO-694) Automate OSGi bundling in JDO 3.1+ build
Posted by "Matthew T. Adams (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams updated JDO-694:
---------------------------------
Attachment: JDO-694.patch
Proposed final patch #1. Will commit upon successful review.
> Automate OSGi bundling in JDO 3.1+ build
> ----------------------------------------
>
> Key: JDO-694
> URL: https://issues.apache.org/jira/browse/JDO-694
> Project: JDO
> Issue Type: Improvement
> Components: api
> Affects Versions: JDO 3 maintenance release 1, JDO 3 maintenance release 2
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> Labels: jdo, osgi
> Fix For: JDO 3 maintenance release 1
>
> Attachments: JDO-694.patch
>
>
> Alter maven build to ensure that the JDO API jar expresses its dependencies on other packages for the purposes of use in an OSGi environment.
--
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