[jbosstools-dev] Question on all external users of IJBoss7ManagerService

[Rob Stryker]

Hi all:

We currently have two plugins containing client jars for the various 
wildfly / as7 versions.  One plugin is named 
org.jboss.ide.eclipse.as.management.as71,  the other 
org.jboss.ide.eclipse.as.management.wildfly8

As currently implemented, org.jboss.ide.eclipse.as.management.as71 holds 
client jars that are used with as70, 71, eap6x, etc. 
org.jboss.ide.eclipse.as.management.wildfly8 is used to hold jars for 
all wildflys, or, expectedly, eap7x.

A bug in deploying large projects has led me to investigate whether the 
wildfly 9 jars work for all servers or not. It turns out, they work for 
all except AS 7.0.x.  With as71, though, a higher timeout is needed.

My PR to fix the issue creates a 71x service inside the 
org.jboss.ide.eclipse.as.management.wildfly8 to live along side the wf8 
service. Unfortunately, it seems strange now to have a plugin named 
org.jboss.ide.eclipse.as.management.as71 which holds a service with 
version=7.1.0.Beta1  which only works for AS 7.0.x  =P   Seems a bit 
odd, no?

So I was planning on harmonizing these constants, plugin names, 
versions, etc, in beta2, and was wondering if anyone else is using these 
service names and constants directly, and how they're being used?   I 
expect to change them and clean them up, and need to know if this will 
break anyone.

- Rob Stryker