[
https://issues.jboss.org/browse/JBIDE-17990?page=com.atlassian.jira.plugi...
]
Harald Wellmann commented on JBIDE-17990:
-----------------------------------------
I tried all sorts of things... I can't reproduce the issue with a clean install
(Virgin Eclipse Luna + 4.2.0.Beta3 Abridged JBoss Tools).
I suspect something went wrong during the update from the update site, and things went
from bad to worse, as there was no way to cleanly rollback this update.
Before the update, I had
* Luna Enterprise Edition
* A subset of Beta2 Abridged Tools
* Some additional m2e extensions.
After the broken update, I noticed that all library folders previously named {{Maven
Dependencies}} were now called something like {{Persistent container \[some technical
identifer\]}} which looked rather suspicious. I don't remember the exact wording -
maybe this is a clue to which plugin was broken during the update.
I tried to revert to the previous configuration from Installation History, which gave me
an error message about 4.2.0.Beta2 no longer available from any update site. Seeing that
Eclipse never really deletes any updated plugins, I don't see why Eclipse is unable to
revert to a known configuration when all required plugins are still on my local disk.
To get out of this mess, I had to revert to the configuration I had before the original
Beta2 install (thus reverting both Beta2 and Beta3 and some other stuff I had installed in
the meantime).
Organize imports does not work for Maven dependencies
-----------------------------------------------------
Key: JBIDE-17990
URL:
https://issues.jboss.org/browse/JBIDE-17990
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.2.0.Beta3
Environment: Oracle JDK 1.8.0_05, Eclipse Luna
Reporter: Harald Wellmann
Assignee: Snjezana Peco
Fix For: 4.2.0.CR1
After upgrading from 4.2.0.Beta2 to Beta3 to test the fix for JBIDE-17724, Organize
Imports is broken in my workspace. More precisely, I'm referring to the capability of
finding the package a class lives in and generating the {{import}} directive with the
FQCN.
The corresponding Quick Fix is also broken.
It only works for class names from sources in the workspace, it no longer works for class
names from a Maven dependency in the local repository.
This is even worse than JBIDE-17724, I'll have to revert to Beta2.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)