Re: Maven PMD, Checkstyle multimodel configuration.
I dont know about the instructions but an example config for checkstyle with a build tools config in a multi module project can be found here https://github.com/simpligility/ksoap2-android hth Manfred simpligility.com Artem Barger wrote on 2016-10-26 08:16: > Hi all, > > I'm trying to follow the tutorial regarding multimodule configuration for > PMD and checkstyle plugins from here: > https://maven.apache.org/plugins-archives/maven-pmd-plugin-LATEST/examples/multi-module-config.html > > And I have a problem with last instruction, once I've done suggested > configuration and trying to run "mvn site" it fails, since it has missing > dependency of "build-tools". It looks like I have to run "mvn install" > prior to "mvn site" in order to have "mvn site" succeeded. > > Does my observation correct? What am I doing wrong? > > Best regards, > Artem Barger. > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven PMD, Checkstyle multimodel configuration.
Hi all, I'm trying to follow the tutorial regarding multimodule configuration for PMD and checkstyle plugins from here: https://maven.apache.org/plugins-archives/maven-pmd-plugin-LATEST/examples/multi-module-config.html And I have a problem with last instruction, once I've done suggested configuration and trying to run "mvn site" it fails, since it has missing dependency of "build-tools". It looks like I have to run "mvn install" prior to "mvn site" in order to have "mvn site" succeeded. Does my observation correct? What am I doing wrong? Best regards, Artem Barger.
[maven-javadoc-plugin] Aggregating Javadocs from Dependency Sources
Hello, I followed the guide https://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate-dependency-sources.html to generate an aggregated javadoc for a multi-module project. I think, it should be mentioned in this guide that the distribution project (Named 'project-distro' in the example) generating the aggregated javadoc should be of packaging type 'jar' and not 'pom'. Even though the latter is the usual packaging type for this kind of project (in my experience), since there are no sources to compile. As a feature request I would like this example to also work on a distribution project with packaging type 'pom'. Currently nothing is being generated, because the project is not a 'Java classpath-capable package'. [INFO] --- maven-javadoc-plugin:2.10.4:jar (module-javadoc-jar) @ distribution --- [INFO] Not executing Javadoc as the project is not a Java classpath-capable package Is this the right mail list or should I post this in the 'Maven Issues List'?
