On May 6, 2009, at 1:55 AM, Andrew Pietsch wrote:
In 0.6.x it seems that the install task of the maven plugin won't
work unless the war plugin is also used (i.e. the war plugin defines
the providedCompile and providedRuntime configurations).
Right, this is a breaking change.
I presume this is a bug? It seems strange to have to use the war
plugin to upload to a maven repository.
For uploading to a Maven repository we automatically generate the pom.
But this pom generation is customizable. To provide the pom for
customization, the Maven plugins adds domain objects to the project.
If you are not interested in maven uploading, you don't want to have
this.
- Hans
On a similar note, when writing my GWT plugin (for 0.5.2) it would
have been nice to use the 'provided' configurations without
requiring the use of the war plugin. This is particularly the case
when developing a GWT library that needs to be released as a jar but
still needs to define 'providedCompile' dependencies (e.g. gwt-
user.jar, gwt-dev-xxx.jar etc).
Given that, would it make sense for the 'provided' configurations to
be defined by the java plugin?
I see your use case. An alternative would be to have another plugin
which declares solely the provided stuff (The war plugin would
automatically apply it). Could you file a Jira for this with fix for
0.7?
Ok. Would you like me to include (or create a separate bug for) the
War/Maven issue?
Separate ones, if you still think that the behavior with the Maven
plugin is a bug.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
