This makes sense to me.
Regards,
David.
--- David Jencks [EMAIL PROTECTED] wrote:
I have been reviewing the jetspeed 2 build process
and believe it could
be improved in several areas.
1. using maven features appropriately within the
current project
structure. For instance, it appears
BUILD SUCCESSFUL
Total time: 35 minutes 7 seconds
Little ? :-)
p.s. It's a build time from a clean installation of
maven.
--- Scott T. Weaver
[EMAIL PROTECTED] ha scritto:
Anything that'll organize the little Maven monster
we have created will
get a +1 from me ;)
David Jencks wrote:
The longest I have ever seen, with unit tests running, is about 5-6
minutes, and that is on a fairly old P3. I have a feeling this long
delay was caused by downloading the dependencies. If you run it again
I am sure it will be MUCH faster, probably a couple of orders of
magnitude faster. I
Ok,
BUILD SUCCESSFUL
Total time: 8 minutes 35 seconds
at the second build of the reactor on my turtle pc.
p.s.
In the instruction for the build getting started
with maven, i don't see the keys
maven.proxy.host = xxx
maven.proxy.port = xxx
It's a facilitation write this stupid settings (in a
On Aug 22, 2004, at 12:00 PM, David Jencks wrote:
I have been reviewing the jetspeed 2 build process and believe it
could be improved in several areas.
1. using maven features appropriately within the current project
structure. For instance, it appears to me that using the multiproject
plugin
