• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [SOLVED] Missing artifact com.google.code:jabsorb:jar:1.2.2
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [SOLVED] Missing artifact com.google.code:jabsorb:jar:1.2.2


  • Subject: Re: [SOLVED] Missing artifact com.google.code:jabsorb:jar:1.2.2
  • From: Ramsey Gurley <email@hidden>
  • Date: Tue, 13 Oct 2015 16:51:33 -0700

On Oct 13, 2015, at 2:41 PM, Hugi Thordarson <email@hidden> 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@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden


References: 
 >Missing artifact com.google.code:jabsorb:jar:1.2.2 (From: Ramsey Gurley <email@hidden>)
 >Re: Missing artifact com.google.code:jabsorb:jar:1.2.2 (From: Faizel Dakri <email@hidden>)
 >Re: Missing artifact com.google.code:jabsorb:jar:1.2.2 (From: Ramsey Gurley <email@hidden>)
 >Re: Missing artifact com.google.code:jabsorb:jar:1.2.2 (From: Fabian Peters <email@hidden>)
 >Re: Missing artifact com.google.code:jabsorb:jar:1.2.2 (From: Henrique Prange <email@hidden>)
 >[SOLVED] Missing artifact com.google.code:jabsorb:jar:1.2.2 (From: Ramsey Gurley <email@hidden>)
 >Re: [SOLVED] Missing artifact com.google.code:jabsorb:jar:1.2.2 (From: Hugi Thordarson <email@hidden>)
 >Re: [SOLVED] Missing artifact com.google.code:jabsorb:jar:1.2.2 (From: Ramsey Gurley <email@hidden>)
 >Re: [SOLVED] Missing artifact com.google.code:jabsorb:jar:1.2.2 (From: Hugi Thordarson <email@hidden>)

  • Prev by Date: Re: [SOLVED] Missing artifact com.google.code:jabsorb:jar:1.2.2
  • Next by Date: Yosemite deployment problem with MySQL
  • Previous by thread: Re: [SOLVED] Missing artifact com.google.code:jabsorb:jar:1.2.2
  • Next by thread: Deployment on Yosemite
  • Index(es):
    • Date
    • Thread