filed:
http://jira.codehaus.org/browse/GRADLE-527I have now built my first ear with gradle 0.6.1! Still a lot to do in updating all gradle files in all projects, but I can now use gradle again. Are there any big breaking changes in the DSL in upcoming releases? I'm trying to decide if I should skip over 0.6 on the CI engine since the people who own the projects I building have less patience than I do for changes in builds.
Thanks for the help!
Jerod
Also, what's the status of an IntelliJ plugin?
hdockter wrote:
On Jun 17, 2009, at 4:52 PM, JerodLass wrote:
>
> Thanks, that worked. I don't have a good answer as to why I do that,
> but it's
> for using the ant task WsEjbDeploy. I declare the module and then,
> later, I
> refer to the configuration when I execute the task and it finds the
> jar.
> It's something I have been using for several gradle releases.
>
> I'm getting a funny error now. It applies all of the plugins, which
> is
> good, but now on the line:
> project.libs.archiveTasks.each {bundle ->
> I get an error:
> Execution failed for task ':projectModule:libs'.
> Cause: Could not find property 'archiveTasks' on task
> ':projectModule:libs'.
>
> I still see this in the userguide in example 24.59.
This is a bug in the UG. Could you file a Jira?
> Is there a new way to
> do something with all archives?
Yes. For example:
task showJars << {
tasks.withType(Jar).each { println it }
}
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
