[
https://issues.jboss.org/browse/JBIDE-12469?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12469:
----------------------------------------
@Rob, your arguments are persuasive ;)
I'm in favor of the incremental approach: first split, then rename.
Let's split common in common.core and common.ui, and keep common as a bundle
re-exporting common.core and common.ui. So there will be nothing to change for 1st
increment.
When everything is fine with it, we can perform renaming of packages and removed of
common, and force consumers to use common.core and common.ui instead.
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