The reason [artifact] isn't used is because it's a configurable token that
may represent an aggregate of any number of other tokens.
For example, [artifact] can be resolved to [module]-[type]; but in a
different case, it can be resolved as [module]-[classifier] and so
maintaining it as [artifact] will lose this information.
The "default-ivy" pattern is an Ivy pattern we found was most commonly
used, but the patterns are customizable so you can use whatever best fits
your needs.
On Mon, Jul 30, 2012 at 6:22 PM, Jeroen van Dun
<[email protected]>wrote:
> Hi Noam,
>
> Changing m2compatibe="true" to m2compatibe="false" indeed fixes it (doh!)
> Thanks! Another question though: I wonder why the 'ivy-default' Artifact
> Path Pattern uses 'classifier' and not 'artifact' since 'classifier' comes
> from the 'maven' namespace? I am trying to setup an ivy-repo and trying to
> do it right the first time but I must admit I am kind of confused now :) Is
> the 'default-ivy' pattern a good pattern to use or would you recommend
> something else?
>
> Thank you,
>
> jeroen
>
>
> Message: 3
> Date: Sun, 29 Jul 2012 09:39:10 +0300
> From: "Noam Y. Tenne" <[email protected]>
> Subject: Re: [Artifactory-users] Retrieving artifacts from a
> 'ivy-layout' repo using ivy and ant
> To: [email protected]
> Message-ID:
> <CAEBOT-1QEFv_z_3ncGTEHeWA9VOOQjjmKa2=
> [email protected]>
> Content-Type: text/plain; charset="windows-1252"
>
> The problems with the URLs in the failing requests are that:
>
> 1. The organization is separated by '/' instead of '.' (as with Maven).
> 2. The legacIt is placed as the artifact name.
>
> I suspect that this is caused by the fact that the resolver configuration
> you use is marked as m2compatibe="true" and so it ignores the patterns you
> specify and applies the Maven layout to them.
>
> On Thu, Jul 26, 2012 at 7:34 PM, Jeroen van Dun
> <[email protected]>wrote:
>
> > Hi, ****
> >
> > ** **
> >
> > I have setup a repository called ?jeroen-test-local? using the
> > ?ivy-default? layout included with Artifactory 2.6.1:****
> >
> > ** **
> >
> > Artifact Path Pattern:****
> >
> >
> >
> [org]/[module]/[baseRev](-[folderItegRev])/[type]s/[module](-[classifier])-[baseRev](-[fileItegRev]).[ext]
> > ****
> >
> > ** **
> >
> > Distinctive Descriptor Path Pattern:****
> >
> >
> >
> [org]/[module]/[baseRev](-[folderItegRev])/[type]s/ivy-[baseRev](-[fileItegRev]).xml
> > ****
> >
> > ** **
> >
> > Folder Integration Revision RegExp and File Integration Revision
> RegExp:**
> > **
> >
> > \d{14}****
> >
> > ** **
> >
> > I am using the client settings generated by Artifactory (using
> > ivy-default):****
> >
> > ** **
> >
> > <chain name="main">****
> >
> > <url name="public" m2compatible="true">****
> >
> > <artifact pattern="
> >
> http://host:8081/artifactory/jeroen-test-local/[organization]/[module]/[revision]/[type]s/[module](-[classifier])-[revision].[ext]
> "
> > />****
> >
> > <ivy pattern="
> >
> http://host:8081/artifactory/jeroen-test-local/[organization]/[module]/[revision]/[type]s/ivy-[revision].xml
> "
> > />****
> >
> > </url>****
> >
> > </chain>****
> >
> > ** **
> >
> > ** **
> >
> > In that repository I published a file:****
> >
> > Repository Path:
> >
> jeroen-test-local:com.rs.seagull/test/7.0-20120625150043/exes/test-legaclt-7.0-20120625150043.exe
> > ****
> >
> > ** **
> >
> > And an ivy file:****
> >
> > Repository Path:
> >
> jeroen-test-local:com.rs.seagull/test/7.0-20120625150043/ivys/ivy-7.0-20120625150043.xml
> > ****
> >
> > ** **
> >
> > I am using the following entry in my ivy file (as suggested by The
> > dependency Declaration in Artifactory for the file I published):****
> >
> > ** **
> >
> > <dependency org="com.rs.seagull" name="test"
> rev="7.0-20120625150043">****
> >
> > ** **
> >
> > <artifact name="test" type="exe" m:classifier="legaclt"
> ext="exe"/>***
> > *
> >
> > ** **
> >
> > </dependency>****
> >
> > ** **
> >
> > If I try to retrieve that published file using the generated client
> > settings and dependency declarations (ivy:resolve) I get the following
> > error message:****
> >
> > ** **
> >
> > [ivy:resolve] :::: WARNINGS****
> >
> > [ivy:resolve] module not found:
> > com.rs.seagull#test;7.0-20120625150043****
> >
> > ** **
> >
> > [ivy:resolve] ==== jeroen-test-local: tried****
> >
> > [ivy:resolve]
> >
> http://host:8081/artifactory/jeroen-test-local/com/rs/seagull/test/7.0-20120625150043/ivys/ivy-7.0-20120625150043.xml
> > ****
> >
> > [ivy:resolve] -- artifact
> > com.rs.seagull#test;7.0-20120625150043!legaclt.exe****
> >
> > :****
> >
> > [ivy:resolve]
> >
> http://host:8081/artifactory/jeroen-test-local/com/rs/seagull/test/7.0-20120625150043/exes/legaclt-7.0-20120625150043.exe
> > ****
> >
> > [ivy:resolve]
> ::::::::::::::::::::::::::::::::::::::::::::::****
> >
> > [ivy:resolve] :: UNRESOLVED DEPENDENCIES
> ::****
> >
> > [ivy:resolve]
> ::::::::::::::::::::::::::::::::::::::::::::::****
> >
> > [ivy:resolve] :: com.rs.seagull#test;7.0-20120625150043: not
> > found****
> >
> > [ivy:resolve]
> ::::::::::::::::::::::::::::::::::::::::::::::****
> >
> > ** **
> >
> > The urls in the error message seems ok? Apparently I am missing
> something?
> > But what? ****
> >
> > ** **
> >
> > Thank you,****
> >
> > ** **
> >
> > jeroen****
> >
> > * *
> >
> >
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Artifactory-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/artifactory-users
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
> ------------------------------
>
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>
> End of Artifactory-users Digest, Vol 65, Issue 19
> *************************************************
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
