[jbosstools-issues] [JBoss JIRA] (JBIDE-13125) discovery plugin cleanup
Max Rydahl Andersen (JIRA)
jira-events at lists.jboss.org
Wed Nov 28 12:01:24 EST 2012
[ https://issues.jboss.org/browse/JBIDE-13125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Max Rydahl Andersen updated JBIDE-13125:
----------------------------------------
Fix Version/s: 4.1.0.Alpha1
(was: 4.0.0.CR1)
> discovery plugin cleanup
> ------------------------
>
> Key: JBIDE-13125
> URL: https://issues.jboss.org/browse/JBIDE-13125
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha1
>
>
> Because of JBDS-2361 and JBIDE-12556 I spent some time reviewing the discovery plugin.xml and found a few items.
> I'll put my raw list in the comments, but here are the highlights:
> - new connector ID's should not use the same name as the feature they refer to; this is so project examples can refer to them as "the maven plugins" instead of "org.eclipse.m2e" when it might be a different name.
> - The word "Free" is added to some entries but not to others.
> - egit and egit.mylyn are two seperate things (good), subversion/subclipse.mylyn is one big one (bad). [incorrect - there are actually two for svn too]
> - eclipsecs includes experiemental com.github.sevntucheckstyle feature - do we need/want that ?
> - common.mylyn.feature - can that be split into bugzilla and jira one ? [no - bugzilla/jira setup currently are connected]
> - jrebel requires server_core feature but why aren't they just listed in there and remove the need for seperate core/server feature ? [cant be done without license problem]
> - Maven connectors seem to be too fine-grained, why do we have m2e,m2e-jdt and m2e-wtp as separate connectors ? [can wait]
--
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
More information about the jbosstools-issues
mailing list