[
https://jira.codehaus.org/browse/MCHECKSTYLE-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=306835#comment-306835
]
Dennis Lundberg commented on MCHECKSTYLE-180:
---------------------------------------------
Well, the buildtools module doesn't need a lot of plugins to build, but I get
your point.
I suggest that you follow my earlier suggestion and make the buildtools module
an entirely separate project. It would look something like this:
* corporate-parent version 1
* specifies plugin versions
* buildtools project
* has corporate-parent:1 as its parent
* corporate-parent version 2
* specifies plugin versions
* specifies buildtools version, preferably in a property so that it can be
easily overridden
* adds buildtools as a dependency to Checkstyle plugin in
build/pluginManagement
* multi-module-project
* has corporate-parent:2 as its parent
* uses Checkstyle plugin in build/plugins
> Multimodule configuration example does not work
> -----------------------------------------------
>
> Key: MCHECKSTYLE-180
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-180
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
> Affects Versions: 2.9.1
> Environment: Maven 3.0.4, Ubuntu 12.04 64bit
> Reporter: Zlika
> Attachments: test-buildtools.zip
>
>
> I followed the multimodule example from
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html,
> but it does not seem to work.
> With the attached test case, when I do "mvn verify" the build fail. It seems
> that Maven wants to download the "buildtool" module from the local repository
> (instead of building it), but it cannot find it.
> {noformat}
> mvn verify
> [INFO] Scanning for projects...
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] test-parent
> [INFO] Build tools
> [INFO] test-test
> [INFO]
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building test-parent 0.1-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.9.1:check (default) @ test-parent ---
> Downloading:
> http://repository.apache.org/snapshots/testgroup/test-buildtools/0.1-SNAPSHOT/maven-metadata.xml
> Downloading:
> http://repository.apache.org/snapshots/testgroup/test-buildtools/0.1-SNAPSHOT/test-buildtools-0.1-SNAPSHOT.jar
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] test-parent ....................................... FAILURE [3.345s]
> [INFO] Build tools ....................................... SKIPPED
> [INFO] test-test ......................................... SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 3.958s
> [INFO] Finished at: Mon Aug 20 14:39:55 CEST 2012
> [INFO] Final Memory: 6M/15M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1:check (default) on
> project test-parent: Execution default of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1:check failed: Plugin
> org.apache.maven.plugins:maven-checkstyle-plugin:2.9.1 or one of its
> dependencies could not be resolved: Could not find artifact
> testgroup:test-buildtools:jar:0.1-SNAPSHOT in apache.snapshots
> (http://repository.apache.org/snapshots) -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
