[jbosstools-dev] Removal of plugin, consequences?

Rob Stryker rstryker at redhat.com
Mon Jan 9 01:37:08 EST 2012


Hi All:

   As per JBIDE-10598,  I removed the as.management.as7 plugin, since it 
had been effectively replaced with as71.  I also, as per JBIDE-10344, 
moved the interfaces for as7 management into their own plugin called 
as.management.core.

The only issue I can find so far is that any installation that still has 
the old deprecated and removed plugin as.management.as7 in the plugins 
folder will experience errors, tons of exceptions, during startup.  
These errors are because the previous versions of jbtools will have the 
as.management.as7 plugin, and it will still be referencing non-existent 
interfaces that previously lived in as.core but now live in 
as.management.core.

Does anyone know for sure if performing an update against an update site 
will properly remove deprecated plugins which have been removed from 
features? Would it be better for me to re-instate as.management.as7 as 
am EMPTY plugin, put it back into the feature, and thus any update 
against an update site will receive an updated empty plugin, which can 
be removed later?

If an update will not remove deprecated plugins which are no longer part 
of features, it seems that putting a stub plugin back into place is the 
only way to solve this issue.

Any advice?

- Rob


More information about the jbosstools-dev mailing list