[wildfly-dev] eclipselink

[Scott Marlow]

First pass of this is at https://github.com/wildfly/wildfly/pull/4839 
and ORG-1742 put EclipseLink into the JBoss nexus repo 
(https://repository.jboss.org/nexus/content/groups/public/org/eclipse/persistence/eclipselink/2.4.2/eclipselink-2.4.2.pom).

Paul Gier mentioned that people should use 
http://repository.jboss.org/nexus/content/groups/public instead of 
http://repository.jboss.org/nexus/content/groups/developer.

On 07/25/2013 10:26 AM, Scott Marlow wrote:
> Hi Kabir,
>
> Paul Gier pointed out that we should instead mirror the Nexus
> groups/public however the EclipseLink artifacts aren't there yet.
>
> I created ORG-1742 for putting them there.
>
> Scott
>
> On 07/25/2013 07:20 AM, Kabir Khan wrote:
>> Hi Scott,
>>
>> Can you add the eclipselink artifacts from testsuite/compat/pom.xml to http://repository.jboss.org/nexus/content/groups/developer/? It causes problems when I use 'mvn clean install', and my settings.xml is set up to mirror to http://repository.jboss.org/nexus/content/groups/developer. I know it has caused problems for some other people as well.
>>
>> I've worked around it by disabling the mirror, but I added it on Paul Gier's instruction once upon a time, so I would like to keep it. I am guessing the reason for that mirror setting is to make sure that JBoss projects are totally buildable using the JBoss repository, so that we don't need to rely on third-party ones.
>>
>> Cheers,
>>
>> Kabir
>>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>