On Oct 13, 2015, at 2:41 PM, Hugi Thordarson <[email protected]> wrote:
> Do you have a recommended path? (read: is there someplace with usable > documentation on how to convert one's WO projects?) I’ve attempted to make > the conversion on several occasions but I always stop somewhere along the > way. I’m currently using Ivy for dependency management, and it’s a hole that > I’d prefer not to dig myself deeper into. > > - hugi I’m basically going with the mindset that this is easy. Maven is easy with non-WO stuff. I proved that to myself before I started. I picked a random archetype from the catalog at apache and built a project. Everything worked, despite the fact I know zilch about apache camel. It built a web service, the unit tests ran. Everything just worked right out of the box. So I know it’s easy. Maven *should* be that easy for everything, but we all know anything WO is going to be something of a pain in the arse thanks to Apple. Swift will be open source, but WO never will. Step one for me was this commons framework. Now that I’ve got it to compile without errors, I have a little victory. I’m hoping I can make one little victory after another and get the whole thing converted. I can keep my progress on a branch as I go. When I run into problems, I first try the maven docs and the wiki. If I really get stuck, I have this great mailing list and all the people on it :D [Thanks for that BTW, everyone. I’m sure I’ll have more questions.] I’ll learn it best if I have to plow through it mostly on my own like this. That’s my plan :) I’m going to finish, because if I don’t I’m going to be really unhappy after getting a taste of the cool stuff Maven can do. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
