Only tricky part is that I depend on Eclipse, and a handful of other
Eclipse projects to build. And I'm usually picking up weekly builds
from them to build against. So is there something that could be set up
to be able to upload these external dependencies? I really wish my
eclipse dependencies could be downloadable with Maven :)
David Blevins wrote:
On Nov 1, 2005, at 12:55 PM, Sachin Patel wrote:
David Blevins wrote:
On Nov 1, 2005, at 4:46 AM, Sachin Patel wrote:
Could I we this up for devtools as well?
Absolutely.
I'm not exactly sure how to build, though. Seems most of the
project.xmls use the <extends> tag so we won't be able to put them in
continuum as maven 1 projects.
Don't understand. Geronimo is using <extends> as well. What makes it
different?
No difference, we run Geronimo as shell project too. I've never built
devtools, though, so if you can help me there I could whip something up
like I did for Geronimo.
Is the inheritance actually useful to you or just there to follow
convention?
Its useful. I need a parent project.properties as I have a good
number of properties shared across the individual projects. I'd hate
to have to respecify them multiple times.
That's cool. Continuum gets smart enough to do things like report which
test failed, etc. when you are dealing with a maven 1 or 2 project. Up
to you if that is worth the trade-off of loosing project.xml
inheritance. You can always poke at it later if you like. You could
also convert to m2 and keep the inheritance if you are interested in the
"smarter" continuum support.
I'd really like to flatten the inheritance in Geronimo but there are
like 40+ modules compared to 4 in the devtools. I'm jealous :)
-David
-David
Sachin Patel wrote:
This is great!!
continuum wrote:
http://ci.gbuild.org/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/21
