maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerome Lacoste (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MECLIPSE-38) Allow custom code formatters to be written to .settings
Date Tue, 10 Apr 2007 15:49:46 GMT

    [ http://jira.codehaus.org/browse/MECLIPSE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92479
] 

Jerome Lacoste commented on MECLIPSE-38:
----------------------------------------

Some thoughts
* the set of rules and the formatter don't completely match.
* given a checkstyle XML file it is hard to know to which version of checkstyle the config
applies. The DTD hasn't changed for a while.
* an idea could be to have the tool that converts from checkstyle to eclipse outside of this
plugin. The tool could part of checkstyle or eclipse, or completely separate.

> Allow custom code formatters to be written to .settings
> -------------------------------------------------------
>
>                 Key: MECLIPSE-38
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-38
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.0
>            Reporter: Mark Hobson
>
> It'd be handy if there was a way of embedding custom code formatters to .settings.  Eclipse
can currently export code formatter profiles as a list of properties in an XML format, so
this file could be configured against the eclipse plugin for it to generate the corresponding
properties-format .settings/org.eclipse.jdt.core.prefs file.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message