I'm just glad that it can be done at the moment. I don't mind that it may take a while to "gradlize" it. This solution makes the build files a bit more complex but in general they are still much simpler then the equivelent ant scripts.
Thanks for all the good work matt ----- Original Message ---- From: Hans Dockter <[email protected]> To: [email protected] Sent: Saturday, 14 February, 2009 12:02:39 Subject: Re: [gradle-user] overriding archive_jar? On Feb 14, 2009, at 7:01 AM, Matthew Fudge wrote: > I also don't think that is nice way of solving the problem but if it works > then I will be very grateful (I will have to try it on monday). A similar > problem appeaerd for me yesterday. Things like this do make migration to > gradle a bit easier even if later you should sort the problem out and solve > it better. In my case I just found out that a number of resources (needed for > production in another system (yes they are in the resources dir at the mo)) > should not be included in the jars. However they do have to be distributed > (but seperately) One problem of our archive handling is that we delegate to Ant. This is rather limiting. On the other hand there is surprisingly no production ready Java-API for compression tasks. Thus, to get away from Ant, means quite a bit of work. We want to invest this time at one point, as archive handling is very important. But right now there are other issues we think are even more important. Apache commons-compress seems also have come back to life, although it is still in the sandbox. So that is another place to look at to improve the Gradle archive handling. - Hans > > > Thanks > > Matt > > > > ----- Original Message ---- > From: Hans Dockter <[email protected]> > To: [email protected] > Sent: Saturday, 14 February, 2009 5:45:24 > Subject: Re: [gradle-user] overriding archive_jar? > > > On Feb 12, 2009, at 10:25 PM, brad22 wrote: > >> >> >> Hi, >> >> I would like to exclude a directory from the classes directory produced by >> "compile". >> >> I can do this by defining a new jar task with a supplied "appendix". But >> what I really want to do is override or modify the default "archive_jar" >> zipFileSet. >> >> The following did not work: >> >> archive_jar.zipFileSet(dir: "build/classes") { >> exclude("data/**") >> } >> >> is there a way to achieve this? > > archive_jar.resourceCollections[0].exclude("data/") > > This is not a particularly nice way of solving your problem, but it should > work. In general we have to strengthen our archive objects in terms of > modifying and querying existing settings. > > - Hans > >> >> >> thanks, >> >> Brad Buchsbaum >> >> >> --View this message in context: >> http://www.nabble.com/overriding-archive_jar--tp21985311p21985311.html >> Sent from the gradle-user mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > -- > Hans Dockter > Gradle Project lead > http://www.gradle.org > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Hans Dockter Gradle Project lead http://www.gradle.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
