Anyway, I don't know how fixed the API is at the moment but it would be a
lot better for me, if I could provide the jar files in a separate query
rather than in BinaryForSourceQueryImplementation. Or would that require
too much change?
2017-07-31 20:01 GMT+02:00 Attila Kelemen
Thanks for the answer. My code-name-base is "org.netbeans.gradle.project".
- What exactly do you mean by "multi module compilation"? That a single
project produces multiple modules? Because if that is the case, I believe
that will not be possible - at least, given what I saw - but I wouldn't be
Hi Kelemen,
there are several things to update in the project.
It’s preferable to look as J2SEProject + java.api.common, not at Maven as Maven
tries to follow the J2SEProject changes and is not complete.
First and important question is if the Gradle will support multi module
compilation. If not
Hi,
I want to update my Gradle plugin to support Java 9. However, I'm unsure
what to do because the behaviour of APIs I looked at are unspecified. In
particular, I saw that the Maven integration used
`ClassPathSupportFactory.createModuleInfoBasedPath` (which is not a public
API, so I had to hack
