Hi,
--- Chris Kimpton <[EMAIL PROTECTED]> wrote:
> >
> > Yes, maven handles that. I don't want any patches to the old
> build
> > system. Please use maven because those build systems are going
> bye
> > bye
> > sooner rather then later hopefully this week.
>
Ok - I have maven installed. I can update my jars and jar my code,
which also runs the tests.
The docs seem to imply that you have one lib.repo for everything - is
that the reccomended choice? I was having one per project - stratum,
turbine, etc...
I also noticed that the {maven.home}/build-test.xml references
specific versions of files - I presume that will be replaced by
references to the dependencies stuff.
I also see a junit-xml task. I want to run this against my turbine
and stratum projects - do I amend the turbine/stratum build-maven.xml
to have a task that calls the one in {maven.home}. Or is there some
other way of getting it?
I don't suppose you can't just "import" all tasks from one build.xml
file into another? This would remove the need to have stub tasks
that forward the calls.
I suggest you remove that old build system asap - there are enough
build files to follow now without some being redundant...
Chris
=====
------------------------------------------
http://www.soccer2002.org.uk
__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
