Well, yes… Maven is probably better thought out since Ivy is basically a hack for Ant to implement a tiny part of Maven (the dependency management). And I’d definitely like to use Maven to build my WO projects but my experience trying to do that was not very nice. Quite a few manual steps involved in getting projects to work. If we could fix that, that would most definitely be the optimal solution (and I’m definitely willing to pitch in work on WOLips for that).
This is the one aspect of WO development that makes me feel like I’m going back in time when I open a WO project. Even javascript has decent dependency management. - hugi > On 1. maí 2015, at 22:35, Chuck Hill <ch...@gevityinc.com> wrote: > > From what I have seen of Ivy, Maven seems like a better thought out and > implemented solution. WO might need better m2e plugin that in WOLips aware. > > Chuck > > > On 2015-05-01, 3:22 PM, "Hugi Thordarson" wrote: > > Hi all. > > Most of our in-house code is written as pure java/scala projects which are > then built, versioned and deployed to a local Maven server using Maven and > SBT. > > We use WO a lot but maintaining the WO applications “old style” (by copying > dependencies into “Libraries” every time something changes) is becoming quite > tiresome. So I’m wondering if anyone would care to share success stories or > tips on methodology for dependency management with WO? Some years ago I heard > of people using Ivy for dependency management in the WO ant scripts, but > haven’t heard much about it since. > > We did try using Maven for all WO development, but I found that WOLips didn’t > really like it. Perhaps that’s working better now? > > Cheers, > - hugi > > // Hugi Thordarson > // http://www.loftfar.is/ <http://www.loftfar.is/> > // s. 895-6688
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
