Hey all,
Okay, weird. Gradle hangs with just one into directive expressed like this:
into('somedir') {
from configurations.runtime
from jar.archivePath
}
This hangs:
into('lib') {
from configurations.runtime
}
into('main') {
from jar.archivePath
rename { 'main.jar' }
}
However this works:
into('main') {
from jar.archivePath
rename { 'main.jar' }
}
into('lib') {
from configurations.runtime
}
Am I using the Jar task as intended? If so, let me know and I'll
create a JIRA for this.
Cheers,
Merlyn
On Fri, Feb 4, 2011 at 3:38 PM, Merlyn Albery-Speyer
<[email protected]> wrote:
> Some more information. The Jar task hangs at this point:
>
> 15:35:31.378 [DEBUG]
> [org.gradle.api.internal.project.taskfactory.ExecutionShortCircuitTaskExecuter]
> task ':exampleOneJar' is not up-to-date
> 15:35:31.379 [DEBUG]
> [org.gradle.api.internal.tasks.DefaultTaskExecuter] Executing actions
> for task ':exampleOneJar'.
>> Building > :exampleOneJar
>
> Also each into directive works when the other is commented out.
>
> On Fri, Feb 4, 2011 at 3:11 PM, Merlyn Albery-Speyer
> <[email protected]> wrote:
>> The problem I'm having is that as soon as I add a second into
>> directive Gradle hangs. Is the idea that I'm limited to a single into
>> directive per archive task? Or something more subtle?
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
