[jbosstools-issues] [JBoss JIRA] (JBIDE-21771) Simplest java project is imported sometimes as JDT, sometimes not.

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-21771:
----------------------------------------

Just to sort out the priority, is the project usable in workspace in any case or does the difference of behavior have an impact on usabillity?

> Simplest java project is imported sometimes as JDT, sometimes not.
> ------------------------------------------------------------------
>
>                 Key: JBIDE-21771
>                 URL: https://issues.jboss.org/browse/JBIDE-21771
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: easymport
>    Affects Versions: 4.3.1.CR1
>            Reporter: Radim Hopp
>         Attachments: PlainJavaProject
>
>
> Importing simplest java project (in attachment) gets sometimes imported as "Java, JDT" and sometimes only as "Java". I am not able to provide exact steps to reproduce, as it seems to do that randomly.
> Looking at http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles/org.eclipse.e4.ui.importer.java/plugin.xml, project should be detected as JDT, in case ".classpath" is found in the project. Couldn't be the issue the order of executing configurators? Like when Java configurator is called first, it creates .classpath and then JDT configurator is called and it sees the .classpath file. When the order is opposite, JDT is not configured, because .classpath is not there yet?



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)