<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.programming.tools.gradle.user">
    <title>gmane.comp.programming.tools.gradle.user</title>
    <link>http://blog.gmane.org/gmane.comp.programming.tools.gradle.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11370"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11358"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11345"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11337"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11336"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11329"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11328"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11324"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11322"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11317"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11310"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11309"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11308"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11300"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11297"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11294"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11292"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11287"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11283"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11273"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11370">
    <title>Gradle analog to Ivy dependency &lt;include&gt; ?</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11370</link>
    <description>&lt;pre&gt;Hi,

In "ivy.xml" I have the following dependency declaration:



How can I add this 
http://ant.apache.org/ivy/history/latest-milestone/ivyfile/dependency-include.html
"inclide"  part to Gradle? I can go



but then it downloads 
http://teamcity.jetbrains.com/guestAuth/repository/download/bt343/latest.lastSuccessful/teamcity-ivy.xml
all dependencies  while I need only one.

Thanks!



-----
Best regards,

Evgeny

evgeny-goldin.com 

--
View this message in context: http://gradle.1045684.n5.nabble.com/Gradle-analog-to-Ivy-dependency-include-tp5709837.html
Sent from the gradle-user mailing list archive at Nabble.com.

&lt;/pre&gt;</description>
    <dc:creator>evgenyg</dc:creator>
    <dc:date>2012-05-24T10:45:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11358">
    <title>Best Practices for storing common configuration values</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11358</link>
    <description>&lt;pre&gt;I am curious about what others are doing in their projects to store common
configuration values.  Please give feedback on your approaches and I
welcome opinions on the approaches I am sharing here.

I use the dynamic properties capability heavily to share common
configuration values and, I take advantage of the gradle.properties file do
achieve this.   With the recent switch to "moving away" from dynamic
properties is this solution future proof?

Here are examples of how I do it and questions related to it.

1. Holding version numbers in gradle.properties like:

SPRING_VERSION=3.0
HIBERNATE=3.4

So you would see in the build.gradle something like this:

dependencies {

         compile {
                [group: 'org.springframework', name: 'spring-context',
version: "$SPRING_VERSION"],
                [group: 'org.springframework', name: 'spring-jdbc',
version: "$SPRING_VERSION"],
                [group: 'org.hibernate', name: 'hibernate', version:
"$HIBERNATE_VERSION"],
                [group: 'org.hibernat&lt;/pre&gt;</description>
    <dc:creator>Jason Hatton</dc:creator>
    <dc:date>2012-05-22T15:38:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11345">
    <title>Gradle Wrapper Resolution issues?</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11345</link>
    <description>&lt;pre&gt;Recently we converted a bunch of our builds to use gradle wrapper to
ensure portability.

Sadly since yesterday afternoon projects trying to use gradlewrapper
for the first time get this exception:

Caused by: java.io.FileNotFoundException:
http://repo.gradle.org/gradle/distributions/gradle-1.0-milestone-9-bin.zip

Has it moved? Is it possible to put a 302 redirect or something in
place if it has? This has essnetially broken all the builds I
converted to use wrapper conveniently after I made the case for using
it. :S


Thanks,
James

&lt;/pre&gt;</description>
    <dc:creator>James Carr</dc:creator>
    <dc:date>2012-05-17T14:31:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11337">
    <title>is there a more "groovy" way to write this gradle code?</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11337</link>
    <description>&lt;pre&gt;if (project.hasProperty("profilingEnabled") &amp;amp;&amp;amp; project.profilingEnabled) {
        runAEJvmArguments &amp;lt;&amp;lt; "-agentlib:yjpagent"
}

seems a bit verbose to me….

&lt;/pre&gt;</description>
    <dc:creator>phil swenson</dc:creator>
    <dc:date>2012-05-16T15:40:38</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11336">
    <title>Resolving dependencies: Alternative syntax for ivy repository</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11336</link>
    <description>&lt;pre&gt;Hello

since I started with gradle i face the problem of not being able to resolve
dynamic revisions when using Ivy.
Today I gave it another try to get rid of it and I may have found something
that could hopefully solve my problem . It was mentioned in GRADLE-1732 
CommonsHttpClientBackedRepository doesn't support version ranges but using 
a URLResolver should do the trick and a  altertnative syntax was mentioned
there.
My problem is that I could not find anything at the documentation and hardly
something in the forum.
I'm also interested how to provide credentials to the URLResolver.
Here is how I got it right now but this does not work.
I see that credentials are added :
[org.gradle.api.internal.artifacts.ivyservice.IvyLoggingAdaper] credentials
added: Subversion Repository&amp;lt; at &amp;gt;https://cmp.de fooman/************

The scripts compile correct and I see that it tries to resolve the
dependencies:
[DEBUG]
[org.gradle.api.internal.artifacts.ivyservice.ivyresolve.UserResolverChain]
Attempting to resolve module 'monro&lt;/pre&gt;</description>
    <dc:creator>Milan Papzilla</dc:creator>
    <dc:date>2012-05-15T12:11:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11329">
    <title>Nested version(...) call in ant closure doesn't work</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11329</link>
    <description>&lt;pre&gt;Hello,

We have the following build.gradle file:

task a {
} &amp;lt;&amp;lt; {
   ant.taskdef(...)
   ant.deb(todir: ...) {
       version(upstream: '1.0.0', debian: 'squeeze')
       ...
   }
}

task b {
} &amp;lt;&amp;lt; {
    def fileName = "program-${version}.zip"
    ...
}

The order of tasks is 'a,b'.
There are two problems:

1. ant.deb(...) doesn't take nested 'version' tag into account and uses
'null' for version value instead.
2. as soon as task 'a' is completed, global project 'version' property is
set to Map [upstream: '1.0.0', debian: 'squeeze']

As a result whole build fails. It used to work with Gradle m3.

Is there a way to use ant 'deb' task (custom task) with a nested tag named
'version'?

Thanks!

--
View this message in context: http://gradle.1045684.n5.nabble.com/Nested-version-call-in-ant-closure-doesn-t-work-tp5703720.html
Sent from the gradle-user mailing list archive at Nabble.com.

&lt;/pre&gt;</description>
    <dc:creator>Alexander Kitaev</dc:creator>
    <dc:date>2012-05-11T18:05:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11328">
    <title>Publishing to Github?</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11328</link>
    <description>&lt;pre&gt;I cannot for the life of me seem to find anything through google about
uploading my artifacts to github for resolving.

Basically I want to do the same thing this guy did for the tomcat
gradle plugin and have people resolve the plugin on github:

https://github.com/bmuschko/gradle-tomcat-plugin


Any ideas? I have a really cool h2 embedded database plugin I want to share. :)


Thanks,
James

&lt;/pre&gt;</description>
    <dc:creator>James Carr</dc:creator>
    <dc:date>2012-05-11T13:27:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11324">
    <title>buildDirName being ignored?</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11324</link>
    <description>&lt;pre&gt;Hi,

I'm setting buildDirName = 'myBuildDir' in my build.gradle file for the
project. When I build things are still getting put in build/... instead of
myBuildDir. When I run gradle properties, I can see the buildDirName is
indeed set to myBuildDir, but it's not being used in any of the other
directory properties - they're all still based off of the default 'build'
directory, and the buildDir itself is still &amp;lt;project root path&amp;gt;/build
instead of &amp;lt;project root path&amp;gt;/myBuildDir.

In my gradle.build file the "buildDirName = 'myBuildDir'" line is the first
non-comment line after the "apply plugin: 'java'" line, which is the very
first line in the file. Am I doing something wrong?

Thanks,

Jeff
&lt;/pre&gt;</description>
    <dc:creator>Jeff Singer</dc:creator>
    <dc:date>2012-05-09T18:56:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11322">
    <title>ProcessResources : How to process resources to different destinations</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11322</link>
    <description>&lt;pre&gt;Hello, 

what is the recommended was to process resources from multiple srcDirs to
different output directories ?
Lets say I have a source set like: 

sourceSets {
    main {        
        output.classesDir "$buildDir/WEB-INF/classes"
        output.resourcesDir "$buildDir/WEB-INF"
       
        java {
            srcDir 'src'
        }
        resources {
            srcDirs = ['src/context', 'web/resources']
        }
    }
}

Can I process the resources from "src/context" and 'web/resources' to
different output directories using the java plugin ? 

--
View this message in context: http://gradle.1045684.n5.nabble.com/ProcessResources-How-to-process-resources-to-different-destinations-tp5696753.html
Sent from the gradle-user mailing list archive at Nabble.com.

&lt;/pre&gt;</description>
    <dc:creator>Milan Papzilla</dc:creator>
    <dc:date>2012-05-09T08:23:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11317">
    <title>waiting for an ant task to finish?</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11317</link>
    <description>&lt;pre&gt;I'm trying to call a jmeter ant task within gradle and currently my
annoyance is that it forks and gradle returns with build successful
before it even runs. Is there anyway to wait on ant tasks like this to
finish?


Thanks,
James

&lt;/pre&gt;</description>
    <dc:creator>James Carr</dc:creator>
    <dc:date>2012-05-04T13:25:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11310">
    <title>Can not resolve artifacts with dynamic revisions from Ivy repository</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11310</link>
    <description>&lt;pre&gt;Hello,

I can not resolve artifacts with dynamic revision number from a Ivy
repository.
According to GRADLE-1789 this should work but when I try to resolve e.g

dependencies {
    testCompile group: 'commons-beanutils', name: 'commons-beanutils',
version: '1.8.+', configuration:'default'
}

version: '1.8.+' fails while version: '1.8.3' is resolved correctly.
Also resolving against mavenCentral()  is working correctly.

But whenever I use a dynamic version number with a Ivy repository it ends up
with:

org.gradle.api.artifacts.ResolveException: Could not resolve all
dependencies for configuration ':testCompile'.
[org.gradle.BuildExceptionReporter] at
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration.rethrowFailure(DefaultLenientConfiguration.java:51)
[org.gradle.BuildExceptionReporter] at
org.gradle.api.internal.artifacts.ivyservice.DefaultResolvedConfiguration.rethrowFailure(DefaultResolvedConfiguration.java:36)
[org.gradle.BuildExceptionReporter] at
org.gradle.api.internal.artifact&lt;/pre&gt;</description>
    <dc:creator>Milan Papzilla</dc:creator>
    <dc:date>2012-05-02T12:53:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11309">
    <title>Well this sucks 1.0-rc-3 broken...</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11309</link>
    <description>&lt;pre&gt;My project compiled and tested fine with 1.0-rc-2 with 1.0-rc-3 I get:

        :compileJava
        
        FAILURE: Build failed with an exception.
        
        * What went wrong:
        Execution failed for task ':compileJava'.
        &amp;gt; invalid source release: 1.7

This sucks:

1.  RC-2 worked fine, which means there are changes RC-2 -&amp;gt; RC-3 which
are not bug fixes aimed solely at turning the RC into the final release.
These are not RCs.

2. My build.gradle doesn't mention 1.7 anywhere.  I demand source
compatibility with 7 on the grounds that 6 is the past and everything
prior should not exist, I may be doing it wrongly, but see above.

 
&lt;/pre&gt;</description>
    <dc:creator>Russel Winder</dc:creator>
    <dc:date>2012-05-01T15:21:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11308">
    <title>Gradle Comms</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11308</link>
    <description>&lt;pre&gt;I assume that the Gradle Users mailing is considered a useless place for
communications about Gradle.  No notices about 1.0-rc-3.

&lt;/pre&gt;</description>
    <dc:creator>Russel Winder</dc:creator>
    <dc:date>2012-05-01T15:02:49</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11300">
    <title>Watching a File For Changes?</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11300</link>
    <description>&lt;pre&gt;This feels like a silly question, but my gradle-fu is a little off since
I've been in node.js land a lot more lately.

Is there an easy way to watch file(s) for changes from gradle? I'm
basically looking to make the embedded jetty/tomcat server restart when
certain files (like the SQL files we use to init H2) change.

Thanks,
James
&lt;/pre&gt;</description>
    <dc:creator>James Carr</dc:creator>
    <dc:date>2012-04-26T20:39:32</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11297">
    <title>gradle in jenkins..</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11297</link>
    <description>&lt;pre&gt;hello all,

  i love how gradle's output is streamlined and clean.  specifically
how the last line of the output dynamically updates with the current
state of the build, like so:


  this line gives me quick feedback in terms of how far along i am.

  in jenkins, i noticed that, when i look at the console output, that
last line is missing.  as a consequence i really have no clue (in
jenkins) how far along the build is until it's done.

  has anyone noticed this or looked into how to make the jenkins
output include the last line?

thanks!
/ eitan

&lt;/pre&gt;</description>
    <dc:creator>Eitan Suez</dc:creator>
    <dc:date>2012-04-26T16:33:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11294">
    <title>gradle use case I haven't seen an example for</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11294</link>
    <description>&lt;pre&gt;I have an ivy repo and use a sort of ugly/hackish ant file to pull things from maven central and then publish them to my own ivy repo

I'd like to do this with gradle, but have no idea where to start.. obviously I can pull down the dependencies/comppile etc etc with gradle.. i've just never tried to make a task to "pull something down and then publish it to another repo"

anyone :)?

Thanks,
Roger


&lt;/pre&gt;</description>
    <dc:creator>Roger Studner</dc:creator>
    <dc:date>2012-04-26T15:15:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11292">
    <title>Obtaining EclipseProject and EclipseClasspath objects.</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11292</link>
    <description>&lt;pre&gt;Hello,

I'm migrating our build plugin from milestone-3 to rc-1. Our build plugin
was patching Eclipse .project and .classpath generating code by modifying
GenerateEclipseClasspath and GenerateEclipseProject tasks. 

Now, I'd like to modify EclipseProject and EclipseClasspath objects
properties. The question is how to get these objects from the build plugin?
I could locate "eclipse" task, but it does not contain "classpath" and
"project" properties. 

How could I get those objects (EclipseProject and EclipseClasspath)
programmatically? 

Thanks!

--
View this message in context: http://gradle.1045684.n5.nabble.com/Obtaining-EclipseProject-and-EclipseClasspath-objects-tp5663105p5663105.html
Sent from the gradle-user mailing list archive at Nabble.com.

&lt;/pre&gt;</description>
    <dc:creator>Alexander Kitaev</dc:creator>
    <dc:date>2012-04-24T19:39:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11287">
    <title>Experimenting ways to produce GUIs from gradle scripts</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11287</link>
    <description>&lt;pre&gt;I'm playing around with graphical user interfaces for my gradle scripts. I
originally thought about antforms
(http://antforms.sourceforge.net/index.html): it works pretty fine in ANT
scripts. But I feel that while antforms had to take care of ANT limitations,
with gradle we have a "developer-friendlier" environment.
So I tried JideBuilkder: here I used the first example from
http://griffon.codehaus.org/JideBuilder.


It quite works. Now the problems:
1. I'd *need a way to leave the gradle JVM alive during all the time needed
to serve the gui*. In the above example the gradle task exits immediately
after the GUI is shown, then the entire jvm terminates. I guess I should
make some thread synchronization machinery between the gradle execution
thread and the awt one. Alternatively I could launch the gui on another jvm
instance, leaving the gradle jvm terminate. In this case the problem would
be: how to execute the gui task (closure) on an external jvm?
2. I'd *need a way to call some tasks execution in response &lt;/pre&gt;</description>
    <dc:creator>davide.cavestro</dc:creator>
    <dc:date>2012-04-24T07:30:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11283">
    <title>Hanging Unit Test</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11283</link>
    <description>&lt;pre&gt;I have a unit test that seems to hang when trying to run it on a
jenkins server. This is odd as it works fine locally, but hangs
indefinitely on the server. I tried on milestone-8 up to rc1 with no
luck

Here's the debug logs:

11:40:24.525 [QUIET] [system.out] 11:40:24.525 [DEBUG]
[org.gradle.messaging.remote.internal.WorkerProtocol] Dispatching
request to worker: [Request consumer:
e7d3a3d6-6ef9-42e2-bac2-082bba005e41, payload: [MethodInvocation
method: startProcessing()]]
11:40:24.572 [QUIET] [system.out] 11:40:24.572 [DEBUG]
[org.gradle.messaging.remote.internal.WorkerProtocol] Dispatching
request to worker: [Request consumer:
e7d3a3d6-6ef9-42e2-bac2-082bba005e41, payload: [MethodInvocation
method: processTestClass()]]
11:40:24.573 [QUIET] [system.out] 11:40:24.573 [DEBUG]
[org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor]
Executing test com.carfax.usage.JmsUsageWriterTest
11:40:24.575 [DEBUG]
[org.gradle.messaging.remote.internal.WorkerProtocol] Dispatching
request to worker: [Request&lt;/pre&gt;</description>
    <dc:creator>James Carr</dc:creator>
    <dc:date>2012-04-23T16:43:12</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11273">
    <title>Get at Artifacts?</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11273</link>
    <description>&lt;pre&gt;Is there a handy way to get a handle on the artifacts that would be
produced by "uploadArchives"? I'd like to use that for my "ghUpload"
script as part of the GitHub development.  (This is a stop-gap
approach to defining a proper GitHub Deployer.)

~~ Robert.

&lt;/pre&gt;</description>
    <dc:creator>Robert Fischer</dc:creator>
    <dc:date>2012-04-22T23:51:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11262">
    <title>Get gradle cache path</title>
    <link>http://comments.gmane.org/gmane.comp.programming.tools.gradle.user/11262</link>
    <description>&lt;pre&gt;Is there some way to get the cache path from inside the build script ?

I'm trying to send artifacts directly to the cache for other projects to use
them.

Thanks.

--
View this message in context: http://gradle.1045684.n5.nabble.com/Get-gradle-cache-path-tp5653772p5653772.html
Sent from the gradle-user mailing list archive at Nabble.com.

&lt;/pre&gt;</description>
    <dc:creator>k4rn4k</dc:creator>
    <dc:date>2012-04-20T09:33:18</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.programming.tools.gradle.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.programming.tools.gradle.user</link>
  </textinput>
</rdf:RDF>

