Are you on 11.3? Because with that the project is recognized, I can open
it, it downloads a ton of external library but generally works, even sub
projects can be opened. The only thing does not work is recognizing the
Kotlin sourcesets, though that support could be in 12.0
On 2/28/20 10:05 PM, Enrico Olivelli wrote:
Il Ven 28 Feb 2020, 22:43 Laszlo Kishalmi <laszlo.kisha...@gmail.com> ha
scritto:
NetBeans Gradle Plugin recognizes projects with Kotlin DSL (from 11.3).
I am trying to open Apache Calcite but NB doesn't recognize the folder as a
project.
https://github.com/apache/calcite
I was going to try IntelliJ but your news is sooo cool, I really would like
to use NB!
Can you please check?
Enrico
We have some Kotlin support via TextMate lexer, so some syntax
highlighting is there as well.
On 2/27/20 11:09 PM, Mario Schroeder wrote:
Hi Lazlo,
those are great news. Thanks for sharing.
I also hope that the Kotlin support is taking up speed than we could even
support the Gradle Kotlin DSL.
Laszlo Kishalmi <laszlo.kisha...@gmail.com> schrieb am Fr., 28. Feb.
2020,
02:23:
Dear all,
I just would like to share the progress of my secret project: build
NetBeans with Gradle
I'm still not sure how far I would like to go with this experiment, but
if nothing else it could be a good test data for the Gradle Support.
I had the following milestones in my mind:
M0: Done: Get the project dependencies straight, without having circular
dependencies: Right now it has 813 sub-projects in the known clusters
M1: Done: Get the modules in the Platform cluster (and the harness
cluster) compileable.
M2: TBD: Make the unit tests pass for the Platform Cluster.
M3: TBD: Make the output of the Platform cluster actually runable.
How it works:
I have a specific NetBeans Gradle Plugin which reads the
nbproject/clusters.properties and each module nbproject/project.xml file
to get the dependency configuration. other configuration items are read
from the nbproject.properties file. In theory we do not have to do any
changes for an ordinary module it shall work out of the box without even
having a build.gradle file. There are however some special cases where
build.gradle file is required. Unfortunately there are some dependency
tangles between the modules causing circular dependency in Gradle. In
these cases I had to split up the modules between test and source
projects.
If anyone would like to have a look:
please clone the gradle2 branch of my fork:
https://github.com/lkishalmi/netbeans
The Gradle build right now needs the help to fetch the external
dependencies: ant download-all-extbins
But after that one:
./gradlew buildPlatformCluster -x check
shall work. (It currently requires JDK 11 or up)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
