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.






Reply via email to