You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Albert Lee (Updated) (JIRA)" <ji...@apache.org> on 2012/02/03 17:55:54 UTC
[jira] [Updated] (OPENJPA-2090) factor out
openjpa-project/checkstyle.xml to own maven project
[ https://issues.apache.org/jira/browse/OPENJPA-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Albert Lee updated OPENJPA-2090:
--------------------------------
Fix Version/s: (was: 2.2.0)
2.3.0
Move fix version to 2.3.0 in preparation for 2.2.0 release.
> factor out openjpa-project/checkstyle.xml to own maven project
> --------------------------------------------------------------
>
> Key: OPENJPA-2090
> URL: https://issues.apache.org/jira/browse/OPENJPA-2090
> Project: OpenJPA
> Issue Type: Improvement
> Components: build / infrastructure
> Affects Versions: 2.2.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 2.3.0
>
>
> Currently our build scripts adopt a file-based way to reference our checkstyle configuration. With having lots of sub-modules with a deeply nested structure, this introduces quite some maintenance effort (e.g. when you try to add integration tests).
> There is another way to incorporate checkstyles for a project easily: serve them in an own maven artifact and include them as dependency of the maven-checkstyle-plugin.
> See OpenWebBeans and MyFaces of how this looks like:
> https://svn.apache.org/repos/asf/openwebbeans/build-tools/trunk/ for the openwebbeans-checkstyle-rules, and
> https://svn.apache.org/repos/asf/openwebbeans/trunk/pom.xml for how it's being used (see maven-checkstyle-plugin section)
> This can e.g. also be used to detect missing ASF headers in java files, etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira