Been using NetBeans instead of Eclipse lately, and explicitly pointed
it at my current Maven ver. (2.0.9) so I wouldn't have experienced that.
I've done a build of the 1_5_x branch with 2.0.9 and then a mvn -U
clean package with 2.2.1 as a sanity check. Good news is, all's well
from that limited test.
As far as performance goes, the numbers aren't directly comparable,
but, the build with 2.0.9 (with some dependencies already in my local
maven repo) took 9m 55s, whereas the 2.2.1 build (which required
refreshing deps via the -U switch) only took 7m 44s. I'd call that
significant savings even without the details.
This is, of course, to say nothing of other work OS/X was doing at the
time but the load was roughly the same.
I'll report any issues I come across, but I'm sticking with 2.2.1 for
my day-to-day dev.
--
sands fish
Software Engineer
MIT Libraries
Technology Research & Development
[email protected]
E25-131
On Aug 13, 2009, at 6:04 PM, Mark Diggory wrote:
Some might be surprised to know they've been already using 2.1.x it
if they are using m2eclipse.
http://docs.codehaus.org/display/M2ECLIPSE/Project+FAQ#ProjectFAQ-WhatMavenversionisusedbyplugin
You can test switching to use Maven 2.2 in the Eclipse Maven
Preferences. I suspect it should work fine, if not be faster in
dependency resolution because it is multithreaded
Enjoy the adventure and report back to us on the view from the other
side.
Mark.
On Thu, Aug 13, 2009 at 1:54 PM, Sands Fish <[email protected]> wrote:
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
