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

[ https://issues.jboss.org/browse/JBIDE-12469?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-12469: ------------------------------------- It will add ambiguity for sure. The problem is that splitting the bundle and renaming the package will break basically every single part of the jboss tools build, until every single component updates all their imports. This is obviously something that simply cannot be done. The only other option I can imagine would be as follows: 1) Create the new o.j.t.common.core plugin 2) Copy all relevent classes into o.j.t.common.core with o.j.t.common.core package names 3) do not delete the o.j.t.common varients, but mark them as @deprecated and make them extend the new plugin (deleting the body of the class) I am fairly certain Max (and others) will not agree to this strategy, as it leaves about 40-45 class "stubs" that are deprecated and who's sole purpose is to sit there with an @Deprecated marker. Webtools typically does something like this though. They would sooner introduce a new class in a new package, make the old class extend the new one, mark the old one as @Deprecated, and, perhaps a year later, remove the old stub class. But from my experiences with the project, many people will see a big problem with this idea. Many members of the team do not like having empty stub classes with identical names sit around useless, cluttering up their views and complicating their ctrl+shift+t open-type hotkeys. -- 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