Thanks, that worked to get all the jars built. Now, hopefully this will
be the last piece of this puzzle:
Most of the time, we're building for local testing or for use with our
own website. When we do so, we like to blanket include all ~40 family
jars from our core project, in addition to the standard core.jar. Doing
this with ant was as simple as using an include notation something along
the lines of {$dist.dir}/*.jar.
So two questions (or one, if the answer to the first covers the second):
1) Is there some similarly easy way to do a blanket *.jar inclusion of
our core jars using Gradle?
2) How do you include a specific list of these sub-jars from core?
I really appreciate all the help,
~Brian
On 12/23/2010 1:00 PM, TheKaptain [via Gradle] wrote:
> The easiest way to fit your tasks into the build lifecycle would
> probably be to add a dependency on your 'sub-jar' from the jar task:
> jar.dependsOn << caaJar
>
> This should work since there are no dependencies between the two jars
> you're building.
>
> ------------------------------------------------------------------------
> View message @
> http://gradle.1045684.n5.nabble.com/How-to-exclude-some-classes-from-jar-tp3315811p3316889.html
> To unsubscribe from How to exclude some classes from jar, click here
> <http://gradle.1045684.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3315811&code=YnJpYW4udHJlemlzZUBpbnRlbGxpZGF0YS5uZXR8MzMxNTgxMXwxMTE4NTY2NjA4>.
>
>
--
View this message in context:
http://gradle.1045684.n5.nabble.com/How-to-exclude-some-classes-from-jar-tp3315811p3317016.html
Sent from the gradle-user mailing list archive at Nabble.com.
