• 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: Missing artifact com.google.code:jabsorb:jar:1.2.2
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Missing artifact com.google.code:jabsorb:jar:1.2.2


  • Subject: Re: Missing artifact com.google.code:jabsorb:jar:1.2.2
  • From: Ramsey Gurley <email@hidden>
  • Date: Mon, 12 Oct 2015 17:26:18 -0700

So in the frameworks pom.xml, something like this:

		<dependency>
			<groupId>wonder.ajax</groupId>
			<artifactId>Ajax</artifactId>
			<version>${wonder.version}</version>
			<type>woframework</type>
			<exclusions>
				<exclusion>
					<artifactId>jabsorb</artifactId>
					<groupId>com.google.code</groupId>
				</exclusion>
			</exclusions>
		</dependency>
		<dependency>
			<groupId>org.jabsorb</groupId>
			<artifactId>jabsorb</artifactId>
			<version>1.3.2</version>
		</dependency>

?

It seems like I’d still get a build error if I build wonder from source. I wonder how the current maven wonder builds are getting around this problem. Is it that the local repository for wonder is old enough to have a copy of the google code version perhaps?


On Oct 10, 2015, at 8:40 PM, Faizel Dakri <email@hidden> wrote:

> No, not just you. It’s been a while, but I believe I ran into the same issue when I started out with building my frameworks and apps with Maven. You can override the Wonder specified version by declaring it explicitly in your own pom.xml with the alternate version (and groupId).  I’ve been doing just that to include 1.3.2 of jabsorb in my apps and it has been working out okay.
>
> F
>
> --
> Faizel Dakri
> email@hidden
>
>
>
>> On 2015-Oct-09, at 07:16 PM, Ramsey Gurley <email@hidden> wrote:
>>
>> I’m currently in the process of converting a core framework into a maven project and I’ve run into an issue:
>>
>> Missing artifact com.google.code:jabsorb:jar:1.2.2
>>
>> Is it just me?
>>
>> I see an alternative 1.3.2 library from org.jabsorb available. It seems like Wonder Ajax should be moving to that one, since google code is going away, yes?
>>
>> Maven is amazing BTW. I don’t know how I lived without it :D I’m discovering all kinds of neat stuff just trying to convert.
>>
>> Thanks,
>>
>> Ramsey
>> _______________________________________________
>> 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
>


 _______________________________________________
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


  • Follow-Ups:
    • Re: Missing artifact com.google.code:jabsorb:jar:1.2.2
      • From: Fabian Peters <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>)

  • Prev by Date: Re: velocity or.....for templates?
  • Next by Date: Re: ERRest using Ember
  • Previous by thread: Re: Missing artifact com.google.code:jabsorb:jar:1.2.2
  • Next by thread: Re: Missing artifact com.google.code:jabsorb:jar:1.2.2
  • Index(es):
    • Date
    • Thread