You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Bruce Snyder (JIRA)" <ji...@apache.org> on 2007/07/25 17:18:50 UTC
[jira] Created: (SM-1009) Create a code formatter profile for
import into Eclipse
Create a code formatter profile for import into Eclipse
--------------------------------------------------------
Key: SM-1009
URL: https://issues.apache.org/activemq/browse/SM-1009
Project: ServiceMix
Issue Type: Task
Affects Versions: 3.2
Reporter: Bruce Snyder
The new Checkstyle code convention checking is nice, but it's a major pain when it keeps causing a build to fail. We should create a code formatter profile for Eclipse to automatically format code according to the Checkstyle code conventions we're using. This will prevent a lot of the issues I'm encountering.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1009) Create a code formatter profile for
import into Eclipse
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Snyder resolved SM-1009.
------------------------------
Resolution: Fixed
Fix Version/s: 3.2
Committed revision [559490|http://svn.apache.org/viewvc?view=rev&revision=559490].
> Create a code formatter profile for import into Eclipse
> --------------------------------------------------------
>
> Key: SM-1009
> URL: https://issues.apache.org/activemq/browse/SM-1009
> Project: ServiceMix
> Issue Type: Task
> Affects Versions: 3.2
> Reporter: Bruce Snyder
> Assignee: Bruce Snyder
> Fix For: 3.2
>
> Attachments: SM-1009.patch.txt
>
>
> The new Checkstyle code convention checking is nice, but it's a major pain when it keeps causing a build to fail. We should create a code formatter profile for Eclipse to automatically format code according to the Checkstyle code conventions we're using. This will prevent a lot of the issues I'm encountering.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-1009) Create a code formatter profile for
import into Eclipse
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Snyder reassigned SM-1009:
--------------------------------
Assignee: Bruce Snyder
> Create a code formatter profile for import into Eclipse
> --------------------------------------------------------
>
> Key: SM-1009
> URL: https://issues.apache.org/activemq/browse/SM-1009
> Project: ServiceMix
> Issue Type: Task
> Affects Versions: 3.2
> Reporter: Bruce Snyder
> Assignee: Bruce Snyder
>
> The new Checkstyle code convention checking is nice, but it's a major pain when it keeps causing a build to fail. We should create a code formatter profile for Eclipse to automatically format code according to the Checkstyle code conventions we're using. This will prevent a lot of the issues I'm encountering.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-1009) Create a code formatter profile for
import into Eclipse
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Snyder updated SM-1009:
-----------------------------
Attachment: SM-1009.patch.txt
Attaching the patch to add the {{smx-eclipse-code-conventions.xml}} file to the repo.
> Create a code formatter profile for import into Eclipse
> --------------------------------------------------------
>
> Key: SM-1009
> URL: https://issues.apache.org/activemq/browse/SM-1009
> Project: ServiceMix
> Issue Type: Task
> Affects Versions: 3.2
> Reporter: Bruce Snyder
> Assignee: Bruce Snyder
> Attachments: SM-1009.patch.txt
>
>
> The new Checkstyle code convention checking is nice, but it's a major pain when it keeps causing a build to fail. We should create a code formatter profile for Eclipse to automatically format code according to the Checkstyle code conventions we're using. This will prevent a lot of the issues I'm encountering.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.