You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Laszlo Kishalmi <la...@gmail.com> on 2018/12/29 19:57:14 UTC
Gradle Support for Apache NetBeans
Dear all,
I would like to donate my Gradle works to Apache NetBeans.
Right now the code is here:
https://github.com/lkishalmi/incubator-netbeans/tree/gradle-support
I just recently rebased it on master, so there is no conflicts. If I'd
create a PR from it that would mean 317 new files and ~35k line of code.
The current state of the plugin:
* It Opens Gradle Projects resource efficiently
* It is based on the ideas found in our Maven Plugin
* It supports JavaSE and Groovy development
* Unit Testing
* Code Coverage
* JPA projects
* Spring (the little support we have for that)
* Navigator for project task
* Custom Task execution
* Output processing
* Debugging (even single methods)
* Creating new projects
The shady side:
* The Gradle <-> NetBeans project discovery and communication.
Based on simple property serialization. Ugly Groovy code, well the
deserialization Java code isn't that nice as well
* Limited number of unittest
* Being a sole developer there could be glitches here and there as of
lack of wider testing.
* Gradle is required to build the NetBeans <-> Gradle tooling
This adds a binary
groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
to the source distribution package, though this file is not
distributed. So Apace might agree with that.
Introduced External Dependencies:
* Gradle Tooling API (Apache Licensed)
o slf4j (Apache Licensed)
* JaCoCo Core Library (EPL 1.0)
The whole JaCoCo project uses other libraries distributed under
different licenses, I need to make sure that the core is EPL 1.0 only
Areas to Improve:
* There is no support for Ergonomy
* Module versions might be incorrectly specified, I did the best I could
* Add Groovy project support (could be trivial)
* Improve Gradle <-> JDK incompatibility check.
* Profiling
* Compile on Save (that's an icy territory)
* Improve project Settings
* Whatever you think...
Future Works:
* I also have a JavaEE support module started, I can donate somewhat
later to the enterprise cluster.
Re: Maven 1st was: Gradle Support for Apache NetBeans
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Are those most in favor of ‘Maven 1st’ also going to pick up the task of
updating all the documentation to retlect this change?
Without that commitment, including an impact analysis on our documentation
and a timeline for updating it, I will veto this PR.
Gj
On Friday, January 4, 2019, arsi <ar...@chello.sk> wrote:
> Hi,
>
> Gradle has weak Tooling API and I'm afraid that getting Gradle support
> level to current NB Maven level will be very hard.
>
> Gradle is required, but Maven must be left as a flagship.
>
> Arsi
>
> ------------------------------------------------------------------------
> *From:* Sven Reimers <sv...@gmail.com>
> *Sent:* Friday, January 04, 2019 1:16PM
> *To:* Dev <de...@netbeans.incubator.apache.org>
> *Cc:* Laszlo Kishalmi <la...@gmail.com>
> *Subject:* Re: Maven 1st was: Gradle Support for Apache NetBeans
>
> Hi,
>>
>> is Maven first more a subtle nudge to say do not prefer and are build
>> system?
>>
>> I think we should offer Gradle and Maven as equal alternatives..
>>
>> So it seems it all comes down how to build project categories, by build
>> system, by impl. language or maybe both?
>>
>> I think we should have an agreed solution before merging the PR...
>>
>> -Sven
>>
>> Am Fr., 4. Jan. 2019, 07:58 hat Jaroslav Tulach <
>> jaroslav.tulach@gmail.com>
>> geschrieben:
>>
>> Dne sobota 29. prosince 2018 20:57:14 CET, Laszlo Kishalmi napsal(a):
>>>
>>>> I would like to donate my Gradle works to Apache NetBeans.
>>>>
>>> Having Gradle support is important. Thanks for working on that.
>>>
>>> However I'd like to also know how it will work with the proposed "Maven
>>> first"
>>> approach and Toni's realization of it
>>> https://github.com/apache/incubator-netbeans/pull/1038 ?
>>>
>>> -jt
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>>
>>> For further information about the NetBeans mailing lists, visit:
>>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>
>>>
>>>
>>>
>>>
>
>
>
Re: Maven 1st was: Gradle Support for Apache NetBeans
Posted by arsi <ar...@chello.sk>.
Hi,
Gradle has weak Tooling API and I'm afraid that getting Gradle support
level to current NB Maven level will be very hard.
Gradle is required, but Maven must be left as a flagship.
Arsi
------------------------------------------------------------------------
*From:* Sven Reimers <sv...@gmail.com>
*Sent:* Friday, January 04, 2019 1:16PM
*To:* Dev <de...@netbeans.incubator.apache.org>
*Cc:* Laszlo Kishalmi <la...@gmail.com>
*Subject:* Re: Maven 1st was: Gradle Support for Apache NetBeans
> Hi,
>
> is Maven first more a subtle nudge to say do not prefer and are build
> system?
>
> I think we should offer Gradle and Maven as equal alternatives..
>
> So it seems it all comes down how to build project categories, by build
> system, by impl. language or maybe both?
>
> I think we should have an agreed solution before merging the PR...
>
> -Sven
>
> Am Fr., 4. Jan. 2019, 07:58 hat Jaroslav Tulach <ja...@gmail.com>
> geschrieben:
>
>> Dne sobota 29. prosince 2018 20:57:14 CET, Laszlo Kishalmi napsal(a):
>>> I would like to donate my Gradle works to Apache NetBeans.
>> Having Gradle support is important. Thanks for working on that.
>>
>> However I'd like to also know how it will work with the proposed "Maven
>> first"
>> approach and Toni's realization of it
>> https://github.com/apache/incubator-netbeans/pull/1038 ?
>>
>> -jt
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
Re: Maven 1st was: Gradle Support for Apache NetBeans
Posted by Sven Reimers <sv...@gmail.com>.
Hi,
is Maven first more a subtle nudge to say do not prefer and are build
system?
I think we should offer Gradle and Maven as equal alternatives..
So it seems it all comes down how to build project categories, by build
system, by impl. language or maybe both?
I think we should have an agreed solution before merging the PR...
-Sven
Am Fr., 4. Jan. 2019, 07:58 hat Jaroslav Tulach <ja...@gmail.com>
geschrieben:
> Dne sobota 29. prosince 2018 20:57:14 CET, Laszlo Kishalmi napsal(a):
> > I would like to donate my Gradle works to Apache NetBeans.
>
> Having Gradle support is important. Thanks for working on that.
>
> However I'd like to also know how it will work with the proposed "Maven
> first"
> approach and Toni's realization of it
> https://github.com/apache/incubator-netbeans/pull/1038 ?
>
> -jt
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Maven 1st was: Gradle Support for Apache NetBeans
Posted by Jaroslav Tulach <ja...@gmail.com>.
Dne sobota 29. prosince 2018 20:57:14 CET, Laszlo Kishalmi napsal(a):
> I would like to donate my Gradle works to Apache NetBeans.
Having Gradle support is important. Thanks for working on that.
However I'd like to also know how it will work with the proposed "Maven first"
approach and Toni's realization of it https://github.com/apache/incubator-netbeans/pull/1038 ?
-jt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Gradle Support for Apache NetBeans
Posted by Laszlo Kishalmi <la...@gmail.com>.
On 12/29/18 6:46 PM, Scott Palmer wrote:
> +1 Great to see more support for Gradle.
>
> How does this plugin compare to the existing Gradle plugin? Would it make sense to merge your efforts?
That is a good question. The two plugins have very different coding
styles. IMHO Attila's plugin does the NetBeans <-> Gradle communication
in a nicer way (though the generic idea is the same), mine, if I may say
so, is more seamless fit into the IDE.
>
> I would really like to see support for Gradle-based native C/C++ projects.
I can imagine that we could work out something when the C++ donation
gets released, Probably for NetBeans 12.0 (or whatever that version
number would be).
>
> Scott
>
>
>> On Dec 29, 2018, at 6:02 PM, John McDonnell <mc...@gmail.com> wrote:
>>
>> Very cool, it'll be nice to have Gradle and Maven in NetBeans moving
>> forward.
>>
>> From what I see, new frameworks seem to be coming out supporting Gradle, so
>> being able to have Gradle as a first class citizen along with Maven that
>> would be really great.
>>
>>
>> Regards
>>
>> John
>>
>> On Sat, 29 Dec 2018 at 19:57, Laszlo Kishalmi <la...@gmail.com>
>> wrote:
>>
>>> Dear all,
>>>
>>> I would like to donate my Gradle works to Apache NetBeans.
>>>
>>> Right now the code is here:
>>> https://github.com/lkishalmi/incubator-netbeans/tree/gradle-support
>>>
>>> I just recently rebased it on master, so there is no conflicts. If I'd
>>> create a PR from it that would mean 317 new files and ~35k line of code.
>>>
>>> The current state of the plugin:
>>>
>>> * It Opens Gradle Projects resource efficiently
>>> * It is based on the ideas found in our Maven Plugin
>>> * It supports JavaSE and Groovy development
>>> * Unit Testing
>>> * Code Coverage
>>> * JPA projects
>>> * Spring (the little support we have for that)
>>> * Navigator for project task
>>> * Custom Task execution
>>> * Output processing
>>> * Debugging (even single methods)
>>> * Creating new projects
>>>
>>> The shady side:
>>>
>>> * The Gradle <-> NetBeans project discovery and communication.
>>> Based on simple property serialization. Ugly Groovy code, well the
>>> deserialization Java code isn't that nice as well
>>> * Limited number of unittest
>>> * Being a sole developer there could be glitches here and there as of
>>> lack of wider testing.
>>> * Gradle is required to build the NetBeans <-> Gradle tooling
>>> This adds a binary
>>> groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
>>> to the source distribution package, though this file is not
>>> distributed. So Apace might agree with that.
>>>
>>> Introduced External Dependencies:
>>>
>>> * Gradle Tooling API (Apache Licensed)
>>> o slf4j (Apache Licensed)
>>> * JaCoCo Core Library (EPL 1.0)
>>> The whole JaCoCo project uses other libraries distributed under
>>> different licenses, I need to make sure that the core is EPL 1.0 only
>>>
>>> Areas to Improve:
>>>
>>> * There is no support for Ergonomy
>>> * Module versions might be incorrectly specified, I did the best I could
>>> * Add Groovy project support (could be trivial)
>>> * Improve Gradle <-> JDK incompatibility check.
>>> * Profiling
>>> * Compile on Save (that's an icy territory)
>>> * Improve project Settings
>>> * Whatever you think...
>>>
>>> Future Works:
>>>
>>> * I also have a JavaEE support module started, I can donate somewhat
>>> later to the enterprise cluster.
>>>
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.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-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Gradle Support for Apache NetBeans
Posted by Laszlo Kishalmi <la...@gmail.com>.
Thanks for catching the external libraries issue. I've fixed them.
Issues/feedback are always welcome!
On 12/30/18 7:01 AM, John McDonnell wrote:
> Hi Laszlo,
>
> Hope you don't mind, but I have this building now(in progress), but I came
> across 2 issues, the one noted previously and another one related to the
> hash's of the slf4j dependencies.
>
> I have created 2 issues in your repository for them, to help track them, if
> thats okay with you?
>
> I have a 2 very small sample gradle projects I might have a look at, and
> any other issues I can raise there as well if you'd like?
>
>
> Regards
>
> John
>
> On Sun, 30 Dec 2018 at 10:44, Geertjan Wielenga
> <ge...@googlemail.com.invalid> wrote:
>
>> This is really awesome and the sooner this is integrated (I suggest in the
>> groovy cluster) the better. I've used this plugin before via Laszlo's repo
>> and it worked beautifully. Ideally this integration be done in
>> co-ordination with the developer/s of the other Gradle plugin so that we're
>> all on the same page and even more ideally working together on the same
>> sources.
>>
>> Gj
>>
>> On Sun, Dec 30, 2018 at 9:35 AM Matthias Bläsing <
>> mblaesing@doppel-helix.eu>
>> wrote:
>>
>>> Hi,
>>>
>>> Am Samstag, den 29.12.2018, 21:36 -0800 schrieb Laszlo Kishalmi:
>>>> Probably we shall switch to jcenter as default to turn to.
>>> we should discuss downloading dependencies again. But switching to
>>> JCenter won't help:
>>>
>>> https://jcenter.bintray.com/org/gradle/gradle-tooling-api/
>>>
>>> does not list version 4.10.2. It seems to be only present in their own
>>> repository:
>>>
>>> https://mvnrepository.com/artifact/org.gradle/gradle-tooling-api/4.10.2
>>>
>>> Looks as if the gradle developers don't publish their artifacts...
>>>
>>> Greetings
>>>
>>> Matthias
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>> For additional commands, e-mail: dev-help@netbeans.incubator.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-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Gradle Support for Apache NetBeans
Posted by John McDonnell <mc...@gmail.com>.
Hi Laszlo,
Hope you don't mind, but I have this building now(in progress), but I came
across 2 issues, the one noted previously and another one related to the
hash's of the slf4j dependencies.
I have created 2 issues in your repository for them, to help track them, if
thats okay with you?
I have a 2 very small sample gradle projects I might have a look at, and
any other issues I can raise there as well if you'd like?
Regards
John
On Sun, 30 Dec 2018 at 10:44, Geertjan Wielenga
<ge...@googlemail.com.invalid> wrote:
> This is really awesome and the sooner this is integrated (I suggest in the
> groovy cluster) the better. I've used this plugin before via Laszlo's repo
> and it worked beautifully. Ideally this integration be done in
> co-ordination with the developer/s of the other Gradle plugin so that we're
> all on the same page and even more ideally working together on the same
> sources.
>
> Gj
>
> On Sun, Dec 30, 2018 at 9:35 AM Matthias Bläsing <
> mblaesing@doppel-helix.eu>
> wrote:
>
> > Hi,
> >
> > Am Samstag, den 29.12.2018, 21:36 -0800 schrieb Laszlo Kishalmi:
> > > Probably we shall switch to jcenter as default to turn to.
> >
> > we should discuss downloading dependencies again. But switching to
> > JCenter won't help:
> >
> > https://jcenter.bintray.com/org/gradle/gradle-tooling-api/
> >
> > does not list version 4.10.2. It seems to be only present in their own
> > repository:
> >
> > https://mvnrepository.com/artifact/org.gradle/gradle-tooling-api/4.10.2
> >
> > Looks as if the gradle developers don't publish their artifacts...
> >
> > Greetings
> >
> > Matthias
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
Re: Gradle Support for Apache NetBeans
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
This is really awesome and the sooner this is integrated (I suggest in the
groovy cluster) the better. I've used this plugin before via Laszlo's repo
and it worked beautifully. Ideally this integration be done in
co-ordination with the developer/s of the other Gradle plugin so that we're
all on the same page and even more ideally working together on the same
sources.
Gj
On Sun, Dec 30, 2018 at 9:35 AM Matthias Bläsing <mb...@doppel-helix.eu>
wrote:
> Hi,
>
> Am Samstag, den 29.12.2018, 21:36 -0800 schrieb Laszlo Kishalmi:
> > Probably we shall switch to jcenter as default to turn to.
>
> we should discuss downloading dependencies again. But switching to
> JCenter won't help:
>
> https://jcenter.bintray.com/org/gradle/gradle-tooling-api/
>
> does not list version 4.10.2. It seems to be only present in their own
> repository:
>
> https://mvnrepository.com/artifact/org.gradle/gradle-tooling-api/4.10.2
>
> Looks as if the gradle developers don't publish their artifacts...
>
> Greetings
>
> Matthias
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Gradle Support for Apache NetBeans
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
Hi,
Am Samstag, den 29.12.2018, 21:36 -0800 schrieb Laszlo Kishalmi:
> Probably we shall switch to jcenter as default to turn to.
we should discuss downloading dependencies again. But switching to
JCenter won't help:
https://jcenter.bintray.com/org/gradle/gradle-tooling-api/
does not list version 4.10.2. It seems to be only present in their own
repository:
https://mvnrepository.com/artifact/org.gradle/gradle-tooling-api/4.10.2
Looks as if the gradle developers don't publish their artifacts...
Greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Gradle Support for Apache NetBeans
Posted by Laszlo Kishalmi <la...@gmail.com>.
Try with: ant -q -Dbinary.server=https://jcenter.bintray.com/
It seems maven central (our last resort to turn to when a binary is
missing) does not have the gradle tooling files. As I had it in my local
cache it got resolved from there.
Probably we shall switch to jcenter as default to turn to.
On 12/29/18 8:19 PM, John McDonnell wrote:
> Switched to your gradle-support branch but wasn't able to build:
>
> BUILD FAILED
> /Users/john/codebase/incubator-netbeans/nbbuild/build.xml:125: Could not
> download
> 70A74F970B22AC1226F6A2983E38A77FA90E3BE9-gradle-tooling-api-4.10.2.jar from
> http://netbeans.osuosl.org/binaries/: java.io.IOException: Could not
> download
> 70A74F970B22AC1226F6A2983E38A77FA90E3BE9-gradle-tooling-api-4.10.2.jar to
> /Users/john/.hgexternalcache/70A74F970B22AC1226F6A2983E38A77FA90E3BE9-gradle-tooling-api-4.10.2.jar:
> java.io.IOException: Skipping download from
> http://central.maven.org/maven2/org/gradle/gradle-tooling-api/4.10.2/gradle-tooling-api-4.10.2.jar
> due to response code 404
> at
> org.netbeans.nbbuild.extlibs.DownloadBinaries.doDownload(DownloadBinaries.java:249)
> at
> org.netbeans.nbbuild.extlibs.DownloadBinaries.fillInFile(DownloadBinaries.java:190)
> at
> org.netbeans.nbbuild.extlibs.DownloadBinaries.execute(DownloadBinaries.java:154)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
> at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
> at org.apache.tools.ant.Task.perform(Task.java:350)
> at org.apache.tools.ant.Target.execute(Target.java:449)
> at org.apache.tools.ant.Target.performTasks(Target.java:470)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1388)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1361)
> at
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
> at org.apache.tools.ant.Main.runBuild(Main.java:834)
> at org.apache.tools.ant.Main.startAnt(Main.java:223)
> at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
> Caused by: java.io.IOException: Skipping download from
> http://central.maven.org/maven2/org/gradle/gradle-tooling-api/4.10.2/gradle-tooling-api-4.10.2.jar
> due to response code 404
> at
> org.netbeans.nbbuild.extlibs.DownloadBinaries.downloadFromServer(DownloadBinaries.java:275)
> at
> org.netbeans.nbbuild.extlibs.DownloadBinaries.mavenFile(DownloadBinaries.java:177)
> at
> org.netbeans.nbbuild.extlibs.DownloadBinaries.lambda$execute$0(DownloadBinaries.java:154)
> at
> org.netbeans.nbbuild.extlibs.DownloadBinaries.doDownload(DownloadBinaries.java:226)
> ... 18 more
>
> Is there a step I'm missing?
>
>
> John
>
>
> On Sun, 30 Dec 2018 at 02:46, Scott Palmer <sw...@gmail.com> wrote:
>
>> +1 Great to see more support for Gradle.
>>
>> How does this plugin compare to the existing Gradle plugin? Would it make
>> sense to merge your efforts?
>>
>> I would really like to see support for Gradle-based native C/C++ projects.
>>
>> Scott
>>
>>
>>> On Dec 29, 2018, at 6:02 PM, John McDonnell <mc...@gmail.com>
>> wrote:
>>> Very cool, it'll be nice to have Gradle and Maven in NetBeans moving
>>> forward.
>>>
>>> From what I see, new frameworks seem to be coming out supporting Gradle,
>> so
>>> being able to have Gradle as a first class citizen along with Maven that
>>> would be really great.
>>>
>>>
>>> Regards
>>>
>>> John
>>>
>>> On Sat, 29 Dec 2018 at 19:57, Laszlo Kishalmi <laszlo.kishalmi@gmail.com
>>>
>>> wrote:
>>>
>>>> Dear all,
>>>>
>>>> I would like to donate my Gradle works to Apache NetBeans.
>>>>
>>>> Right now the code is here:
>>>> https://github.com/lkishalmi/incubator-netbeans/tree/gradle-support
>>>>
>>>> I just recently rebased it on master, so there is no conflicts. If I'd
>>>> create a PR from it that would mean 317 new files and ~35k line of code.
>>>>
>>>> The current state of the plugin:
>>>>
>>>> * It Opens Gradle Projects resource efficiently
>>>> * It is based on the ideas found in our Maven Plugin
>>>> * It supports JavaSE and Groovy development
>>>> * Unit Testing
>>>> * Code Coverage
>>>> * JPA projects
>>>> * Spring (the little support we have for that)
>>>> * Navigator for project task
>>>> * Custom Task execution
>>>> * Output processing
>>>> * Debugging (even single methods)
>>>> * Creating new projects
>>>>
>>>> The shady side:
>>>>
>>>> * The Gradle <-> NetBeans project discovery and communication.
>>>> Based on simple property serialization. Ugly Groovy code, well the
>>>> deserialization Java code isn't that nice as well
>>>> * Limited number of unittest
>>>> * Being a sole developer there could be glitches here and there as of
>>>> lack of wider testing.
>>>> * Gradle is required to build the NetBeans <-> Gradle tooling
>>>> This adds a binary
>>>>
>> groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
>>>> to the source distribution package, though this file is not
>>>> distributed. So Apace might agree with that.
>>>>
>>>> Introduced External Dependencies:
>>>>
>>>> * Gradle Tooling API (Apache Licensed)
>>>> o slf4j (Apache Licensed)
>>>> * JaCoCo Core Library (EPL 1.0)
>>>> The whole JaCoCo project uses other libraries distributed under
>>>> different licenses, I need to make sure that the core is EPL 1.0 only
>>>>
>>>> Areas to Improve:
>>>>
>>>> * There is no support for Ergonomy
>>>> * Module versions might be incorrectly specified, I did the best I
>> could
>>>> * Add Groovy project support (could be trivial)
>>>> * Improve Gradle <-> JDK incompatibility check.
>>>> * Profiling
>>>> * Compile on Save (that's an icy territory)
>>>> * Improve project Settings
>>>> * Whatever you think...
>>>>
>>>> Future Works:
>>>>
>>>> * I also have a JavaEE support module started, I can donate somewhat
>>>> later to the enterprise cluster.
>>>>
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.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-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Gradle Support for Apache NetBeans
Posted by John McDonnell <mc...@gmail.com>.
Switched to your gradle-support branch but wasn't able to build:
BUILD FAILED
/Users/john/codebase/incubator-netbeans/nbbuild/build.xml:125: Could not
download
70A74F970B22AC1226F6A2983E38A77FA90E3BE9-gradle-tooling-api-4.10.2.jar from
http://netbeans.osuosl.org/binaries/: java.io.IOException: Could not
download
70A74F970B22AC1226F6A2983E38A77FA90E3BE9-gradle-tooling-api-4.10.2.jar to
/Users/john/.hgexternalcache/70A74F970B22AC1226F6A2983E38A77FA90E3BE9-gradle-tooling-api-4.10.2.jar:
java.io.IOException: Skipping download from
http://central.maven.org/maven2/org/gradle/gradle-tooling-api/4.10.2/gradle-tooling-api-4.10.2.jar
due to response code 404
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.doDownload(DownloadBinaries.java:249)
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.fillInFile(DownloadBinaries.java:190)
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.execute(DownloadBinaries.java:154)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform(Task.java:350)
at org.apache.tools.ant.Target.execute(Target.java:449)
at org.apache.tools.ant.Target.performTasks(Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1388)
at org.apache.tools.ant.Project.executeTarget(Project.java:1361)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.Main.runBuild(Main.java:834)
at org.apache.tools.ant.Main.startAnt(Main.java:223)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
Caused by: java.io.IOException: Skipping download from
http://central.maven.org/maven2/org/gradle/gradle-tooling-api/4.10.2/gradle-tooling-api-4.10.2.jar
due to response code 404
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.downloadFromServer(DownloadBinaries.java:275)
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.mavenFile(DownloadBinaries.java:177)
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.lambda$execute$0(DownloadBinaries.java:154)
at
org.netbeans.nbbuild.extlibs.DownloadBinaries.doDownload(DownloadBinaries.java:226)
... 18 more
Is there a step I'm missing?
John
On Sun, 30 Dec 2018 at 02:46, Scott Palmer <sw...@gmail.com> wrote:
> +1 Great to see more support for Gradle.
>
> How does this plugin compare to the existing Gradle plugin? Would it make
> sense to merge your efforts?
>
> I would really like to see support for Gradle-based native C/C++ projects.
>
> Scott
>
>
> > On Dec 29, 2018, at 6:02 PM, John McDonnell <mc...@gmail.com>
> wrote:
> >
> > Very cool, it'll be nice to have Gradle and Maven in NetBeans moving
> > forward.
> >
> > From what I see, new frameworks seem to be coming out supporting Gradle,
> so
> > being able to have Gradle as a first class citizen along with Maven that
> > would be really great.
> >
> >
> > Regards
> >
> > John
> >
> > On Sat, 29 Dec 2018 at 19:57, Laszlo Kishalmi <laszlo.kishalmi@gmail.com
> >
> > wrote:
> >
> >> Dear all,
> >>
> >> I would like to donate my Gradle works to Apache NetBeans.
> >>
> >> Right now the code is here:
> >> https://github.com/lkishalmi/incubator-netbeans/tree/gradle-support
> >>
> >> I just recently rebased it on master, so there is no conflicts. If I'd
> >> create a PR from it that would mean 317 new files and ~35k line of code.
> >>
> >> The current state of the plugin:
> >>
> >> * It Opens Gradle Projects resource efficiently
> >> * It is based on the ideas found in our Maven Plugin
> >> * It supports JavaSE and Groovy development
> >> * Unit Testing
> >> * Code Coverage
> >> * JPA projects
> >> * Spring (the little support we have for that)
> >> * Navigator for project task
> >> * Custom Task execution
> >> * Output processing
> >> * Debugging (even single methods)
> >> * Creating new projects
> >>
> >> The shady side:
> >>
> >> * The Gradle <-> NetBeans project discovery and communication.
> >> Based on simple property serialization. Ugly Groovy code, well the
> >> deserialization Java code isn't that nice as well
> >> * Limited number of unittest
> >> * Being a sole developer there could be glitches here and there as of
> >> lack of wider testing.
> >> * Gradle is required to build the NetBeans <-> Gradle tooling
> >> This adds a binary
> >>
> groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
> >> to the source distribution package, though this file is not
> >> distributed. So Apace might agree with that.
> >>
> >> Introduced External Dependencies:
> >>
> >> * Gradle Tooling API (Apache Licensed)
> >> o slf4j (Apache Licensed)
> >> * JaCoCo Core Library (EPL 1.0)
> >> The whole JaCoCo project uses other libraries distributed under
> >> different licenses, I need to make sure that the core is EPL 1.0 only
> >>
> >> Areas to Improve:
> >>
> >> * There is no support for Ergonomy
> >> * Module versions might be incorrectly specified, I did the best I
> could
> >> * Add Groovy project support (could be trivial)
> >> * Improve Gradle <-> JDK incompatibility check.
> >> * Profiling
> >> * Compile on Save (that's an icy territory)
> >> * Improve project Settings
> >> * Whatever you think...
> >>
> >> Future Works:
> >>
> >> * I also have a JavaEE support module started, I can donate somewhat
> >> later to the enterprise cluster.
> >>
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Gradle Support for Apache NetBeans
Posted by Scott Palmer <sw...@gmail.com>.
+1 Great to see more support for Gradle.
How does this plugin compare to the existing Gradle plugin? Would it make sense to merge your efforts?
I would really like to see support for Gradle-based native C/C++ projects.
Scott
> On Dec 29, 2018, at 6:02 PM, John McDonnell <mc...@gmail.com> wrote:
>
> Very cool, it'll be nice to have Gradle and Maven in NetBeans moving
> forward.
>
> From what I see, new frameworks seem to be coming out supporting Gradle, so
> being able to have Gradle as a first class citizen along with Maven that
> would be really great.
>
>
> Regards
>
> John
>
> On Sat, 29 Dec 2018 at 19:57, Laszlo Kishalmi <la...@gmail.com>
> wrote:
>
>> Dear all,
>>
>> I would like to donate my Gradle works to Apache NetBeans.
>>
>> Right now the code is here:
>> https://github.com/lkishalmi/incubator-netbeans/tree/gradle-support
>>
>> I just recently rebased it on master, so there is no conflicts. If I'd
>> create a PR from it that would mean 317 new files and ~35k line of code.
>>
>> The current state of the plugin:
>>
>> * It Opens Gradle Projects resource efficiently
>> * It is based on the ideas found in our Maven Plugin
>> * It supports JavaSE and Groovy development
>> * Unit Testing
>> * Code Coverage
>> * JPA projects
>> * Spring (the little support we have for that)
>> * Navigator for project task
>> * Custom Task execution
>> * Output processing
>> * Debugging (even single methods)
>> * Creating new projects
>>
>> The shady side:
>>
>> * The Gradle <-> NetBeans project discovery and communication.
>> Based on simple property serialization. Ugly Groovy code, well the
>> deserialization Java code isn't that nice as well
>> * Limited number of unittest
>> * Being a sole developer there could be glitches here and there as of
>> lack of wider testing.
>> * Gradle is required to build the NetBeans <-> Gradle tooling
>> This adds a binary
>> groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
>> to the source distribution package, though this file is not
>> distributed. So Apace might agree with that.
>>
>> Introduced External Dependencies:
>>
>> * Gradle Tooling API (Apache Licensed)
>> o slf4j (Apache Licensed)
>> * JaCoCo Core Library (EPL 1.0)
>> The whole JaCoCo project uses other libraries distributed under
>> different licenses, I need to make sure that the core is EPL 1.0 only
>>
>> Areas to Improve:
>>
>> * There is no support for Ergonomy
>> * Module versions might be incorrectly specified, I did the best I could
>> * Add Groovy project support (could be trivial)
>> * Improve Gradle <-> JDK incompatibility check.
>> * Profiling
>> * Compile on Save (that's an icy territory)
>> * Improve project Settings
>> * Whatever you think...
>>
>> Future Works:
>>
>> * I also have a JavaEE support module started, I can donate somewhat
>> later to the enterprise cluster.
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Gradle Support for Apache NetBeans
Posted by Josh Juneau <ju...@gmail.com>.
Very nice! Great work Laszlo! Looking forward to having support for Gradle as a first class citizen.
Josh Juneau
http://jj-blogger.blogspot.com
https://www.apress.com/index.php/author/author/view/id/1866
> On Dec 29, 2018, at 5:02 PM, John McDonnell <mc...@gmail.com> wrote:
>
> Very cool, it'll be nice to have Gradle and Maven in NetBeans moving
> forward.
>
> From what I see, new frameworks seem to be coming out supporting Gradle, so
> being able to have Gradle as a first class citizen along with Maven that
> would be really great.
>
>
> Regards
>
> John
>
> On Sat, 29 Dec 2018 at 19:57, Laszlo Kishalmi <la...@gmail.com>
> wrote:
>
>> Dear all,
>>
>> I would like to donate my Gradle works to Apache NetBeans.
>>
>> Right now the code is here:
>> https://github.com/lkishalmi/incubator-netbeans/tree/gradle-support
>>
>> I just recently rebased it on master, so there is no conflicts. If I'd
>> create a PR from it that would mean 317 new files and ~35k line of code.
>>
>> The current state of the plugin:
>>
>> * It Opens Gradle Projects resource efficiently
>> * It is based on the ideas found in our Maven Plugin
>> * It supports JavaSE and Groovy development
>> * Unit Testing
>> * Code Coverage
>> * JPA projects
>> * Spring (the little support we have for that)
>> * Navigator for project task
>> * Custom Task execution
>> * Output processing
>> * Debugging (even single methods)
>> * Creating new projects
>>
>> The shady side:
>>
>> * The Gradle <-> NetBeans project discovery and communication.
>> Based on simple property serialization. Ugly Groovy code, well the
>> deserialization Java code isn't that nice as well
>> * Limited number of unittest
>> * Being a sole developer there could be glitches here and there as of
>> lack of wider testing.
>> * Gradle is required to build the NetBeans <-> Gradle tooling
>> This adds a binary
>> groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
>> to the source distribution package, though this file is not
>> distributed. So Apace might agree with that.
>>
>> Introduced External Dependencies:
>>
>> * Gradle Tooling API (Apache Licensed)
>> o slf4j (Apache Licensed)
>> * JaCoCo Core Library (EPL 1.0)
>> The whole JaCoCo project uses other libraries distributed under
>> different licenses, I need to make sure that the core is EPL 1.0 only
>>
>> Areas to Improve:
>>
>> * There is no support for Ergonomy
>> * Module versions might be incorrectly specified, I did the best I could
>> * Add Groovy project support (could be trivial)
>> * Improve Gradle <-> JDK incompatibility check.
>> * Profiling
>> * Compile on Save (that's an icy territory)
>> * Improve project Settings
>> * Whatever you think...
>>
>> Future Works:
>>
>> * I also have a JavaEE support module started, I can donate somewhat
>> later to the enterprise cluster.
>>
>>
>>
Re: Gradle Support for Apache NetBeans
Posted by John McDonnell <mc...@gmail.com>.
Very cool, it'll be nice to have Gradle and Maven in NetBeans moving
forward.
From what I see, new frameworks seem to be coming out supporting Gradle, so
being able to have Gradle as a first class citizen along with Maven that
would be really great.
Regards
John
On Sat, 29 Dec 2018 at 19:57, Laszlo Kishalmi <la...@gmail.com>
wrote:
> Dear all,
>
> I would like to donate my Gradle works to Apache NetBeans.
>
> Right now the code is here:
> https://github.com/lkishalmi/incubator-netbeans/tree/gradle-support
>
> I just recently rebased it on master, so there is no conflicts. If I'd
> create a PR from it that would mean 317 new files and ~35k line of code.
>
> The current state of the plugin:
>
> * It Opens Gradle Projects resource efficiently
> * It is based on the ideas found in our Maven Plugin
> * It supports JavaSE and Groovy development
> * Unit Testing
> * Code Coverage
> * JPA projects
> * Spring (the little support we have for that)
> * Navigator for project task
> * Custom Task execution
> * Output processing
> * Debugging (even single methods)
> * Creating new projects
>
> The shady side:
>
> * The Gradle <-> NetBeans project discovery and communication.
> Based on simple property serialization. Ugly Groovy code, well the
> deserialization Java code isn't that nice as well
> * Limited number of unittest
> * Being a sole developer there could be glitches here and there as of
> lack of wider testing.
> * Gradle is required to build the NetBeans <-> Gradle tooling
> This adds a binary
> groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
> to the source distribution package, though this file is not
> distributed. So Apace might agree with that.
>
> Introduced External Dependencies:
>
> * Gradle Tooling API (Apache Licensed)
> o slf4j (Apache Licensed)
> * JaCoCo Core Library (EPL 1.0)
> The whole JaCoCo project uses other libraries distributed under
> different licenses, I need to make sure that the core is EPL 1.0 only
>
> Areas to Improve:
>
> * There is no support for Ergonomy
> * Module versions might be incorrectly specified, I did the best I could
> * Add Groovy project support (could be trivial)
> * Improve Gradle <-> JDK incompatibility check.
> * Profiling
> * Compile on Save (that's an icy territory)
> * Improve project Settings
> * Whatever you think...
>
> Future Works:
>
> * I also have a JavaEE support module started, I can donate somewhat
> later to the enterprise cluster.
>
>
>
Re: Gradle Support for Apache NetBeans
Posted by Javier Ortiz <ja...@gmail.com>.
This is the only missing piece for the stuff I use most. Right now this is
the only reason I still have 8.2 around.
On Wed, Jan 2, 2019, 6:54 PM Laszlo Kishalmi <laszlo.kishalmi@gmail.com
wrote:
>
> On 12/30/18 10:22 AM, Jan Lahoda wrote:
> > Hi Laszlo,
> >
> > It will be great to have Gradle support - thanks for that!
> >
> > Regarding the:
> > groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
> >
> > I don't think that can be in the source distro ("compiled code not
> > allowed"), but it shouldn't be too problematic to download that during
> > build as well, right?
> I've checked a few Apache projects how they are solving this issue, then
> as of we have Ant as a wrapper around the Gradle phase, I added some
> tweaks to download the wrapper from Gradle's git repo. So that concern
> has been solved.
> > Thanks for doing this!
> >
> > Jan
> >
> > On Sat, Dec 29, 2018 at 8:57 PM Laszlo Kishalmi <
> laszlo.kishalmi@gmail.com>
> > wrote:
> >
> >> Dear all,
> >>
> >> I would like to donate my Gradle works to Apache NetBeans.
> >>
> >> Right now the code is here:
> >> https://github.com/lkishalmi/incubator-netbeans/tree/gradle-support
> >>
> >> I just recently rebased it on master, so there is no conflicts. If I'd
> >> create a PR from it that would mean 317 new files and ~35k line of code.
> >>
> >> The current state of the plugin:
> >>
> >> * It Opens Gradle Projects resource efficiently
> >> * It is based on the ideas found in our Maven Plugin
> >> * It supports JavaSE and Groovy development
> >> * Unit Testing
> >> * Code Coverage
> >> * JPA projects
> >> * Spring (the little support we have for that)
> >> * Navigator for project task
> >> * Custom Task execution
> >> * Output processing
> >> * Debugging (even single methods)
> >> * Creating new projects
> >>
> >> The shady side:
> >>
> >> * The Gradle <-> NetBeans project discovery and communication.
> >> Based on simple property serialization. Ugly Groovy code, well the
> >> deserialization Java code isn't that nice as well
> >> * Limited number of unittest
> >> * Being a sole developer there could be glitches here and there as of
> >> lack of wider testing.
> >> * Gradle is required to build the NetBeans <-> Gradle tooling
> >> This adds a binary
> >>
> groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
> >> to the source distribution package, though this file is not
> >> distributed. So Apace might agree with that.
> >>
> >> Introduced External Dependencies:
> >>
> >> * Gradle Tooling API (Apache Licensed)
> >> o slf4j (Apache Licensed)
> >> * JaCoCo Core Library (EPL 1.0)
> >> The whole JaCoCo project uses other libraries distributed under
> >> different licenses, I need to make sure that the core is EPL 1.0
> only
> >>
> >> Areas to Improve:
> >>
> >> * There is no support for Ergonomy
> >> * Module versions might be incorrectly specified, I did the best I
> could
> >> * Add Groovy project support (could be trivial)
> >> * Improve Gradle <-> JDK incompatibility check.
> >> * Profiling
> >> * Compile on Save (that's an icy territory)
> >> * Improve project Settings
> >> * Whatever you think...
> >>
> >> Future Works:
> >>
> >> * I also have a JavaEE support module started, I can donate somewhat
> >> later to the enterprise cluster.
> >>
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Gradle Support for Apache NetBeans
Posted by Laszlo Kishalmi <la...@gmail.com>.
On 12/30/18 10:22 AM, Jan Lahoda wrote:
> Hi Laszlo,
>
> It will be great to have Gradle support - thanks for that!
>
> Regarding the:
> groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
>
> I don't think that can be in the source distro ("compiled code not
> allowed"), but it shouldn't be too problematic to download that during
> build as well, right?
I've checked a few Apache projects how they are solving this issue, then
as of we have Ant as a wrapper around the Gradle phase, I added some
tweaks to download the wrapper from Gradle's git repo. So that concern
has been solved.
> Thanks for doing this!
>
> Jan
>
> On Sat, Dec 29, 2018 at 8:57 PM Laszlo Kishalmi <la...@gmail.com>
> wrote:
>
>> Dear all,
>>
>> I would like to donate my Gradle works to Apache NetBeans.
>>
>> Right now the code is here:
>> https://github.com/lkishalmi/incubator-netbeans/tree/gradle-support
>>
>> I just recently rebased it on master, so there is no conflicts. If I'd
>> create a PR from it that would mean 317 new files and ~35k line of code.
>>
>> The current state of the plugin:
>>
>> * It Opens Gradle Projects resource efficiently
>> * It is based on the ideas found in our Maven Plugin
>> * It supports JavaSE and Groovy development
>> * Unit Testing
>> * Code Coverage
>> * JPA projects
>> * Spring (the little support we have for that)
>> * Navigator for project task
>> * Custom Task execution
>> * Output processing
>> * Debugging (even single methods)
>> * Creating new projects
>>
>> The shady side:
>>
>> * The Gradle <-> NetBeans project discovery and communication.
>> Based on simple property serialization. Ugly Groovy code, well the
>> deserialization Java code isn't that nice as well
>> * Limited number of unittest
>> * Being a sole developer there could be glitches here and there as of
>> lack of wider testing.
>> * Gradle is required to build the NetBeans <-> Gradle tooling
>> This adds a binary
>> groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
>> to the source distribution package, though this file is not
>> distributed. So Apace might agree with that.
>>
>> Introduced External Dependencies:
>>
>> * Gradle Tooling API (Apache Licensed)
>> o slf4j (Apache Licensed)
>> * JaCoCo Core Library (EPL 1.0)
>> The whole JaCoCo project uses other libraries distributed under
>> different licenses, I need to make sure that the core is EPL 1.0 only
>>
>> Areas to Improve:
>>
>> * There is no support for Ergonomy
>> * Module versions might be incorrectly specified, I did the best I could
>> * Add Groovy project support (could be trivial)
>> * Improve Gradle <-> JDK incompatibility check.
>> * Profiling
>> * Compile on Save (that's an icy territory)
>> * Improve project Settings
>> * Whatever you think...
>>
>> Future Works:
>>
>> * I also have a JavaEE support module started, I can donate somewhat
>> later to the enterprise cluster.
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Gradle Support for Apache NetBeans
Posted by Jan Lahoda <la...@gmail.com>.
Hi Laszlo,
It will be great to have Gradle support - thanks for that!
Regarding the:
groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
I don't think that can be in the source distro ("compiled code not
allowed"), but it shouldn't be too problematic to download that during
build as well, right?
Thanks for doing this!
Jan
On Sat, Dec 29, 2018 at 8:57 PM Laszlo Kishalmi <la...@gmail.com>
wrote:
> Dear all,
>
> I would like to donate my Gradle works to Apache NetBeans.
>
> Right now the code is here:
> https://github.com/lkishalmi/incubator-netbeans/tree/gradle-support
>
> I just recently rebased it on master, so there is no conflicts. If I'd
> create a PR from it that would mean 317 new files and ~35k line of code.
>
> The current state of the plugin:
>
> * It Opens Gradle Projects resource efficiently
> * It is based on the ideas found in our Maven Plugin
> * It supports JavaSE and Groovy development
> * Unit Testing
> * Code Coverage
> * JPA projects
> * Spring (the little support we have for that)
> * Navigator for project task
> * Custom Task execution
> * Output processing
> * Debugging (even single methods)
> * Creating new projects
>
> The shady side:
>
> * The Gradle <-> NetBeans project discovery and communication.
> Based on simple property serialization. Ugly Groovy code, well the
> deserialization Java code isn't that nice as well
> * Limited number of unittest
> * Being a sole developer there could be glitches here and there as of
> lack of wider testing.
> * Gradle is required to build the NetBeans <-> Gradle tooling
> This adds a binary
> groovy/gradle/netbeans-gradle-tooling/gradle/wrapper/gradle-wrapper.jar
> to the source distribution package, though this file is not
> distributed. So Apace might agree with that.
>
> Introduced External Dependencies:
>
> * Gradle Tooling API (Apache Licensed)
> o slf4j (Apache Licensed)
> * JaCoCo Core Library (EPL 1.0)
> The whole JaCoCo project uses other libraries distributed under
> different licenses, I need to make sure that the core is EPL 1.0 only
>
> Areas to Improve:
>
> * There is no support for Ergonomy
> * Module versions might be incorrectly specified, I did the best I could
> * Add Groovy project support (could be trivial)
> * Improve Gradle <-> JDK incompatibility check.
> * Profiling
> * Compile on Save (that's an icy territory)
> * Improve project Settings
> * Whatever you think...
>
> Future Works:
>
> * I also have a JavaEE support module started, I can donate somewhat
> later to the enterprise cluster.
>
>
>