L.S.,
We could also configure the Maven Eclipse plugin to generate per-project
code formatting rules while doing mvn eclipse:eclipse. The only
drawback is that it overwrites the .settings/org.eclipse.jdt.core.prefs
in the process, so we also have to specify the compiler compliance level
ourselves in the template prefs file. I gave it a quick try on my
machine and it seems to work fine this way.
Regards,
Gert
Jon Anstey wrote:
Spot on Ramon. You can also tell Maven where your Eclipse workspace actually
is like so
mvn -Psetup.eclipse -Declipse.workspace.dir=/path/to/your/workspace
On Tue, Jan 27, 2009 at 9:28 AM, Ramon Buckland <[email protected]>wrote:
cc'd to dev@
Thanks Charles, I have/had the same question.
Once it is in email I'll volunteer to push that to the wiki.
I know already that line width is set at 140 (thanks Claus).
In Eclipse I am using Sun standard formatting with change of 140 line
width.
It seems, by inspecting 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 <[email protected]> wrote:
Hi,
I would like to know the procedure to follow in order to format code to
be
published to camel project in Eclipse ?
Idem but to check style ?
Is the code formatted automatically during maven build process of Camel
project ?
Remarks :
- ActiveMQCodeFormatter.xml file exists under the folder etc/eclipse.
Maybe
this file could be rename to CamelCodeFormater ? Is it the file to be
used
in Eclipse to format the code ?
- Several files exist under buildingtools project ? Which one to be used
with eclipse to checkstyle (using checkstyle plugin / PMD plugin) ?
