I remember a thread on the list that discussed this (it was Russel, I
think). The conclusion was (again, IIRC) that the name urls was not the best
choice, since you're declaring a single repository. Have you tried
repositories {
mavenRepo urls: 'http://testserver:15000/artifactory/nbs-snapshots'
mavenRepo urls: 'http://testserver:15000/artifactory/sdk-snapshots'
}
On Mon, Mar 29, 2010 at 10:16 AM, Rene Groeschke <[email protected]>wrote:
> Hi there,
> I've detected a strange behaviour in my build script. I declared multiple
> maven repositories:
>
> repositories{
> mavenRepo urls:["http://testserver:15000/artifactory/nbs-snapshots
> ",
> "http://testserver:15000/artifactory/sdk-snapshots";];
> }
>
> and some dependencies:
>
> dependencies {
> backOffice "org.acme:SdkFragment:${version}"
> backOffice "org.acme:NbsFragment:${version}"
> }
>
> then I try to copy all artifacts into a libs directory:
>
> copy{
> from{
> configurations.backOffice
> }
> into('libs')
> }
>
> running the copy copies "SdkFragment" and "NbsFragment" jars to the libs
> folder and the runtime dependencies of SdkFragment, BUT NOT the runtime
> fragments of NbsFragment. If I change the order of my repo definitions to
>
> repositories{
> mavenRepo urls:["http://testserver:15000/artifactory/sdk-snapshots
> ",
> "http://testserver:15000/artifactory/nbs-snapshots";];
> }
>
> NbsFragments are resolved transitive but SdkFragment isn't. I'm using
> gradle version 0.9-20100213071645+0000 . Is this a known issue? should I
> raise a JIRA for that. This is really a kind of blocker in my actual
> build.
>
> regards,
>
> René
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
