<snip>
> I'd like to add a new option:
>
> 5. Introduce the concept of bundling, and publish those components that do
> not bundle (or imply) one of the other components:
> * If I produce a jvm component and a web application that bundles that
> library, then I almost always want to publish just the web application.
> * If I produce a web application and a jvm component and a j2ee
> application that bundles the web app and library, then I almost always want
> to publish the j2ee application
> * If I produce a java command-line application and a jvm component that
> is bundled, then I want to publish the application.
> * If I produce a jvm component and a native shared library, then I want
> to publish both.
> * If I produce a jvm library and a web application that does not
> include that library, then I want to publish both.
>
> Just a reminder: for all these options, there will be an underlying DSL where
> you can change whatever it is that Gradle publishes by default. So, I think
> the goal here is to choose an option that most often does the right thing
> (and preferring an approach where you add missing stuff rather than remove
> unwanted stuff). We don't need a solution that always does the right thing.
This would take bundling across subprojects into account?
Hans
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
