[jbosstools-issues] [JBoss JIRA] (JBIDE-17990) Organize imports does not work for Maven dependencies

[Snjezana Peco (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-17990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989611#comment-12989611 ] 

Snjezana Peco commented on JBIDE-17990:
---------------------------------------

I can't reproduce the issue.
I have tried JBT master, JBDS 8.0.0.Beta3 and JBDS 8.0.0.Beta3 updated from Beta2

I have also encountered different issues after updating JBT or some other plugins on Luna.
There is a bug in Luna causing some plugins can't be solved after updating. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=430458. 
A workaround is to start JBT/Eclipse with the -clean option.
Do you have any other plugins except JBT?

> 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)