>>
>> @Claus Yes, I wasn't questioning the schedule at all.
>>
>> However, if the code is validated with checkstyle 8.40 and not 8.43, I was
>> wondering if those new (or modified) rules do make sense for camel or we
>> should skip them when working on the
> On 21 Jun 2021, at 16:00, Guillaume Nodet wrote:
>
> @Claus Yes, I wasn't questioning the schedule at all.
>
> However, if the code is validated with checkstyle 8.40 and not 8.43, I was
> wondering if those new (or modified) rules do make sense for camel or we
> sho
@Claus Yes, I wasn't questioning the schedule at all.
However, if the code is validated with checkstyle 8.40 and not 8.43, I was
wondering if those new (or modified) rules do make sense for camel or we
should skip them when working on the upgrade for 3.12. Babak, can you give
some hints
ese
>>>> errors a bit faster or eventually revert and postpone to 3.12.0, because
>>>> the sourcecheck is part of the release profile.
>>>>
>>>> https://github.com/apache/camel/blob/main/pom.xml#L375
>>>>
>>>> Thanks
>>
> > Thanks
> > >
> > > Il giorno lun 21 giu 2021 alle ore 00:13 Babak Vahdat <
> > > babak.vah...@swissonline.ch> ha scritto:
> > >
> > > > Hi
> > > >
> > > > Upgrading the Maven plugin com.puppycrawl.tools:checkstyle f
ha scritto:
> >
> > > Hi
> > >
> > > Upgrading the Maven plugin com.puppycrawl.tools:checkstyle from the
> > > version 8.40 to 8.43 has caused tons of checkstyle validations to fail.
> > >
> > > I'm on it and need to find some mo
:
>
> > Hi
> >
> > Upgrading the Maven plugin com.puppycrawl.tools:checkstyle from the
> > version 8.40 to 8.43 has caused tons of checkstyle validations to fail.
> >
> > I'm on it and need to find some more free cycle to fix the remaining ones.
> >
> >
giu 2021 alle ore 00:13 Babak Vahdat <
babak.vah...@swissonline.ch> ha scritto:
> Hi
>
> Upgrading the Maven plugin com.puppycrawl.tools:checkstyle from the
> version 8.40 to 8.43 has caused tons of checkstyle validations to fail.
>
> I'm on it and need to find so
Hi
Upgrading the Maven plugin com.puppycrawl.tools:checkstyle from the version
8.40 to 8.43 has caused tons of checkstyle validations to fail.
I'm on it and need to find some more free cycle to fix the remaining ones.
Babak
oscerd commented on issue #2: Bump checkstyle from 7.6.1 to 8.18 in /parent
URL:
https://github.com/apache/camel-kafka-connector/pull/2#issuecomment-562055457
@dependabot ignore this dependency
This is an automated message
dependabot[bot] closed pull request #2: Bump checkstyle from 7.6.1 to 8.18 in
/parent
URL: https://github.com/apache/camel-kafka-connector/pull/2
This is an automated message from the Apache Git Service.
To respond to the
dependabot[bot] commented on issue #2: Bump checkstyle from 7.6.1 to 8.18 in
/parent
URL:
https://github.com/apache/camel-kafka-connector/pull/2#issuecomment-562055476
OK, I won't notify you about com.puppycrawl.tools:checkstyle again, unless
you re-open this PR or update it yoursel
dependabot[bot] opened a new pull request #2: Bump checkstyle from 7.6.1 to
8.18 in /parent
URL: https://github.com/apache/camel-kafka-connector/pull/2
Bumps [checkstyle](https://github.com/checkstyle/checkstyle) from 7.6.1 to
8.18.
Release notes
*Sourced from [checkstyle&#
davsclaus merged pull request #177: Make code generators checkstyle compliant
URL: https://github.com/apache/camel-quarkus/pull/177
This is an automated message from the Apache Git Service.
To respond to the message, please
asf-ci commented on issue #177: Make code generators checkstyle compliant
URL: https://github.com/apache/camel-quarkus/pull/177#issuecomment-528389036
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/131
jamesnetherton opened a new pull request #177: Make code generators checkstyle
compliant
URL: https://github.com/apache/camel-quarkus/pull/177
This is an automated message from the Apache Git Service.
To respond to the
lburgazzoli merged pull request #175: Fix checkstyle violations
URL: https://github.com/apache/camel-quarkus/pull/175
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
asf-ci commented on issue #175: Fix checkstyle violations
URL: https://github.com/apache/camel-quarkus/pull/175#issuecomment-528315056
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/129
oscerd commented on issue #175: Fix checkstyle violations
URL: https://github.com/apache/camel-quarkus/pull/175#issuecomment-528283711
I'm ok with any configuration that doens't make the build fail for code
styl
jamesnetherton opened a new pull request #175: Fix checkstyle violations
URL: https://github.com/apache/camel-quarkus/pull/175
I think the extension generator stuff contributes a little bit to this,
because it doesn't add license headers to all files and some of the generated
oscerd closed issue #14: Configure checkstyle
URL: https://github.com/apache/camel-quarkus/issues/14
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
lburgazzoli merged pull request #88: Enable checkstyle and license checks
URL: https://github.com/apache/camel-k-runtime/pull/88
This is an automated message from the Apache Git Service.
To respond to the message, please log
lburgazzoli opened a new issue #14: Configure checkstyle
URL: https://github.com/apache/camel-quarkus/issues/14
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
Github user aldettinger closed the pull request at:
https://github.com/apache/camel/pull/1958
---
GitHub user aldettinger opened a pull request:
https://github.com/apache/camel/pull/1958
CAMEL: Fixed checkstyle errors for connectors
Just cleaned those checkstyle errors in the `connectors` directory.
You can merge this pull request into a Git repository by running:
$ git
Thanks Zoran. You seem to provide it. I have tested on Windows(yes it was
windows), it is working.
Thanks
On Tue, Jun 6, 2017 at 4:57 PM, Zoran Regvart wrote:
> Hi Önder,
> there is a small beanshell script that converts the header-*.txt files
> into string expressions expected by che
Hi Önder,
there is a small beanshell script that converts the header-*.txt files
into string expressions expected by checkstyle[1].
It somewhat strange process but the idea is that there is only one
header.txt[2] and all other header-*.txt files are generated from it.
My guess is that I haven&#
Hi,
I am building on my local.
and if i build buildingtools and after try to run
- mvn clean install -Psourcecheck
I get lots of checkstyle errors.
However, if i go to my local repo and delete camel-buildtools folder and
afterwards if i run the build for the same component.
Checkstyle seems
Hi Önder,
yeah, snapshots are at repository.apache.org[1] perhaps you can get
that Archiva instance to proxy[2] to:
https://repository.apache.org/content/groups/public/
zoran
[1]
https://repository.apache.org/#nexus-search;gav~org.apache.camel~camel-core~2.20.0-SNAPSHOT~~
[2] https://archiva.ap
Hi Zoran,
apparently we have archiava running which has not been maintained for a
long time.
i figured out that archiava has access to maven public repo. so i changed
my maven's setting.xml to point that archiava. however i am failing to run
mvn install. i guess it does not have access to snapsho
Hi Önder,
that's a real bummer :(
Perhaps you you can make the case that it's needed for work and it
ruins everybody's productivity and convince the IT to either pass
certain sites (like repo.maven.org and repository.apache.org), or can
run a Maven repository manager (like Nexus) and the IT can al
1.94K --.-KB/sin 0s
2017-05-15 22:00:39 (55.7 MB/s) -
‘camel-buildtools-2.20.0-20170511.100836-14.jar.3’ saved [1990/1990]
On Mon, May 15, 2017 at 2:56 PM, onders
wrote:
> I dont have access without proxy
>
>
>
> --
> View this message in context: http://camel.46542
I dont have access without proxy
--
View this message in context:
http://camel.465427.n5.nabble.com/checkstyle-plugin-problem-tp5799504p5799538.html
Sent from the Camel Development mailing list archive at Nabble.com.
On Mon, May 15, 2017 at 1:26 PM, onders wrote:
> Any suggestions are welcome.
if wget-ed jars are OK, perhaps you can put nonProxyHosts[1]
configuration for repo.maven.apache.org?
zoran
[1] https://maven.apache.org/guides/mini/guide-proxies.html
--
Zoran Regvart
> View this message in context:
> http://camel.465427.n5.nabble.com/checkstyle-plugin-problem-tp5799504p5799532.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
i can do.
Any suggestions are welcome.
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/checkstyle-plugin-problem-tp5799504p5799532.html
Sent from the Camel Development mailing list archive at Nabble.com.
On Mon, May 15, 2017 at 10:01 AM, onders
wrote:
> I have done but no success.
> I'll try what Claus suggested.
if that fails ping me, I'd like to help you and see if there is
anything we can do to prevent developers running into issues,
zoran
--
Zoran Regvart
Hi Önder,
On Mon, May 15, 2017 at 10:00 AM, Onder SEZGIN wrote:
> I have to manually update those jar by downloading them via wget.
>
> Do you know a workaround for such issues?
Could it be that you have a proxy configured to scan for viruses? I've
seen instances of security appliances that inje
I have done but no success.
I'll try what Claus suggested.
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/checkstyle-plugin-problem-tp5799504p5799510.html
Sent from the Camel Development mailing list archive at Nabble.com.
> > ---
> > [INFO] Deleting D:\dev\github\camel\components\camel-undertow\target
> > [INFO]
> > [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven) @
> > camel-undertow
> > ---
> > [INFO]
> > [INFO] --- maven-bundle-plugin:3.3.0:cleanVersions (vers
Hi Önder,
this should be due to older version of camel-buildtools in your local
maven repository, try `mvn install` just from `buildingtools` first,
if you still have issues ping me on IRC so we can troubleshoot,
zoran
On Mon, May 15, 2017 at 8:53 AM, onders wrote:
> When i pulled the source fro
[INFO] --- maven-bundle-plugin:3.3.0:cleanVersions (versions) @
> camel-undertow -
> --
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.17:checkstyle (default-cli) @
> camel-underto
> w ---
> [INFO] Starting audit...
> [ERROR]
> D:\dev\github\camel\components\camel-undertow\src
3.0:cleanVersions (versions) @
camel-undertow -
--
[INFO]
[INFO] --- maven-checkstyle-plugin:2.17:checkstyle (default-cli) @
camel-underto
w ---
[INFO] Starting audit...
[ERROR]
D:\dev\github\camel\components\camel-undertow\src\main\java\org\apache\c
amel\component\undertow\cl
Github user zregvart closed the pull request at:
https://github.com/apache/camel/pull/1656
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
GitHub user zregvart opened a pull request:
https://github.com/apache/camel/pull/1656
CAMEL-11194 Upgrade Checkstyle and update rules
This upgrades Checkstyle to the latest version currently available, refines
the way license header in properties files are handled and sets the
Github user zregvart closed the pull request at:
https://github.com/apache/camel/pull/1347
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
GitHub user zregvart opened a pull request:
https://github.com/apache/camel/pull/1347
CAMEL-10595 Fix Checkstyle in camel-salesforce-maven-plugin
Fixes checkstyle error originating in #1334
You can merge this pull request into a Git repository by running:
$ git pull https
check style issues?
>
>
>> On Apr 29, 2016, at 12:45 AM, Claus Ibsen wrote:
>>
>> I upgraded checkstyle to latest release that supports better lambdas
>> so the styling is correct.
>>
>> But the new rules find new issues which we did not have reports about
&
Is there a JIRA for this that I can use for PRs if I get a chance to go fix
some of the new check style issues?
> On Apr 29, 2016, at 12:45 AM, Claus Ibsen wrote:
>
> I upgraded checkstyle to latest release that supports better lambdas
> so the styling is correct.
>
> But
I upgraded checkstyle to latest release that supports better lambdas
so the styling is correct.
But the new rules find new issues which we did not have reports about
before. So there is more errors to fix now.
I pushed on master so people can help fix the errors over the foreseable time
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/740
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
GitHub user lburgazzoli opened a pull request:
https://github.com/apache/camel/pull/740
[CAMEL-9437] Fix checkstyle indentation violation for generated API test
cases
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lburgazzoli
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/542
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
checkstyle upgrade. You are
welcome to work on a patch for that to.
On Wed, Jun 10, 2015 at 1:52 AM, unleashed85 wrote:
> What is the projects policy with using Java7 syntax (specifically try with
> resources)? I assumed it was allowed but am getting errors when running mvn
> compile -Pso
What is the projects policy with using Java7 syntax (specifically try with
resources)? I assumed it was allowed but am getting errors when running mvn
compile -Psourcecheck
I added a try with resources to the camel-rabbitmq component but the
maven-checkstyle-plugin version 2.9.1 doesn't all
GitHub user brreitme opened a pull request:
https://github.com/apache/camel/pull/542
Checkstyle fixes in camel-rabbitmq component.
This will fix all but 4 issues in the camel-rabbitmq component reported by
checkstyle. The remaining issues are due to maven-checkstyle-plugin version
I noticed this error a few days ago and the errors are still there as of today.
It looks like the changes come from Dhiraj, so I'm cc'ing him.
The commit log shows him as the author and committer of the change and
I am wondering if this was a pull request and merged without resetting
the commiter/
Just a heads up that we got a bunch of CS issues on master. It seems
related to the new camel-component-api
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://
2014-05-28 14:38 GMT+02:00 Matt Sicker :
> Doesn't the checkstyle plugin add a bit of time to the build? I can see why
> it's not default!
>
It adds more processing but not building with the check on the jenkins
also leaves those violation unnoticed until someone runs the
Doesn't the checkstyle plugin add a bit of time to the build? I can see why
it's not default!
On 28 May 2014 06:54, Willem Jiang wrote:
> Current the checkstyle verification only run when we do the release.
>
> We had some argument about enable the -Psourcecheck by defau
Current the checkstyle verification only run when we do the release.
We had some argument about enable the -Psourcecheck by default, but we didn’t
have the agreement with that.
If you are using eclipse, the check style plugin can work very well without
running any mvn command :)
--
Willem
Hi,
I saw Willem fixing some of my checkstyle violation (Thanks Willem)
and realized belately that the checkstyle is not active by default in
camel when doing mvn clean install.
I thought that the checkstyle was enabled as in cxf by default.
When I ran mvn -Psourcecheck, I saw some additional
ou can resume the build with the
> command
> [ERROR] mvn
>
> -rf :camel-buildtools
>
>
>
>
> --
> Claus Ibsen
> -
> FuseSource
> Email:
> cibsen@
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://d
> -rf :camel-buildtools
>
>
>
>
> --
> Claus Ibsen
> -
> FuseSource
> Email:
> cibsen@
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
--
View this message in context:
http://camel.465427.n5.nabble.com/Checkstyle-plugin-no-longer-works-tp5719570p5719648.html
Sent from the Camel Development mailing list archive at Nabble.com.
Hi Claus,
I just tried to run the "mvn clean install -Dtest=false" from the camel root
directory, I didn't get the error that you have.
Here is my system info
Apache Maven 3.0.3 (r1075438; 2011-03-01 01:31:09+0800)
Maven home: /usr/share/maven
Java version: 1.6.0_31, vendor: Apple Inc.
Java hom
Hi
This problem continues this morning. Doing a mvn clean install
-Dtest=false renders this problem now
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total
gt;
> Babak
>
>
> Claus Ibsen-2 wrote
> > Hi
> >
> > There must been some changes to our pom.xml files recently, since the
> > checkstyle plugin no longer works. eg running on camel-core gives an
> > error.
> >
> >
> > davsclaus:~
self).
Babak
Claus Ibsen-2 wrote
> Hi
>
> There must been some changes to our pom.xml files recently, since the
> checkstyle plugin no longer works. eg running on camel-core gives an
> error.
>
>
> davsclaus:~/workspace/camel/camel-core$ mvn compile -Psourcecheck
>
Hi there,
Are there any intentions to ditch checkstyle in favor of sonar. To me,
would be good to remove the checkstyle plugin from the poms.
Cheers,
Bruno Barin
Purchasing/Warranty Business Support
Toyota Motor Europe
60 Avenue du Bourget,
1140 Brussels, Belgium
Ph: +32 (0) 2 745 5606
ng this also.
I always do a full mvn clean install -Dtest=false, in the morning.
But I suspect some pom.xml commits caused this.
> Babak
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Checkstyle-plugin-no-longer-works-tp5719570p5719572.ht
Good morning
I've experienced the same as well. The workaround for me was to go to
../buildingtools and do a "maven clean install" beforehand. Then it works
again.
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/Checkstyle-plugin-no-longer-works-tp
[
https://issues.apache.org/jira/browse/CAMEL-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-4563.
Resolution: Fixed
Fix Version/s: 2.9.0
Thanks
> Checkstyle fixes in o
checkstyle changes.
> Checkstyle fixes in osgi integration tests.
> ---
>
> Key: CAMEL-4563
> URL: https://issues.apache.org/jira/browse/CAMEL-4563
> Project: Camel
> Is
Checkstyle fixes in osgi integration tests.
---
Key: CAMEL-4563
URL: https://issues.apache.org/jira/browse/CAMEL-4563
Project: Camel
Issue Type: Improvement
Components: osgi, tests
There is a fair number of checkstyle issues on trunk on camel-core. I
suspect its due some of the latest refactorings.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
In CXF the build fails when there are checkstyle errors. I think that is
a good idea.
Of course this can only be done when we are at 0 errors for a moment.
But we could aim to do that for 2.9 or 3.0.
Christian
Am 28.08.2011 04:09, schrieb Johan Edstrom:
Would a tag+IDE cleanup be something
rting web tooling
being able to display them.
However its just much easier to run the cmd from the command line once
in a while.
> Christian
>
>
> Am 27.08.2011 18:29, schrieb Claus Ibsen:
>>
>> Hi
>>
>> There is a fair number of checkstyle issues on trunk on
ug 27, 2011, at 10:29 AM, Claus Ibsen wrote:
> Hi
>
> There is a fair number of checkstyle issues on trunk on camel-core. I
> suspect its due some of the latest refactorings.
>
>
> --
> Claus Ibsen
> -
> FuseSource
> Email: cib...@fusesource.com
i
>>
>> There is a fair number of checkstyle issues on trunk on camel-core. I
>> suspect its due some of the latest refactorings.
>>
>>
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.co
Ok will check on Monday.
Can the issues be seen somewhere on the web or only in eclipse?
Christian
Am 27.08.2011 18:29, schrieb Claus Ibsen:
Hi
There is a fair number of checkstyle issues on trunk on camel-core. I
suspect its due some of the latest refactorings.
--
Christian Schneider
Hi
There is a fair number of checkstyle issues on trunk on camel-core. I
suspect its due some of the latest refactorings.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author
ign checkstyle versions between maven and eclipse
> ---
>
> Key: CAMEL-3918
> URL: https://issues.apache.org/jira/browse/CAMEL-3918
> Project: Camel
> Issue Type: Improvement
>
ld system" component in JIRA would be better of
these kinds of things. Tooling seems to be more for the tooling Camel may
provide, I think.
> Align checkstyle versions between maven and eclipse
> ---
>
> Key: CAMEL-3918
&g
[
https://issues.apache.org/jira/browse/CAMEL-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea resolved CAMEL-3918.
Resolution: Fixed
Patch applied in r1097908 with thanks to Dan Kulp.
> Align checkst
r if this fits these kind of issues
as well?
> Align checkstyle versions between maven and eclipse
> ---
>
> Key: CAMEL-3918
> URL: https://issues.apache.org/jira/browse/CAMEL-3918
>
[
https://issues.apache.org/jira/browse/CAMEL-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-3918:
---
Component/s: tooling
Description: If you install a fresh eclipse and install checkstyle
[
https://issues.apache.org/jira/browse/CAMEL-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea reassigned CAMEL-3918:
--
Assignee: Hadrian Zbarcea
> Align checkstyle versions between maven and ecli
Align checkstyle versions between maven and eclipse
---
Key: CAMEL-3918
URL: https://issues.apache.org/jira/browse/CAMEL-3918
Project: Camel
Issue Type: Improvement
Reporter
[
https://issues.apache.org/jira/browse/CAMEL-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp updated CAMEL-3918:
---
Attachment: camel-checkstyle.patch
> Align checkstyle versions between maven and ecli
Hi,
I try to format my code in Eclipse to make this in concordance with
checkstyle rules but it fails.
Scenario :
1) In eclipse, I have imported the following file to format the code :
https://svn.apache.org/repos/asf/camel/trunk/etc/eclipse/ActiveMQCodeFormatter.xml
2) I format my java classes
/checkstyle (= Plugin CheckStyle)
template.checkstyle-config.xml
org.eclipse.jdt.core.prefs
Remark : I propose also to remove unnecessary files like
ActiveMQCodeFormatter.xml, ...
Regards,
Charles
On Tue, Apr 28, 2009 at 9:54 AM, Gert Vanthienen
wrote:
> Charles,
>
> I think you are lo
h version of Eclipse,
> ???
>
> Regards,
>
> Charles
>
> On Tue, Apr 28, 2009 at 9:26 AM, Claus Ibsen wrote:
>
>> Hi
>>
>> Take a look in the camel source. There should be some checkstyle files
>> that Eclipse can use.
>>
>> In this fo
arles
On Tue, Apr 28, 2009 at 9:26 AM, Claus Ibsen wrote:
> Hi
>
> Take a look in the camel source. There should be some checkstyle files
> that Eclipse can use.
>
> In this folder
> /buildingtools/src/main/resources$
>
>
>
> On Tue, Apr 28, 2009 at 9:19
Hi
Take a look in the camel source. There should be some checkstyle files
that Eclipse can use.
In this folder
/buildingtools/src/main/resources$
On Tue, Apr 28, 2009 at 9:19 AM, Charles Moulliard wrote:
> Hi,
>
> I'm looking for a template that I can use in Eclipse Ganymed
Hi,
I'm looking for a template that I can use in Eclipse Ganymede 3.4 allowing
to format my code according to checkstyle rules which are supported by
Apache Camel community.
Is such template existing ?
Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Comm
g the uber pom.xml that
{code} mvn -Psetup.eclipse {code}
should create the magic with a checkstyle configuration applied to a
workspace. but it assumed a few things about workspace locations and etc
which did not seem to hold for me.
On Tue, Jan 27, 2009 at 23:49, cmoulliard wrote:
>
>
96 matches
Mail list logo
