[jbosstools-issues] [JBoss JIRA] (JBIDE-6343) Create a "sanity check plugin/feature" tool for running on integration builds

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen updated JBIDE-6343:
---------------------------------------

    Fix Version/s: LATER
                       (was: 4.2.0.Beta1)

    
> Create a "sanity check plugin/feature" tool for running on integration builds
> -----------------------------------------------------------------------------
>
>                 Key: JBIDE-6343
>                 URL: https://issues.jboss.org/browse/JBIDE-6343
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build
>            Reporter: Max Rydahl Andersen
>            Assignee: Max Rydahl Andersen
>            Priority: Minor
>             Fix For: LATER
>
>
> I keep seeing the following antipatterns or oversights happening in our codebase, most of them I believe we could mechanically check for.
> No duplicate names in .project since it makes it impossible to import into Eclipse
> bin folders should be svn:ignored and not be committed (causes problems when doing svn synchronization and all the .class files are showing up and some even commits it)
> things in svn:ignore should be committed (either someone overrode svn:ignore or the svn:ignore were added later)
> if pom.xml file exists target should be svn:ignored too.
> Execution environment should be specified in manifest.mf's

--
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