[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3285: -------------------------------------- There is no clear priorities between frameworks/technologies/languages/buildtools.... Examples: Why would Gradle have priority over Maven, or vice-versa? And if a Maven project doesn't define a JavaScript plugin, does that make that we shouldn't enable JSDT on a given webapp which includes many JavaScript files? If we have Bower and Maven, which one should have priority? Should we also define some "work together" rules? Where would they be defined? Dealing with priorities require every configurator to be aware of all other configurators in order to define priorities/compatibilities... I've thought about it while designing the API, and I came to the conclusion that priorities are a quite complex and weak workaround for things don't work together. It's IMO more scalable to just assume that things have to work together. About giving choice to the user about which configurator to use, this is already what the "legacy" import wizard has done for so many years. The less choice we give to user, the more useful is this tool. -- This message was sent by Atlassian JIRA (v6.3.11#6341)