[jbosstools-issues] [JBoss JIRA] (JBIDE-12469) Creation of org.jboss.tools.common.core component and associated feature

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713433#comment-12713433 ] 

Nick Boldt commented on JBIDE-12469:
------------------------------------

Conflicting opinions arise here about the best approach:

a) leaving empty stubs is ugly but (as in WTP) is motivated by the idea that consumers will move with glacial speed when you mark something deprecated. So, to make the pain less (or at least delayed) you give them a couple years to migrate before deleting the deprecated stuff. Seems reasonable given enterprise customers.

b) OTOH, we're doing a 4.0 release, on a new Eclipse base (4.x instead of 3.x) so maybe this is the BEST time to break people and force them to adapt and adopt the new conventions.

EITHER WAY, +1 for refactoring. 
                
> Creation of org.jboss.tools.common.core component and associated feature
> ------------------------------------------------------------------------
>
>                 Key: JBIDE-12469
>                 URL: https://issues.jboss.org/browse/JBIDE-12469
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: common/jst/core
>    Affects Versions: 4.0.0.M1
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>             Fix For: 4.0.0.M1
>
>         Attachments: JBIDE-12469.scope2.txt
>
>
> As part of the refactor of the "common" component, this jira will track the addition of a new plugin. Some complain that common already has too many plugins, so this new plugin's creation will follow a careful process to ensure the new plugin has a purpose, is not repetitive, and helps move the component into a cleaner direction rather than a messier one. 
> The process (in progress) is being formed over at https://community.jboss.org/wiki/DevelopingForJBossTools

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira