db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject Re: [jira] Commented: (JDO-279) Release tck20 as source with a binary dependency on other projects
Date Mon, 16 Jan 2006 23:09:01 GMT
Hi Michael,

On Jan 16, 2006, at 2:18 PM, Michael Bouschen wrote:

> Hi Craig,
>>    [ http://issues.apache.org/jira/browse/JDO-279? 
>> page=comments#action_12362798 ]
>> Craig Russell commented on JDO-279:
>> -----------------------------------
>> This looks good. A few items we need to resolve.
>> 1. We want to continue development on the projects but want to cut  
>> a release. What incantations do we need to make to do this? The  
>> version in maven identifies dependencies which is fine, but how do  
>> we actually build the 2.0-beta version to put into the local  
>> directory?
> This is a good question! Maybe it is as simple as copying  
> everything we want to release as beta from jdo/trunk to jdo/ 
> branches/2.0-beta and change the version number there. I think this  
> should be done after we changed the group ids (JDO-278).

I changed the version tag from SNAPSHOT to 2.0-beta and built. Voila.  
The artifacts are properly named in the repository jars and poms. So  
I guess we need to change the version in order to make the release  
locally then publish it.

Meantime, I will change the groupId as a separate item and check it in.


> Regards Michael
>> 2. Slight changes will be needed if we adopt the groupId change  
>> for the api jar to be javax.jdo instead of org.apache.jdo.
>> 3. I think it's good that the distributed tck20 can run both the  
>> RI and the IUT with different maven goals. The first thing the  
>> user will want to do is to run the RI and make sure it works. Then  
>> they can install the IUT, modify their properties etc. and try to  
>> run it.
>> 4. The version number for "beta" in the attached files should  
>> include the release number, e.g. "2.0-beta".
>>> Release tck20 as source with a binary dependency on other projects
>>> ------------------------------------------------------------------
>>>         Key: JDO-279
>>>         URL: http://issues.apache.org/jira/browse/JDO-279
>>>     Project: JDO
>>>        Type: Improvement
>>>  Components: tck20
>>>    Reporter: Craig Russell
>>>     Fix For: JDO 2 beta
>>> Attachments: distrib.patch
>>> This proposal would repackage tck20 as a project that has no  
>>> dependencies on the super-project (../project.xml). It would  
>>> continue to have binary dependencies on several of the other  
>>> projects.
>>> This allows us to distribute the tck20 including sources to allow  
>>> users to run the tck without having to use the svn workspace. The  
>>> sources are needed in order to debug the implementation under test.
> -- 
> Michael Bouschen		Tech@Spree Engineering GmbH
> mailto:mbo.tech@spree.de	http://www.tech.spree.de/
> Tel.:++49/30/235 520-33		Buelowstr. 66			
> Fax.:++49/30/2175 2012		D-10783 Berlin			

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!

View raw message