|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
23/Apr/06 02:30 AM
|
|
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.
|
|
Description
|
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.
|
Show » |
|
Improvement
Closed
Major
Improve documentation on build dependencies
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.