On May 9, 2009, at 1:59 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.
Here's the scenario I'm facing. I want to upload a regular jar to a
maven repo, but I can't use maven unless I include the war plugin,
and including the war plugin causes the default build to generate a
war and not a jar. So to upload a jar to a maven repository I have
to a) use the war plugin even though I'm not building a war, and b)
turn off the 'war'ing to generate a jar. This seems like bug to me
as I would have expected the two concepts to be independent (at
least from a users perspective).
Sorry. I wasn't reading your initial posting properly. In 0.5.2 you
don't need to use the maven plugin to upload to a Maven repository. In
0.6 you need to use the plugin. But your point is a completely
different one. That was a bug in the 0.6 branch which is fixed now.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
