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

[Radim Hopp (JIRA)]

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

Radim Hopp commented on JBIDE-21771:
------------------------------------

Yes, the project is usable either way... I've tried to compare two projects, one imported as "Java" one as "Java, JDT"... and they are identical (except for name).

> 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
>            Assignee: Mickael Istria
>         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)