[jbosstools-issues] [JBoss JIRA] (JBIDE-17990) Organize imports does not work for Maven dependencies
Max Rydahl Andersen (JIRA)
issues at jboss.org
Thu Jul 31 15:00:31 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-17990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989655#comment-12989655 ]
Max Rydahl Andersen commented on JBIDE-17990:
---------------------------------------------
[~hwellmann] this statement has not been true for the last 3-4 years:
{quote}Seeing that Eclipse never really deletes any updated plugins{quote}
Eclipse does actually these days "garbage collect" plugins that is not used by the latest updates.
Just a FYI
> 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, upstream
> 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)
More information about the jbosstools-issues
mailing list