[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-6343) Create a "sanity check plugin/feature" tool for running on integration builds
Max Andersen (JIRA)
jira-events at lists.jboss.org
Wed Oct 20 05:28:54 EDT 2010
[ https://jira.jboss.org/browse/JBIDE-6343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Max Andersen updated JBIDE-6343:
--------------------------------
Priority: Minor (was: Major)
Assignee: Max Andersen
Fix Version/s: 3.2.0.Beta2
(was: LATER)
> Create a "sanity check plugin/feature" tool for running on integration builds
> -----------------------------------------------------------------------------
>
> Key: JBIDE-6343
> URL: https://jira.jboss.org/browse/JBIDE-6343
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng
> Reporter: Max Andersen
> Assignee: Max Andersen
> Priority: Minor
> Fix For: 3.2.0.Beta2
>
>
> 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 contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list