[jbosstools-issues] [JBoss JIRA] (JBIDE-17990) Organize imports does not work for Maven dependencies
Max Rydahl Andersen (JIRA)
issues at jboss.org
Tue Aug 26 09:13:00 EDT 2014
[ https://issues.jboss.org/browse/JBIDE-17990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995786#comment-12995786 ]
Max Rydahl Andersen commented on JBIDE-17990:
---------------------------------------------
[~hwellmann] [~hwellmann.de] can you provide more info ?
i.e. do you have an error log where we can see what is failing ?
Any exceptions ?
And can you say if running eclipse with -clean fixes this or at least some of it ?
And what is "some technical identifier" exactly ?
All this would be helpful for us to diagnose the issue.
> 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.3.1#6329)
More information about the jbosstools-issues
mailing list