> 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. > 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? > Many thanks for your feedback. Apologies for taking so long to reply. > No worries. One other thing that would make the documentation easier for new users is to include a captions on code examples to identify the file that is being edited. This would especially help for chapter 17 (multi project builds) where some examples are for settings.gradle, and others for the various build files. Some of the examples mention the file in the text, but some don't (see 17.1.1). Cheers Andrew
