[
https://issues.apache.org/jira/browse/CAMEL-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Müller updated CAMEL-3268:
------------------------------------
Attachment: CAMEL-3268_maven-checkstyle-plugin_upgrade.patch
Attached the proposed patch for upgrading to maven-checkstyle-plugin 2.6 which
fixed the issue discussed in
[Nabble|http://camel.465427.n5.nabble.com/Building-Camel-with-Maven-3-td3351258.html].
I will commit it *AFTER* Camel 2.6 is release.
By working on this patch, I had two questions:
1) I'm wondering, why the files 'camel-checkstyle.xml',
'camel-checkstyle-supressions.xml', 'camel-eclipse-checkstyle',
'camel-eclipse-pmd' and 'camel-pmd-ruleset.xml' exists twice in this project
(they are identical). In the root folder and in 'src/main/resources'. Is there
any reason for?
2) Checkstyle 5.0 (which is used by the maven-checkstyle-plugin 2.6) introduces
a few new checks compared to Checkstyle 4.4 (which is used in
maven-checkstyle-plugin 2.3). This checks could also be useful for Camel. I
would like to add this new checks to the camel-checkstyle.xml file and disable
they. One of the core committer should check the new checks and enable they
afterward, if they are useful.
> Maven 3 to build source
> -----------------------
>
> Key: CAMEL-3268
> URL: https://issues.apache.org/jira/browse/CAMEL-3268
> Project: Camel
> Issue Type: Task
> Affects Versions: 2.5.0
> Reporter: Claus Ibsen
> Assignee: Christian Müller
> Priority: Minor
> Fix For: 2.7.0, 3.0.0
>
> Attachments: CAMEL-3268_maven-checkstyle-plugin_upgrade.patch
>
>
> It should be possible to build the project with Maven 3 without any issues.
> Dan Kulp says there is an issue with using old Maven 1 repo style.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.