Hi,
I found this plugin which might get things working with m2e :
https://github.com/SciSysUK/m2eclipse-maveneclipse
From the project page:
"Applies POM.xml configuration defined against the maven-eclipse-plugin
to m2e eclipse projects. Using this plugin it is possible to define
additional eclipse settings in a consistent manner whilst retaining back
compatibily with users that do not run eclipse with m2e."
Taken from
http://stackoverflow.com/questions/10696170/configure-eclipse-formatter-with-m2e
I haven't tried it myself though.
Bertrand
On 25/09/2012 9:37 AM, Martijn Dashorst wrote:
I'm not sure who is using eclipse or some other IDE, but currently I
don't have the proper formatting settings in my local checkout of
Wicket. AFAIR we used to have the formatting rules specified.
I don't know whether m2eclipse supports updating the eclipse
formatting settings from a jar file, but fortunately the
maven-eclipse-plugin does (and isn't a resource hog for your average
day Java coding).
At topicus we have a jar file (topicus-eclipse-settings-0.1.jar) that
contains all settings for eclipse that are relevant for working in a
team: centralized formatting rules, etc. We deploy this through our
maven repository and let the maven-eclipse-plugin update these
workspace settings whenever you run mvn eclipse:eclipse
I consider this a really good way of using and sharing settings, and
I'd like to propose to do the same for Wicket.
For this to happen, I would like to create a project in our subversion
repository (wicket-common/wicket-eclipse-settings/) that contains our
formatting settings, get the settings from one of you guys, release it
to maven central, and let the maven-eclipse-plugin depend on it such
that with a new mvn eclipse:eclipse the project will have the correct
settings.
The benefit is that the eclipse settings are no longer part of the
"official" wicket checkout, and are only applied when someone is using
Eclipse—hence no longer 'polluting' the tree.
Who is with me?
Martijn
