[jira] [Created] (NETBEANS-5629) Gradle project Lookups ordering not defined well

["Svatopluk Dedic (Jira)" <ji...@apache.org>]

Svatopluk Dedic created NETBEANS-5629:
-----------------------------------------

             Summary: Gradle project Lookups ordering not defined well
                 Key: NETBEANS-5629
                 URL: https://issues.apache.org/jira/browse/NETBEANS-5629
             Project: NetBeans
          Issue Type: Bug
            Reporter: Svatopluk Dedic


Individual Plugins can contribute to project Lookup. In my testcase, which uses java/java-base plugins, the Lookups loaded from *Projects/org-netbeans-modules-gradle/*** were loaded in the following order:
{code:java}
[java, <nb-general>, root, java-base, base]
{code}
When Groovy was also present, the order was
{code:java}
[java, groovy, <nb-general>, root, groovy-base, java-base, base]
{code}
(note - groovy after java, groovy-base before java-base). But with scala, the order is:
{code:java}
[java, scala, <nb-general>, root, java-base, scala-base, base]
{code}
(note - scala-base AFTER java-base).

When opening a project with 
{code:java}
apply plugin: 'groovy'
{code}
the order is yet different:
{code:java}
[groovy, java, <nb-general>, root, groovy-base, java-base, base]{code}
The order is unreliable and I guess under some circumstances even the <nb-general>, xxx-base and xxx could be reordered as plugin names go through series of hashmaps.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists