Ah, thanks for the info. I'm using Maven in one (open source) project, but I chose Ivy for my last client. I've never gotten very familiar with Maven, but I've worked with Ant a lot, so Ivy seemed like a better choice.
We're still using 1.4, though. I'll be happy when IvyDE comes out for 2.0. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kito D. Mann - Author, JavaServer Faces in Action http://www.virtua.com - JSF/Java EE consulting, training, and mentoring http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info >----Original Message----- > From: mguadagna [mailto:[EMAIL PROTECTED] > Sent: Monday, October 15, 2007 3:46 PM > To: [email protected] > Subject: RE: Extremely Slow to Resolve > > > > kito99 wrote: > > > > By the way, why are you switching from Maven? (Just curious.) > > > > In short, we switched to Maven2 earlier this year. At first it seemed > appealing to have standardization, and we were willing to learn what we > needed to make it work for us. We got the basic stuff to work, used > many > plug-ins, and wrote a few as well. What we found is that we never > really got > over the struggling, though. The struggles continued every time we > wanted > to extend our build process in some way. What seemed like it should > take > only 5 mintues, pretty much always took us much longer. The > documentation is > so poor, we found we had the learn more about the black magic (aka > convention) than we wanted to just to understand what it was doing -- > so > much for the ease of convention over configuration. We opted to go back > to > Ant where we could plainly see what was going on. > > In a work, Ant+Ivy is simple, transparent, and flexible. We now get > stuff > done in 5 minutes again. > > -- > View this message in context: http://www.nabble.com/Extremely-Slow-to- > Resolve-tf4622650.html#a13220377 > Sent from the ivy-user mailing list archive at Nabble.com.
