db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JDO-51) Improve documentation on build dependencies
Date Tue, 20 Sep 2005 20:11:27 GMT
     [ http://issues.apache.org/jira/browse/JDO-51?page=all ]
Michael Bouschen resolved JDO-51:

    Resolution: Fixed

I added new goals to the top level maven.xml to clean and build jdo11, jdo20 and tck20 projects:
 jdo11.build - builds all JDO1 projects
 jdo11.clean - cleans all JDO1 projects
 jdo20.build - builds all JDO2 projects
 jdo20.clean - cleans all JDO2 projects
 tck20.build - builds tck20 and dependent JDO2 projects
 tck20.clean - cleans tck20 and dependent JDO2 projects
These goals use the maven multiproject support to build the projects in the order of their
defined dependencies. 

I added a new implementation of multiproject:clean to avoid problem that maven multiproject:clean
fails if the jars of dependent projects are not available.   

> Improve documentation on build dependencies
> -------------------------------------------
>          Key: JDO-51
>          URL: http://issues.apache.org/jira/browse/JDO-51
>      Project: JDO
>         Type: Improvement
>   Components: tck20
>     Reporter: Michelle Caisse
>     Assignee: Michael Bouschen

> Michael B's summary:
> yes, we need to describe the dependencies in the README.txt. I propose the following
build order:
> JDO1: api11, btree, ri11, tck11
> JDO2: api20, tck20
> Another alternative is using the multiproject support of maven. You can call 'maven -Dgoal=build
multiproject:goal' in the directory trunk. Then maven looks at all the subprojects and calculates
a dependency graph using the specified dependencies in the project.xml file. It then executes
the goal build in all the subprojects in the order of the calculated dependencies. The only
downside is that it does it for all the subprojects, so for the jdo1 and jdo2 subprojects.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message