Re: [jbosstools-dev] Removal of plugin, consequences?

BTW as-bootstrap is broken: [ERROR] Child module /home/igels/Projects/jbt-3.3/trunk/as/plugins/org.jboss.ide.eclipse.as.management.as7/pom.xml of /home/igels/Projects/jbt-3.3/trunk/as/plugins/pom.xml does not exist @ at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:339) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:632) at org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:581) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:233) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) [ERROR] [ERROR] The project org.jboss.tools.as:plugins:2.3.0-SNAPSHOT (/home/igels/Projects/jbt-3.3/trunk/as/plugins/pom.xml) has 1 error [ERROR] Child module /home/igels/Projects/jbt-3.3/trunk/as/plugins/org.jboss.ide.eclipse.as.management.as7/pom.xml of /home/igels/Projects/jbt-3.3/trunk/as/plugins/pom.xml does not exist On 01/08/2012 10:37 PM, 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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev