Hi,
OK, the layouts are good.
The issue with the optional ([org].) is that when Artifactory is building a
path out of this layout the org field will always be added since it's never
empty.
So, the queries from Artifactory to your external IVY repository will always
contain the org value.
Here is what I suggest:
- The libs-release virtual repository should have the "maven2-default"
layout set,
- The libs-release virtual should aggregate (include in its repo list) 2
remote repositories ivy-legacy-1 and ivy-legacy-2,
- There should be a repo layout ivy-legacy-1 with artifact pattern equal to:
'[org]/[module]/[baseRev](-[folderItegRev])/[type]/[module](-[classifier])(-[baseRev])(-[fileItegRev]).[ext]'
- There should be a repo layout ivy-legacy-2 with artifact pattern equal to:
'[org]/[module]/[baseRev](-[folderItegRev])/[type]/[org].[module](-[classifier])(-[baseRev])(-[fileItegRev]).[ext]'
- The ivy-legacy-1 should have ivy-layout-1 repo layout config for both
storage and remote.
- The ivy-legacy-2 should have ivy-layout-2 repo layout config for both
storage and remote.
After doing a request like:
http://someserver/artifactory/libs-release/com/abc/common_library/common_library_to/4.0.0.4-1/common_library_to-4.0.0.4-1.jarcan
you record and see what is the format of request sent to your legacy
IVY
repository?
Adding the following:
<logger name="org.artifactory.repo.HttpRepo">
<level value="debug"/>
</logger>
to your etc/logback.xml file will provide you with feedback about requests
sent from Artifactory to the remote repo.
Can you send (to support if sensitive information) he artifactory.log,
request.log and artifactory.config.xml so we can investigate further this
issue.
Thanks,
Fred.
On Tue, Sep 20, 2011 at 11:54 AM, ap.forrest <
[email protected]> wrote:
> Hi Frederic
>
> Thank you for your response, though I'm not quite following your point.
>
> For our IVY repository, the artifact layout pattern is now:
>
> /[org]/[module]/[baseRev](-[folderItegRev])/[type](s)/[module](-[classifier])(-[baseRev])(-[fileItegRev]).[ext]/
> Testing the following url gives the following output:
> /
> Url:
>
> com.abc.common_library/common_library_to/4.0.0.4-1/jar/common_library_to.jar
> Organization: com.abc.common_library
> Module: common_library_to
> Base Revision: 4.0.0.4-1
> Folder Integration Revision:
> File Integration Revision:
> Classifier:
> Extension: jar
> Type: jar
> /
>
> For Maven, we have left the pattern as the default:
>
> /[orgPath]/[module]/[baseRev](-[folderItegRev])/[module]-[baseRev](-[fileItegRev])(-[classifier]).[ext]/
> Testing the following url gives the following output:
> /
>
> Url:com/abc/common_library/common_library_to/4.0.0.4-1/common_library_to-4.0.0.4-1.jar
> Organization: com.abc.common_library
> Module: common_library_to
> Base Revision: 4.0.0.4-1
> Folder Integration Revision:
> File Integration Revision:
> Classifier:
> Extension: jar
> Type:
> /
>
> Trying any other combination doesn't work, for instance, passing in the IVY
> url to the Maven pattern - this is what I expect.
>
> Regarding the comment around the [org] tag, I dont appreciate the concerns
> here, as when it was included as part of the module name, it was declared
> like so /([org].)[module](-[fileItegRev])(-[classifier]).[ext]/ meaning
> that
> it was optional.
>
> Thank you again, but I'm still no further with this one. Any other
> thoughts?
>
> --
> View this message in context:
> http://forums.jfrog.org/Mapping-from-one-repository-type-to-another-does-it-work-tp6807726p6811427.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> 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
>
--
Chief Architect
JFrog Ltd
http://www.jfrog.org/
http://twitter.com/freddy33
------------------------------------------------------------------------------
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
