[jbosstools-dev] Removal of plugin, consequences?

[Nick Boldt]

I'm pretty sure that the updated feature, which no longer includes the 
old deprecated plugin, when updated will remove the orphaned old version.

But of course you can build locally and test locally by installing the 
new feature from your locally generated update site into an Eclipse 
instance which includes the old feature (and the deprecated plugin).

In other words -- steps to reproduce/verify:

1. install eclipse 371 JEE (or newer)
2. install JBT M5 including the deprecated plugin (wrapped by its 
containing feature)
3. build new feature (which excludes the deprecated plugin)
4. install JBT nightly local build from ~/.../as/site/target/site/ 
folder to see what happens when you update.
5. Verify if the org.jboss.now.deprecated_0.0.0.jar disappear from 
~/.../eclipse371/eclipse/plugins/ folder?


On 01/09/2012 01:37 AM, Rob Stryker wrote:
> 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
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com