Correction, for snapshot use this URL
http://repo.jfrog.org/artifactory/gradle-plugins-snapshots

On Wed, Mar 21, 2012 at 10:12 AM, Eli Givoni <[email protected]> wrote:

> Hi Tinkerer,
>
> We added a protection from the missing files, you can try and use the
> latest 
> SNAPSHOT<http://repo.jfrog.org/artifactory/list/libs-snapshots-local/org/jfrog/buildinfo/build-info-extractor-gradle/2.0.x-SNAPSHOT/>of
>  the plugin and see if it resolve your issue.
> Adding this to the build script should do the trick
>
> buildscript {
>
>     repositories {
>
>         maven {
>
>             url "http://repo.jfrog.org/artifactory/gradle";
>
>         }
>
>         dependencies {
>
>             classpath(group: 'org.jfrog.buildinfo', name: 
> 'build-info-extractor-gradle', version: '2.0.x-SNAPSHOT')
>
>         }
>
>     }
>
>      configurations.classpath {
>         resolutionStrategy {
>             failOnVersionConflict()
>             cacheDynamicVersionsFor 0, 'seconds'
>             cacheChangingModulesFor 0, 'seconds'
>         }
>     }
> }
> *
> *
>
> HTH,
>
>
> Eli
>
>
> On Thu, Mar 15, 2012 at 11:57 PM, Yoav Landman <[email protected]> wrote:
>
>> It doesn't seem right for the default config to contain a non exiting
>> file. Can you open an issue <https://issues.jfrog.org/jira/browse/GAP>and 
>> specify which version of Gradle and the Artifactory plugin you are
>> using? Attaching a minimal project that demonstrates this will also help.
>>
>> Thanks
>>
>> On Thu, Mar 15, 2012 at 6:26 PM, Tinkerer <[email protected]>wrote:
>>
>>> Yes, but it only works when I comment out the *default* publishConfigs
>>> in my
>>> top-level build.gradle file-
>>>
>>> artifactory{
>>>   publish {
>>>     ...
>>>     defaults {
>>>          //publishConfigs('archives')
>>>     }
>>>  }
>>> }
>>>
>>> and in the subproject build.gradle, I use  -
>>> artifactoryPublish {
>>>        publishConfigs ('someOtherConfig')
>>> }
>>>
>>> The issue is that I want to selectively use either of the two configs -
>>> archives, someOtherConfig- from my various sub-projects. Does the DSL
>>> allow
>>> the ability to override publishConfigs (eg. publishConfigs =
>>> 'mynewandonlyconfig') instead of just appending to it? Thanks!
>>>
>>> --
>>> View this message in context:
>>> http://forums.jfrog.org/Gradle-artifactoryPublish-expects-jar-file-in-buildir-libs-jar-tp7375684p7376192.html
>>> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF email is sponsosred by:
>>> Try Windows Azure free for 90 days Click Here
>>> http://p.sf.net/sfu/sfd2d-msazure
>>> _______________________________________________
>>> Artifactory-users mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF email is sponsosred by:
>> Try Windows Azure free for 90 days Click Here
>> http://p.sf.net/sfu/sfd2d-msazure
>> _______________________________________________
>> Artifactory-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>>
>>
>
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

Reply via email to