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 "Michael Bouschen (JIRA)" <ji...@apache.org> on 2005/09/20 22:04:29 UTC

[jira] Assigned: (JDO-51) Improve documentation on build dependencies

     [ http://issues.apache.org/jira/browse/JDO-51?page=all ]

Michael Bouschen reassigned JDO-51:
-----------------------------------

    Assign To: Michael Bouschen  (was: Michelle Caisse)

> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira