Re: [Artifactory-users] Mapping from one repository type to another, does it work?

[Yoav L. <yo...@jf...>]

Cross-repo layout mapping is supported in the pro version of Artifactory.
You shouldn't have to create a remote repo pointing back at your server -
instead, simply configure a virtual repository with the Maven layout that
includes your Ivy local repo and point Maven at the virtual repo.

Looking at the URL of your sample jar, it appears like your mapping may be
incorrect - you are using 'orgPath' (replaces dots for slashes), instead of
'org'. Can you try changing your layout on the local Ivy repo and see
whether that resolves the issue?

Yoav


On Mon, Sep 19, 2011 at 12:08 PM, ap.forrest <
and...@sm...> wrote:

> Morning.
>
> So I've been going through all the scenarios, digging around the web, and
> have yet to find an answer to this. Is it possible for Artifactory to map
> from one repository layout to another? This is my attempt so far...
>
> In our business we currently have an IVY repository for which we deploy
> built artifacts. One such artifact is stored at the following path, with
> the
> following IVY file:
> /
>
> http://someserver:8080/com.abc.common_library/common_library_to/4.0.0.4-1/jar/common_library_to.jar
>
> http://someserver:8080/com.abc.common_library/common_library_to/4.0.0.4-1/ivy/ivy.xml
> /
>
> For the IVY layouts I've configured the following:
> /
>
> [orgPath]/[module]/[baseRev](-[folderItegRev])/[type]/([orgPath].)[module](-[fileItegRev])(-[classifier]).[ext]
>
> [orgPath]/[module]/[baseRev](-[folderItegRev])/[type]/ivy(-[fileItegRev])(-[classifier]).xml
> /
>
> Now we want to expose this within Artifactory for our maven2 projects to
> consume. So I configure a new repository, setting the url, etc, and under
> advanced settings, I set the 'Repository Layout' to be maven-2-default and
> 'Remote Layout Mapping' to be the modified ivy-default. On making these
> changes I see the following message appear:
> /
> Not all tokens can be mapped between the source and the target layout,
> which
> may cause path translation not to work as expected.
> /
>
> I test and save the new repository and all appears happy. I can browse the
> newly configured repository and view it's contents, including the above
> mentioned artifact. I then generate the maven settings from the home
> screen,
> ensure that the correct repositories are selected that include the newly
> configured one, and apply this to Eclipse.
>
> Having done all of this, I now open the pom file within my Eclipse project
> and create a new dependency. I specify the following configuration:
> /
> Group Id: com.abc.common_library
> Artifact Id: common_library_to
> Version: 4.0.0.4-1
> Type: jar
> Scope: compile
> /
>
> Eclipse now attempts to resolve the dependency but gives the following
> error:
> /
> Missing artifact
> com.abc.common_library:common_library_to:jar:4.0.0.4-1:compile
> /
>
> Am I missing something here? This is quite an important step for us to be
> able to do. Any feedback will be most appreciated.
>
> --
> View this message in context:
> http://forums.jfrog.org/Mapping-from-one-repository-type-to-another-does-it-work-tp6807726p6807726.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
> Learn about the latest advances in developing for the
> BlackBerry&reg; mobile platform with sessions, labs & more.
> See new tools and technologies. Register for BlackBerry&reg; DevCon today!
> http://p.sf.net/sfu/rim-devcon-copy1
> _______________________________________________
> Artifactory-users mailing list
> Art...@li...
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>