Hi Paul,
Well, not directly. What you can do is excluding one of the group ids from
all the repositories so it will never show up unexpectedly.
Yossi
On Wed, Oct 5, 2011 at 11:32, Paul Slusarz <[email protected]> wrote:
> Is there any way to resolve organization naming conflicts in Artifactory?
> Specifically, we have two types of problems:****
>
> **1. **Org/GroupId changes with later version
> (nekohtml:nekohtml:0.9.1 and net.sourceforge.nekohtml: nekohtml:1.9.15)***
> *
>
> **2. **Org/GroupId differs between different remote repositories
> (velocity:velocity:1.5 and org.apache.velocity:velocity:1.5)****
>
> ** **
>
> We are not having much luck using ivy namespaces since the example seems to
> require a custom built repository, and that’s the role we wanted to have
> reserved for Artifactory. ****
>
> ** **
>
> Thanks,****
>
> Cody and Paul****
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
