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 "Craig Russell (JIRA)" <ji...@apache.org> on 2006/01/14 22:31:20 UTC
[jira] Created: (JDO-279) Release tck20 as source with a binary
dependency on other projects
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
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=all ]
Michael Bouschen updated JDO-279:
---------------------------------
Attachment: distrib.patch
I propose to add a new directory called distrib to the tck20 project. It includes slightly adapted versions of project.xml, project.properties and maven.xml where any depedencies to the super projrect are removed. These files will refer to beta or fcs version of the jdo2-api and jpox project instead of a SNAPSHOT version.
The attached path distrib.patch adds the distrib directory with the three files mentioned above. It also adds a new goal distrib to the maven.xml in tck20. The distrib goal creates a jar called jdo2-tck-beta-distrib.jar in the distrib directory. It includes all the sources (from subdirectories conf, java, jdo, orm, sql and testdata) plus the maven config files project.xml, project.properties and maven.xml from the distrib directory.
Please note, the patch distrib.patch is not a complete solution for the issue, it is meant to stimulate the discussion. We might want to consider splitting the goals from maven.xml such that all the jdori goals stay in the tck20 version where the iut goals go into the distrib version.
The config files under distrib already use the new groupId org.apache.jdo. So if you test them you need to manually adapt your local maven repository. You also need to copy the jndi files fscontext.jar and providerutil.jar to the lib/ext directory after unpackaing the distribution. Another change is that the build rule in the distrib version of maven.xml does not automatically run the jdori.
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=comments#action_12362800 ]
Craig Russell commented on JDO-279:
-----------------------------------
For the file name of the tck distribution we should use the standard naming convention for JCP distributions. This will serve two purposes: first, it has a very different naming structure from the .jar distributions; second, it is already in the right format for the JCP.
For the tck for jdo 1, this was jdotck-1_0-fcs-src-04_Mar_2002.zip.
For this distribution, if it were made today, it would be jdotck-2_0-beta-src-15_Jan_2006.zip
Secret decoder ring available upon request. ;-)
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=comments#action_12363537 ]
Michael Bouschen commented on JDO-279:
--------------------------------------
Hi Craig,
I did not intent to include the content of iut_jars, just the empty directory:
<include name="iut_jars"/>
<exclude name="iut_jars/*"/>
The second line should exclude any iut jars that are in the iut_jars directory of the release manager.
> 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, distrib.patch2, mavenDistSupport-2.patch, mavenDistSupport-3.patch, mavenDistSupport.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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=all ]
Craig Russell resolved JDO-279:
-------------------------------
Resolution: Fixed
Assign To: Craig Russell
> 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
> Assignee: Craig Russell
> Fix For: JDO 2 beta
> Attachments: distrib.patch, distrib.patch2, mavenDistSupport-2.patch, mavenDistSupport-3.patch, mavenDistSupport.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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Updated: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by Michael Bouschen <mb...@spree.de>.
Hi Craig,
with the patch I was able to run a test using the source distribution. I
called 'maven dist' in tck20, unzipped the created source distribution
in a new directory, renamed directory src to test and then called maven
build (using a single configuration). We do not need the renaming
anymore as soon as JDO-280 isresolved. I hope this helps.
Regards Michael
> [ http://issues.apache.org/jira/browse/JDO-279?page=all ]
>
>Michael Bouschen updated JDO-279:
>---------------------------------
>
> Attachment: mavenDistSupport.patch
>
>Andy proposed to use 'maven dist' for the distribution. There is not need to add our own distrib goal to tck20, so forget the previous patches attached to this issue.
>
>The new patch for review (mavenDistSupport.patch) adds a preGoal and a postGoal for dist:build-src. The preGoal adds some files and directories to be included in the source distribution (Thanks Michelle, copying works). The postGoal simply copies the source distribution zip to file with a different name. The patch defines the property maven.src.dir in tck20/project.properties. This can be removed as soon as JDO-280 is resolved.
>
>
>
>>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, distrib.patch2, mavenDistSupport.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
[jira] Updated: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=all ]
Michael Bouschen updated JDO-279:
---------------------------------
Attachment: mavenDistSupport.patch
Andy proposed to use 'maven dist' for the distribution. There is not need to add our own distrib goal to tck20, so forget the previous patches attached to this issue.
The new patch for review (mavenDistSupport.patch) adds a preGoal and a postGoal for dist:build-src. The preGoal adds some files and directories to be included in the source distribution (Thanks Michelle, copying works). The postGoal simply copies the source distribution zip to file with a different name. The patch defines the property maven.src.dir in tck20/project.properties. This can be removed as soon as JDO-280 is resolved.
> 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, distrib.patch2, mavenDistSupport.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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=comments#action_12363458 ]
Craig Russell commented on JDO-279:
-----------------------------------
I reviewed the new patch mavenDistSupport-2.patch cleaning up the added preGoal and postGoal.
I agree that you should apply the patch mavenDistSupport-2.patch to the trunk and to branches/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, distrib.patch2, mavenDistSupport-2.patch, mavenDistSupport.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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=comments#action_12363539 ]
Craig Russell commented on JDO-279:
-----------------------------------
Oops, read it too quickly. I saw include iut_jars and iut_jars/*. My bad.
Good to go.
> 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, distrib.patch2, mavenDistSupport-2.patch, mavenDistSupport-3.patch, mavenDistSupport.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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=comments#action_12363463 ]
Michael Bouschen commented on JDO-279:
--------------------------------------
I checked in the patch mavenDistSupport-2.patch ino the trunk and into branches/2.0-beta (see revision 370910).
> 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, distrib.patch2, mavenDistSupport-2.patch, mavenDistSupport.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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=all ]
Michael Bouschen updated JDO-279:
---------------------------------
Attachment: mavenDistSupport-2.patch
I attached a new patch mavenDistSupport-2.patch cleaning up the added preGoal and postGoal. It also copies teh RunRules to the tck directory in the distribution.
I propose to apply the patch mavenDistSupport-2.patch to the trunk and to branches/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, distrib.patch2, mavenDistSupport-2.patch, mavenDistSupport.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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=comments#action_12363530 ]
Craig Russell commented on JDO-279:
-----------------------------------
Hi Michael,
I agree to add assertions to the tck20 source distribution. But I'm not as sure that we should send out the iut_jars contents. It's empty in my workspace, and if the release manager has been testing an IUT, why should it be distributed?
> 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, distrib.patch2, mavenDistSupport-2.patch, mavenDistSupport-3.patch, mavenDistSupport.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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=comments#action_12363541 ]
Michael Bouschen commented on JDO-279:
--------------------------------------
Checked in, see revision 371128.
> 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, distrib.patch2, mavenDistSupport-2.patch, mavenDistSupport-3.patch, mavenDistSupport.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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=all ]
Michael Bouschen updated JDO-279:
---------------------------------
Attachment: mavenDistSupport-3.patch
The new patch mavenDistSupport-3.patch adds the directories assertions and iut_jars to the jdo2-tck distribution.
I propose to apply the patch to the trunk and the 2.0-beta branch.
> 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, distrib.patch2, mavenDistSupport-2.patch, mavenDistSupport-3.patch, mavenDistSupport.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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi Michael,
I don't have any good ideas about how to do this. I haven't used XSLT.
Java would work. You could even have a look at jelly. I used the jelly
file tag to generate a properties file in our maven.xml. But I think it
would be monstruously ugly for this job, if it is even possible.
-- Michelle
Michael Bouschen wrote:
> Hi Michelle,
>
>> [
>> http://issues.apache.org/jira/browse/JDO-279?page=comments#action_12362905
>> ]
>> Michelle Caisse commented on JDO-279:
>> -------------------------------------
>>
>> Would it be a good idea to generate distrib/maven.xml by a simple
>> filter of maven.xml to avoid code duplication?
>
>
> yes, it would make sense, since we just need to skip one or two goals
> (such as distrib). I need to figure out what is the easiest way to
> automatically skip a goal. XSLT script? Any idea?
>
> Regards Michael
>
>>
>>
>>
>>> 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, distrib.patch2
>>>
>>> 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.
>>
>>
>>
>
>
Re: [jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by Michael Bouschen <mb...@spree.de>.
Hi Michelle,
Andy had an important remark about using 'maven dist'. It sounds like
this could do the job and would replace most of what I tried to do with
the distrib goal. We now need to figure out how to configure 'maven
dist' such that all the necessary files are included.
About the lib/ext directory. We currently use this directory for
external jars that need to be manually downloaded such as File System
Service Provider jndi implementation fscontext.jar and providerutil.jar.
Since there are several subprojects using these jars (ri11, fostore20,
tck20) we decided to put the lib/text directory parallel to the subprojects.
Regards Michael
> Michael,
>
> Are the differences between the project.xml and project.properties in
> tck20 and tck20/distrib necessary?
>
> $ diff project.properties distrib/project.properties
> 15a16,19
> > # Make sure the compiled class still work with J2SE 1.3
> > maven.compile.source = 1.3
> > maven.compile.target = 1.3
> >
> 89c93
> < jndi =
> ${basedir}/../lib/ext/fscontext.jar${path.separator}${basedir}/../lib/ext/providerutil.jar
>
> ---
> > jndi =
> ${basedir}/lib/ext/fscontext.jar${path.separator}${basedir}/lib/ext/providerutil.jar
>
>
> $ diff project.xml distrib/project.xml
> 19d18
> < <extend>../project.xml</extend>
> 23a23
> > <groupId>org.apache.jdo</groupId>
> 24a25,29
> > <organization>
> > <name>Apache Software Foundation</name>
> > <url>http://www.apache.org</url>
> > </organization>
> > <inceptionYear>2005</inceptionYear>
>
> Could we:
> (1) have a lib/ext under tck20
> (2) not extend ..project.xml in tck20/project.xml
> in order not to require two copies of these files? I don't understand
> the J2SE 1.3 part of the diff.
>
> -- Michelle
>
> Michael Bouschen wrote:
>
>> Hi Michelle,
>>
>>> [
>>> http://issues.apache.org/jira/browse/JDO-279?page=comments#action_12362905
>>> ]
>>> Michelle Caisse commented on JDO-279:
>>> -------------------------------------
>>>
>>> Would it be a good idea to generate distrib/maven.xml by a simple
>>> filter of maven.xml to avoid code duplication?
>>
>>
>>
>> yes, it would make sense, since we just need to skip one or two goals
>> (such as distrib). I need to figure out what is the easiest way to
>> automatically skip a goal. XSLT script? Any idea?
>>
>> Regards Michael
>>
>>>
>>>
>>>
>>>> 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, distrib.patch2
>>>>
>>>> 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
Re: [jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by Michelle Caisse <Mi...@Sun.COM>.
Michael,
Are the differences between the project.xml and project.properties in
tck20 and tck20/distrib necessary?
$ diff project.properties distrib/project.properties
15a16,19
> # Make sure the compiled class still work with J2SE 1.3
> maven.compile.source = 1.3
> maven.compile.target = 1.3
>
89c93
< jndi =
${basedir}/../lib/ext/fscontext.jar${path.separator}${basedir}/../lib/ext/providerutil.jar
---
> jndi =
${basedir}/lib/ext/fscontext.jar${path.separator}${basedir}/lib/ext/providerutil.jar
$ diff project.xml distrib/project.xml
19d18
< <extend>../project.xml</extend>
23a23
> <groupId>org.apache.jdo</groupId>
24a25,29
> <organization>
> <name>Apache Software Foundation</name>
> <url>http://www.apache.org</url>
> </organization>
> <inceptionYear>2005</inceptionYear>
Could we:
(1) have a lib/ext under tck20
(2) not extend ..project.xml in tck20/project.xml
in order not to require two copies of these files? I don't understand
the J2SE 1.3 part of the diff.
-- Michelle
Michael Bouschen wrote:
> Hi Michelle,
>
>> [
>> http://issues.apache.org/jira/browse/JDO-279?page=comments#action_12362905
>> ]
>> Michelle Caisse commented on JDO-279:
>> -------------------------------------
>>
>> Would it be a good idea to generate distrib/maven.xml by a simple
>> filter of maven.xml to avoid code duplication?
>
>
> yes, it would make sense, since we just need to skip one or two goals
> (such as distrib). I need to figure out what is the easiest way to
> automatically skip a goal. XSLT script? Any idea?
>
> Regards Michael
>
>>
>>
>>
>>> 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, distrib.patch2
>>>
>>> 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.
>>
>>
>>
>
>
Re: [jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by Michael Bouschen <mb...@spree.de>.
Hi Michelle,
> [ http://issues.apache.org/jira/browse/JDO-279?page=comments#action_12362905 ]
>
> Michelle Caisse commented on JDO-279:
> -------------------------------------
>
> Would it be a good idea to generate distrib/maven.xml by a simple filter of maven.xml to avoid code duplication?
yes, it would make sense, since we just need to skip one or two goals
(such as distrib). I need to figure out what is the easiest way to
automatically skip a goal. XSLT script? Any idea?
Regards Michael
>
>
>
>>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, distrib.patch2
>>
>>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
[jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Michelle Caisse (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=comments#action_12362905 ]
Michelle Caisse commented on JDO-279:
-------------------------------------
Would it be a good idea to generate distrib/maven.xml by a simple filter of maven.xml to avoid code duplication?
> 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, distrib.patch2
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-279?page=all ]
Michael Bouschen updated JDO-279:
---------------------------------
Attachment: distrib.patch2
Attached you find a new patch distrib.patch2.
- I think any groupId changes should be part of of JDO-278, so I removed any groupId changes from the patch.
- I changed the distribution file to be a zip instead of a jar and used the naming as proposed.
> 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, distrib.patch2
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by Craig L Russell <Cr...@Sun.COM>.
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.
Craig
>
> 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!
Re: [jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by Michael Bouschen <mb...@spree.de>.
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).
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
[jira] Commented: (JDO-279) Release tck20 as source with a binary
dependency on other projects
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ 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?
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira