[
https://issues.apache.org/jira/browse/MAHOUT-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730825#action_12730825
]
Benson Margulies commented on MAHOUT-144:
-----------------------------------------
The buildtools directory builds a JAR which can be in the classpath of plugins
in other projects and in eclipse. The 'parent' project (called 'maven' in
mahout) can't build a JAR and so can't supply anything to the classpath.
See
http://dssheep.blogspot.com/2008/12/maven-eclipse-checkstyle-pmd-oy-vey.html
and the page it links to.
> Some maven refactoring and prep for enforcing code style
> --------------------------------------------------------
>
> Key: MAHOUT-144
> URL: https://issues.apache.org/jira/browse/MAHOUT-144
> Project: Mahout
> Issue Type: Bug
> Affects Versions: 0.2
> Reporter: Benson Margulies
> Attachments: miscbuildtools.patch.txt
>
>
> The attached does a few things:
> 1) sorts out the maven parents: now the modules parent to 'maven', and
> 'maven' parents to the top-level project.
> 2) The release management in the top-level POM is in a profile.
> 3) the version of 'maven' is consistent with other version numbers.
> 4) the source control URLs are corrected.
> 5) a new buildtools module to hold pmd and checkstyle config.
> 6) dependencyManagement in the parent, initially just for lucene.
> 7) backup to current lucene release. -Dlucene.version is there for those who
> really want to use 2.9-SNAPSHOT.
> 8) a profile, sourcecheck, that turns on checkstyle and pmd. This creates a
> giant pile of complaints.
> The next step in this process would be to come up with a set of checkstyle
> and pmd rules consistent with the community's desires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
