db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <craig.russ...@oracle.com>
Subject Fwd: [jira] [Commented] (JDO-684) Fix OSGi Export-Package entries in JDO 3.0 manifest to include version
Date Mon, 05 Sep 2011 17:52:58 GMT
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)" <jira@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!


Mime
View raw message