Hi guys,

The Ajax framework requires jabsorb 1.2.2 and this version is not available in 
the Maven Central repository [1]. I’ve added the jabsorb 1.2.2 as a third party 
library into the WOCommunity repository. You shouldn’t have problems if you 
build your framework using the same settings.xml required to build Wonder (the 
one that adds the WOCommunity repository as a source of dependencies).

You can do as described by yourself if you want to use a distinct version of 
jabsorb (exclude the one from Ajax and include another one as a direct 
dependency of your project). We can also update the Ajax dependency declaration 
as soon as version 1.3.2 doesn’t introduce any bugs. We should update the jar 
into Libraries folder to keep both Ant and Maven builds consistent.

Anyway, the jabsorb library isn’t the only one required by Wonder that is not 
available in the Maven Central. You may face the same problem with other Wonder 
framework. That’s why we've created the WOCommunity repository in the first 
place.

[1]http://search.maven.org

Cheers,

Henrique

> On 13 de out de 2015, at 03:08, Fabian Peters <[email protected]> wrote:
> 
> Hi Ramsey,
> 
> Version 1.2.2 is available in the community repo: 
> <http://maven.wocommunity.org/content/groups/public/com/google/code/jabsorb/1.2.2/
>  
> <http://maven.wocommunity.org/content/groups/public/com/google/code/jabsorb/1.2.2/>>
> 
> Maybe it just wasn't accessible at some point when you tried to build? I know 
> Henrique was about to move the repo to another server.
> 
> Fabian
> 
>> Am 13.10.2015 um 02:26 schrieb Ramsey Gurley <[email protected] 
>> <mailto:[email protected]>>:
>> 
>> 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 protected]> 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 protected]
>>> 
>>> 
>>> 
>>>> On 2015-Oct-09, at 07:16 PM, Ramsey Gurley <[email protected]> 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 protected])
>>>> Help/Unsubscribe/Update your Subscription:
>>>> https://lists.apple.com/mailman/options/webobjects-dev/listfez%40dakri.com
>>>> 
>>>> This email sent to [email protected]
>>> 
>> 
>> 
>> _______________________________________________
>> 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/lists.fabian%40e-lumo.com
>>  
>> <https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com>
>> 
>> This email sent to [email protected] <mailto:[email protected]>
> 
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected] 
> <mailto:[email protected]>)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/hprange%40gmail.com 
> <https://lists.apple.com/mailman/options/webobjects-dev/hprange%40gmail.com>
> 
> This email sent to [email protected] <mailto:[email protected]>
 _______________________________________________
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]

Reply via email to