Svatopluk Dedic created NETBEANS-5628:
-----------------------------------------
Summary: Fallback project support shoudl honour apply (plugin)
directives.
Key: NETBEANS-5628
URL: https://issues.apache.org/jira/browse/NETBEANS-5628
Project: NetBeans
Issue Type: Improvement
Reporter: Svatopluk Dedic
The gradle cannot be executed to process/read the build.gradle until the
project is trusted. But at least basic technology plugins should be recognized
- and the process should be pluggable. Right now, the technologies are
hardcoded to: scala, java, groovy, war.
The *ProjectInfoExtractor* should get an extension to actually *contribute* to
the GradleBaseProject (maybe others, too ?) - e.g. passing some Builder around
to the individual Extractors somehow.
The base implementation should lookup / honour simple cases like
{code:java}
plugins {
id("io.github.gradle-nexus.publish-plugin") version "1.0.0"
}
apply plugin: java{code}
Individual gradle-aware project modules could extend the recognition to e.g.
{code:java}
// code placeholder
application {
mainClass.set("com.example1.Application")
}
micronaut {
...
}
{code}
Of course that would be *just a heuristic*, but could allow individual
implementations to be exposed early, so the query system in the IDE is not
broken that much.
Maybe a contribution to *plugins* could be sufficient as a start, but the
interface should support extensions for the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
