[ 
> Release tck20 as source with a binary dependency on other projects
> ------------------------------------------------------------------
>
>          Key: JDO-279
>          URL: [url]http://issues.apache.org/jira/browse/JDO-279" target="_blank">http://issues.apache.org/jira/brows.../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 depe
ndencies 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 deb
ug 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/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]

Hi Michelle,

>     [ http://issues.apache.org/jira/brows...236
2905 ]
>
> 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

>
>
> 
>
>


--
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

[ Post a follow-up to this message ]

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,
> 
>
>
> 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
> 
>
>

[ Post a follow-up to this message ]

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}/l
ib/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,
> 
>
>
> 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
> 
>
>

[ Post a follow-up to this message ]

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
[vbcol=seagreen]
> 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 
> 89c93
> < jndi =
> ${basedir}/../lib/ext/fscontext.jar${path.separator}${based
ir}/../lib/ext/providerutil.jar
>
> --- 
> ${basedir}/lib/ext/fscontext.jar${path.separator}${basedir}
/lib/ext/providerutil.jar
>
>
> $ diff project.xml distrib/project.xml
> 19d18
> <     <extend>../project.xml</extend>
> 23a23 
> 24a25,29 
>
> 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:
> 


--
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

[ Post a follow-up to this message ]