[jbosstools-issues] [JBoss JIRA] (JBIDE-15132) Have Maven projects automatically apply project defined code style, formatting and templates

[Fred Bricon (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-15132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Bricon updated JBIDE-15132:
--------------------------------

    Fix Version/s: LATER

    
> Have Maven projects automatically apply project defined code style, formatting and templates
> --------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-15132
>                 URL: https://issues.jboss.org/browse/JBIDE-15132
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: maven
>         Environment: Eclipse
>            Reporter: Sanne Grinovero
>             Fix For: LATER
>
>
> Very often we need to re-import Maven projects, and m2 reconfigures it *almost* all correctly. Latest Eclipse even auto-shares the git repository, which solved one very annoying and repetitive step, but there is one left:
> most of our projects use a custom formatting rule, code cleanup rules, and templates to generate some common elements like the project specific copyright headers.
> For example Hibernate recommends to download three files from:
> https://community.jboss.org/wiki/ContributingToHibernateUsingEclipse
> these need to be imported in eclipse, and applied to each project.
> Nowadays I need to re-apply these each and every time M2 needs to reconfigure the project; it would be absolutely amazing if I could commit these three files in the project and refer to them from my pom.xml?
> We already have something like that working for checkstyle: m2 detects the need to download a plugin, and applies the custom rules. But that's not enough.
> Benefit:
> not just our own time, but also make life of each and every occasional contributor much easier to get started.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira