Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
2.0-beta-1
-
None
Description
The latest multi-module tip shows the following:
<reporting> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-checkstyle-plugin</artifactId> <configuration> <configLocation>whizbang/checkstyle.xml</configLocation> <headerLocation>whizbang/LICENSE.txt</headerLocation> </configuration> <dependencies> <dependency> <groupId>com.example.whizbang</groupId> <artifactId>build-tools</artifactId> <version>1.0</version> </dependency> </dependencies> </plugin> </plugins> </reporting>
This is invalid according to the latest 2.0.2 POM schema. <dependencies> is not supported in reporting plugins.
So it seems impossible to provide a custom config in a multi-module build without using a network URL as we cannot use File or classpath.
Attachments
Issue Links
- depends upon
-
MSITE-444 reporting section should allow additional dependencies in plugins as well
- Closed