Re: Does JaCoCo 0.8.2 break NetBeans code coverage?

[Emilian Bold]

Pasting my comment on https://github.com/jacoco/jacoco/issues/772

'd like to remark that from my tests (and looking at the source code)
this problem only happens under NetBeans 8.2! This does not happen
under any Apache NetBeans version.

Under NetBeans 8.2 this happens due to the way the DTD was obtained.
If you look at 
http://hg.netbeans.org/main-golden/file/tip/maven.coverage/src/org/netbeans/modules/maven/coverage/MavenCoverageProvider.java
you see a check publicId.equals("-//JACOCO//DTD Report 1.0//EN"). So
when you moved to `DTD Report 1.1` it broke NetBeans 8.2 parsing.
That's all.

--emi

On Sun, Jan 27, 2019 at 8:38 AM Emilian Bold  wrote:
>
> Philip, did you even test this with *any* Apache NetBeans version.
> This bug only seems to happen in NetBeans 8.2.
>
> --emi
>
> http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!
>
>
> On Sat, Jan 26, 2019 at 10:14 PM Philip Durbin  wrote:
> >
> > Ok, I created an issue: JaCoCo 0.8.2 breaks code coverage integration - 
> > https://issues.apache.org/jira/browse/NETBEANS-1997
> >
> > I've never worked on the NetBeans code base so I don't plan to attempt to 
> > provide a pull request unless someone out there can provide a little 
> > guidance.
> >
> > Thanks,
> >
> > Phil
> >
> > On Wed, Jan 23, 2019 at 5:41 PM Geertjan Wielenga 
> >  wrote:
> >>
> >> The reason for the problem is explained in the links you reference, would 
> >> indeed be great if you'd file an issue (and ideally make an attempt at 
> >> providing a pull request for it):
> >>
> >>> AFAIK NetBeans integration reads XML Report, which was intentionally 
> >>> changed in version 0.8.2 in a perfectly valid way by addition of new 
> >>> attribute - see #702. NetBeans integration must be fixed accordingly and 
> >>> ideally be less strict to cope with such updates in future. This problem 
> >>> should reported to developers of NetBeans integration
> >>
> >>
> >> Thanks,
> >>
> >> Gj
> >>
> >> On Wed, Jan 23, 2019 at 11:39 PM Philip Durbin  
> >> wrote:
> >>>
> >>> Please see https://github.com/IQSS/dataverse/issues/5483 and 
> >>> https://github.com/jacoco/jacoco/issues/772 for details but downgrading 
> >>> to JaCoCo 0.8.1 seems to get code coverage working again. Has anyone else 
> >>> observed this problem? Is there a ticket tracking this?
> >>>
> >>> Thanks!
> >>>
> >>> Phil

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Does JaCoCo 0.8.2 break NetBeans code coverage?

[Emilian Bold]

Philip, did you even test this with *any* Apache NetBeans version.
This bug only seems to happen in NetBeans 8.2.

--emi

http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!


On Sat, Jan 26, 2019 at 10:14 PM Philip Durbin  wrote:
>
> Ok, I created an issue: JaCoCo 0.8.2 breaks code coverage integration - 
> https://issues.apache.org/jira/browse/NETBEANS-1997
>
> I've never worked on the NetBeans code base so I don't plan to attempt to 
> provide a pull request unless someone out there can provide a little guidance.
>
> Thanks,
>
> Phil
>
> On Wed, Jan 23, 2019 at 5:41 PM Geertjan Wielenga 
>  wrote:
>>
>> The reason for the problem is explained in the links you reference, would 
>> indeed be great if you'd file an issue (and ideally make an attempt at 
>> providing a pull request for it):
>>
>>> AFAIK NetBeans integration reads XML Report, which was intentionally 
>>> changed in version 0.8.2 in a perfectly valid way by addition of new 
>>> attribute - see #702. NetBeans integration must be fixed accordingly and 
>>> ideally be less strict to cope with such updates in future. This problem 
>>> should reported to developers of NetBeans integration
>>
>>
>> Thanks,
>>
>> Gj
>>
>> On Wed, Jan 23, 2019 at 11:39 PM Philip Durbin  
>> wrote:
>>>
>>> Please see https://github.com/IQSS/dataverse/issues/5483 and 
>>> https://github.com/jacoco/jacoco/issues/772 for details but downgrading to 
>>> JaCoCo 0.8.1 seems to get code coverage working again. Has anyone else 
>>> observed this problem? Is there a ticket tracking this?
>>>
>>> Thanks!
>>>
>>> Phil

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Calling all Gradle users!

[Enrico Olivelli]

Hi,
I am trying latest nightly build on linux + jdk8 (and with jdk8 the
result is the same) on the project linked below, itis quite complex
but I was able to work on it with the 'other' plugin.
https://github.com/pravega/pravega

The project has a lot of subprojects but I can see only the first one
("pravega common") displayed in the project tree.
I can't see any particular error in logs apart from this, but it seems unrelated

INFO [org.openide.loaders.FolderInstance.Toolbars]: Cannot create
org.openide.loaders.FolderInstance$HoldInstance@259ead78[Toolbars/Build]
java.io.IOException: Cyclic reference. Somebody is trying to get value
from FolderInstance (org.openide.awt.Toolbar$Folder) from the same
thread that is processing the instance
at 
org.openide.loaders.FolderInstance.instanceCreate(FolderInstance.java:274)
at 
org.openide.loaders.FolderInstance.instanceForCookie(FolderInstance.java:555)
at 
org.openide.loaders.FolderInstance$HoldInstance.instanceCreate(FolderInstance.java:1132)
[catch] at 
org.openide.loaders.FolderInstance$1R.instances(FolderInstance.java:675)
at org.openide.loaders.FolderInstance$1R.run(FolderInstance.java:696)
at 
org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
at 
org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
at 
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)

To reproduce:
- download nightly build
- unzip
- git clone https://github.com/pravega/pravega
- open with netbeans
- install nbjavac (this pops up)
- you will see only a subproject "common", but if you look at
build.gradle or you run "clean and build" you will see that there are
plenty of modules


Any hint/help is appreciated.
I am available to any debug, I have never debugged NB before, so any
pointer will help

Cheers
Enrico

Il giorno sab 26 gen 2019 alle ore 22:42 Scott Palmer
 ha scritto:
>
> I exclusively use Gradle, so I will be testing extensively. The new plugin 
> (or maybe it is partly the NB build) does have some issues with my projects. 
> I will attempt to isolate a test case.  I already emailed Laszlo, but he 
> needs to be able to reproduce the issue.
>
> Scott
>
> > On Jan 26, 2019, at 8:07 AM, Geertjan Wielenga 
> >  wrote:
> >
> > https://github.com/gradle/gradle-build-scan-quickstart
> >
> > ...and we need more like that to play with to see whether the new Gradle 
> > support works! :-)
> >
> > Gj
> >
> >
> >
> >> On Sat, Jan 26, 2019 at 2:07 PM Geertjan Wielenga 
> >>  wrote:
> >> Hi all,
> >>
> >> If you're using Gradle in any way at all -- and especially if you have 
> >> some Gradle projects of whatever kind lying around -- we need you!
> >>
> >> Thanks to Laszlo, we have integration with Gradle for the first time in 
> >> the upcoming release scheduled to be released in March. We need as many as 
> >> possible to try out the Gradle features, i.e., simply open your existing 
> >> projects into the latest NetBeans builds and see if there are any problems 
> >> so they can be fixed in time.
> >>
> >> Interested? Please respond to this e-mail indicating your intention to try 
> >> out your existing Gradle projects in the upcoming release of Apache 
> >> NetBeans and we'll work on this together from there initially via this 
> >> mail thread.
> >>
> >> For example, without any problems at all, I was able to open and work with 
> >> this random project I found on GitHub:
> >>

-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
For additional commands, e-mail: users-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Does JaCoCo 0.8.2 break NetBeans code coverage?

[Philip Durbin]

Ok, I created an issue: JaCoCo 0.8.2 breaks code coverage integration -
https://issues.apache.org/jira/browse/NETBEANS-1997

I've never worked on the NetBeans code base so I don't plan to attempt to
provide a pull request unless someone out there can provide a little
guidance.

Thanks,

Phil

On Wed, Jan 23, 2019 at 5:41 PM Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

> The reason for the problem is explained in the links you reference, would
> indeed be great if you'd file an issue (and ideally make an attempt at
> providing a pull request for it):
>
> AFAIK NetBeans integration reads XML Report, which was intentionally
>> changed in version 0.8.2 in a perfectly valid way by addition of new
>> attribute - see #702 .
>> NetBeans integration must be fixed accordingly and ideally be less strict
>> to cope with such updates in future. This problem should reported to
>> developers of NetBeans integration
>>
>
> Thanks,
>
> Gj
>
> On Wed, Jan 23, 2019 at 11:39 PM Philip Durbin 
> wrote:
>
>> Please see https://github.com/IQSS/dataverse/issues/5483 and
>> https://github.com/jacoco/jacoco/issues/772 for details but downgrading
>> to JaCoCo 0.8.1 seems to get code coverage working again. Has anyone else
>> observed this problem? Is there a ticket tracking this?
>>
>> Thanks!
>>
>> Phil
>>
>

Re: Calling all Gradle users!

[Peter Steele]

Hi

Some good news on testing further with a brand new project and maybe some
suggestions for further enhancements

1) The exception I saw was caused by gradle running a too old version on
root project (the default gradle installation on linux was too low for jdk
11 (actually 9 10 and 11). I fixed it by running this "gradle wrapper
--gradle-version 5.1".
2) The issue of not loading the sub projects was only because I didn't open
the project from the project dialog, it opened because it was the last
project I opened. My suggestion here would be to default to open all
subprojects in this scenario.
3) The issue of the sub projects changing name was caused because I had a
settings.gradle in root project and all the sub projects from the previous
gradle pluggin. In the new netbeans it is not done this way. My suggestion
here is to better handle the behavior if settings.gradle is present and has
rootProject.nane=X set to a value different to the directory name of
the project (the previous plugin allowed you to set th emodule name and
project name).
4) The other reason for the compiling not working is because the root
project settings.gradle did not have all the includes set for the sub
project.

For 3 and 4 I think this was caused by a old version of the current gradle
plugin as it doesn't happen now. and produces similar file to the new
version of netbeans

So overall a positive experice (once I fixed issues with my project).

Regards

Peter

On Sat, Jan 26, 2019 at 3:21 PM Peter Steele  wrote:

> H
>
> I downloaded the new version and ran it side by side with the current
> setup. After installing javafx (which was new), I got an error initially
>
> java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
> at
> java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
> at
> java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
> at
> java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
> at java.base/java.util.Objects.checkIndex(Objects.java:372)
> at java.base/java.util.ArrayList.get(ArrayList.java:458)
> at
> org.netbeans.modules.gradle.options.GradleDistributionManager.evaluateGradleWrapperDistribution(GradleDistributionManager.java:209)
> at
> org.netbeans.modules.gradle.GradleProjectCache.loadGradleProject(GradleProjectCache.java:159)
> at
> org.netbeans.modules.gradle.GradleProjectCache.access$100(GradleProjectCache.java:83)
> [catch] at
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:337)
> at
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:311)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
> at
> org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
> at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
> at
> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
>
> It then installed nc-javac and requested a restart. After the restart I
> got the same error again. My root project + subprojects project was
> attempted to be opened but it didn't recognise the fact the that the root
> project was a root project and didn't load all the sub projects. When I
> closed all the projects and reopened the root project it seemed to
> recognise the root project and that it had sub projects just fine but the
> error above still came up.
>
> When I right click on the sub projects and say open project (would be much
> nicer if they were opened by default), the project name in the sub projects
> tree and the name in the new open project tree node are renamed to the
> settings.gradle -> rootProject.name value from the directory name value
> (which is the name of the project it was given when created).
>
> When I try and run the main sub project, which depends on the other sub
> projects I get lots of compile errors because it can't find the classes in
> the other sub projects. This is because the compile dependencies are
> currently set in the build.gradle of the root project. In the current
> gradle plugin it runs everything from the root projects perspective and
> allows you to choose a sub project to be the main sub project where as this
> new version of netbeans runs things from the perspective of the subproject
> in isolation.
>
> Sorry if the above doesn't make sense, I will try later on today to get an
> example project together which highlights as many of the issues as I can.
> I'll create the project in the new version of netbeans to test the creation
> process too.
>
> Regards
>
> Peter
>
>
> On Sat, Jan 26, 2019 at 2:06 PM marccollin7...@gmail.com <
> marccollin7...@gmail.com> wrote:
>
>> like i said work fine but it use a lot more memory...
>>
>> gc monitor with netbeans 10 turn around 500mb... now with this release i
>> go to 2000mb and cpu is high
>>

Manifold support

[Uwe Pachler]

Hi there,

I'm currently trying Manifold (http://manifold.systems) and I'm wondering
about support for it in NetBeans. Manifold is in some ways similar to
Lombok, in that it generates additional code while javac is running (but it
is a javac plugin rather than an annotation processor).
However, when trying it in NB 10 with the Manifold Maven sample project
project and Java 11, Netbeans won't see Manifold-generated types and
methods, highlighting code spots referencing them as errors.

Because Lombok used to work out of the box, I assumed this may be the case
with Manifold as well (obviously it is not). I'd guess NB would just need
to read the maven compiler plugin settings from the POM, compile with that
and inspect whatever .class files were produced - but maybe it doesn't work
like that...

So I'm wondering:
* Has anyone tried this before, and even had success?
* If NB can't support it now, is support planned? Any ideas what would be
necessary?

Cheers,
Uwe

Re: Calling all Gradle users!

[Peter Steele]

H

I downloaded the new version and ran it side by side with the current
setup. After installing javafx (which was new), I got an error initially

java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
at
java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at
java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at
java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
at java.base/java.util.Objects.checkIndex(Objects.java:372)
at java.base/java.util.ArrayList.get(ArrayList.java:458)
at
org.netbeans.modules.gradle.options.GradleDistributionManager.evaluateGradleWrapperDistribution(GradleDistributionManager.java:209)
at
org.netbeans.modules.gradle.GradleProjectCache.loadGradleProject(GradleProjectCache.java:159)
at
org.netbeans.modules.gradle.GradleProjectCache.access$100(GradleProjectCache.java:83)
[catch] at
org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:337)
at
org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:311)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
at
org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)

It then installed nc-javac and requested a restart. After the restart I got
the same error again. My root project + subprojects project was attempted
to be opened but it didn't recognise the fact the that the root project was
a root project and didn't load all the sub projects. When I closed all the
projects and reopened the root project it seemed to recognise the root
project and that it had sub projects just fine but the error above still
came up.

When I right click on the sub projects and say open project (would be much
nicer if they were opened by default), the project name in the sub projects
tree and the name in the new open project tree node are renamed to the
settings.gradle -> rootProject.name value from the directory name value
(which is the name of the project it was given when created).

When I try and run the main sub project, which depends on the other sub
projects I get lots of compile errors because it can't find the classes in
the other sub projects. This is because the compile dependencies are
currently set in the build.gradle of the root project. In the current
gradle plugin it runs everything from the root projects perspective and
allows you to choose a sub project to be the main sub project where as this
new version of netbeans runs things from the perspective of the subproject
in isolation.

Sorry if the above doesn't make sense, I will try later on today to get an
example project together which highlights as many of the issues as I can.
I'll create the project in the new version of netbeans to test the creation
process too.

Regards

Peter


On Sat, Jan 26, 2019 at 2:06 PM marccollin7...@gmail.com <
marccollin7...@gmail.com> wrote:

> like i said work fine but it use a lot more memory...
>
> gc monitor with netbeans 10 turn around 500mb... now with this release i
> go to 2000mb and cpu is high
>
> On 2019/01/26 13:07:14, Geertjan Wielenga
>  wrote:
> > Hi all,
> >
> > If you're using Gradle in any way at all -- and especially if you have
> some
> > Gradle projects of whatever kind lying around -- we need you!
> >
> > Thanks to Laszlo, we have integration with Gradle for the first time in
> the
> > upcoming release scheduled to be released in March. We need as many as
> > possible to try out the Gradle features, i.e., simply open your existing
> > projects into the latest NetBeans builds and see if there are any
> problems
> > so they can be fixed in time.
> >
> > Interested? Please respond to this e-mail indicating your intention to
> try
> > out your existing Gradle projects in the upcoming release of Apache
> > NetBeans and we'll work on this together from there initially via this
> mail
> > thread.
> >
> > For example, without any problems at all, I was able to open and work
> with
> > this random project I found on GitHub:
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>

Re: Glassfish on NetBeans 10

[Robert Erdt]

Yes, I will try my best to help.

Sent from my iPhone

> On Jan 26, 2019, at 8:46 AM, Geertjan Wielenga 
>  wrote:
> 
> More description and steps need to be provided.
> 
> Officially, Apache NetBeans 10 simply doesn't support Glassfish at all. You 
> must have tried to install a plugin from 8.2, which is always going to be 
> some kind of workaround.
> 
> However, in the upcoming release, Apache NetBeans 11, we'll include the 
> 'enterprise' cluster, which means the Glassfish plugin will be available 
> natively in Apache NetBeans.
> 
> However (another however), that does mean we'll need to try out that support 
> and make sure it works -- do you want to volunteer to be involved with that?
> 
> Gj
> 
>> On Sat, Jan 26, 2019 at 2:43 PM Robert Erdt  wrote:
>> I was not able to run Glassfish on NetBeans 10.
>> 
>>  
>> 
>> I was able to run Google App Engine though….
>> 
>>  
>> 
>> I am sorry I will not be able to fix the issue, Glassfish Starts, the 
>> interface between netbeans and Glassfish is lost.
>> 
>>  
>> 
>> I am one developer in a Hospital of 30,000 employees and I wish I could , I 
>> do feel loyal to NetBeans, so I am putting the issue out there.
>> 
>>  
>> 
>> Rob Erdt

Re: Glassfish on NetBeans 10

[Geertjan Wielenga]

More description and steps need to be provided.

Officially, Apache NetBeans 10 simply doesn't support Glassfish at all. You
must have tried to install a plugin from 8.2, which is always going to be
some kind of workaround.

However, in the upcoming release, Apache NetBeans 11, we'll include the
'enterprise' cluster, which means the Glassfish plugin will be available
natively in Apache NetBeans.

However (another however), that does mean we'll need to try out that
support and make sure it works -- do you want to volunteer to be involved
with that?

Gj

On Sat, Jan 26, 2019 at 2:43 PM Robert Erdt  wrote:

> I was not able to run Glassfish on NetBeans 10.
>
>
>
> I was able to run Google App Engine though….
>
>
>
> I am sorry I will not be able to fix the issue, Glassfish Starts, the
> interface between netbeans and Glassfish is lost.
>
>
>
> I am one developer in a Hospital of 30,000 employees and I wish I could ,
> I do feel loyal to NetBeans, so I am putting the issue out there.
>
>
>
> Rob Erdt
>

Glassfish on NetBeans 10

[Robert Erdt]

I was not able to run Glassfish on NetBeans 10.

 

I was able to run Google App Engine though..

 

I am sorry I will not be able to fix the issue, Glassfish Starts, the
interface between netbeans and Glassfish is lost.

 

I am one developer in a Hospital of 30,000 employees and I wish I could , I
do feel loyal to NetBeans, so I am putting the issue out there.

 

Rob Erdt

Re: Calling all Gradle users!

[Geertjan Wielenga]

The Gradle support that will be in the next release of Apache NetBeans is
completely different to the well known NetBeans Gradle plugin. In other
words, two different Gradle plugins have been created, Laszlo's one needs
to be explored by all Gradle users to see whether it makes sense, opens
your projects, works correctly, etc. I.e., you will not need to install a
separate Gradle plugin and the support that there will be is different to
what the Gradle plugin provides.

Anyway, best is to download the latest build and simply open your existing
projects and see what happens -- and report back here, and if there are
problems please provide a reproducible scenario ideally via a project on
GitHub:

https://builds.apache.org/job/incubator-netbeans-linux/lastSuccessfulBuild/artifact/nbbuild/

Thanks!

Gj




On Sat, Jan 26, 2019 at 2:33 PM Peter Steele  wrote:

> I am a big gradle user, I currently use the gradle plugin setup with a
> root project and many sub projects. I am interested in helping. I'm
> currently on netbeans 10 with jdk 11 (there is a minimum version of gradle
> required for Jdk 11)
>
> On Sat, 26 Jan 2019, 13:07 Geertjan Wielenga
> 
>> Hi all,
>>
>> If you're using Gradle in any way at all -- and especially if you have
>> some Gradle projects of whatever kind lying around -- we need you!
>>
>> Thanks to Laszlo, we have integration with Gradle for the first time in
>> the upcoming release scheduled to be released in March. We need as many as
>> possible to try out the Gradle features, i.e., simply open your existing
>> projects into the latest NetBeans builds and see if there are any problems
>> so they can be fixed in time.
>>
>> Interested? Please respond to this e-mail indicating your intention to
>> try out your existing Gradle projects in the upcoming release of Apache
>> NetBeans and we'll work on this together from there initially via this mail
>> thread.
>>
>> For example, without any problems at all, I was able to open and work
>> with this random project I found on GitHub:
>>
>>

Re: Calling all Gradle users!

[Peter Steele]

I am a big gradle user, I currently use the gradle plugin setup with a root
project and many sub projects. I am interested in helping. I'm currently on
netbeans 10 with jdk 11 (there is a minimum version of gradle required for
Jdk 11)

On Sat, 26 Jan 2019, 13:07 Geertjan Wielenga
 Hi all,
>
> If you're using Gradle in any way at all -- and especially if you have
> some Gradle projects of whatever kind lying around -- we need you!
>
> Thanks to Laszlo, we have integration with Gradle for the first time in
> the upcoming release scheduled to be released in March. We need as many as
> possible to try out the Gradle features, i.e., simply open your existing
> projects into the latest NetBeans builds and see if there are any problems
> so they can be fixed in time.
>
> Interested? Please respond to this e-mail indicating your intention to try
> out your existing Gradle projects in the upcoming release of Apache
> NetBeans and we'll work on this together from there initially via this mail
> thread.
>
> For example, without any problems at all, I was able to open and work with
> this random project I found on GitHub:
>
>

Re: Calling all Gradle users!

[Geertjan Wielenga]

https://github.com/gradle/gradle-build-scan-quickstart

...and we need more like that to play with to see whether the new Gradle
support works! :-)

Gj



On Sat, Jan 26, 2019 at 2:07 PM Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

> Hi all,
>
> If you're using Gradle in any way at all -- and especially if you have
> some Gradle projects of whatever kind lying around -- we need you!
>
> Thanks to Laszlo, we have integration with Gradle for the first time in
> the upcoming release scheduled to be released in March. We need as many as
> possible to try out the Gradle features, i.e., simply open your existing
> projects into the latest NetBeans builds and see if there are any problems
> so they can be fixed in time.
>
> Interested? Please respond to this e-mail indicating your intention to try
> out your existing Gradle projects in the upcoming release of Apache
> NetBeans and we'll work on this together from there initially via this mail
> thread.
>
> For example, without any problems at all, I was able to open and work with
> this random project I found on GitHub:
>
>

Calling all Gradle users!

[Geertjan Wielenga]

Hi all,

If you're using Gradle in any way at all -- and especially if you have some
Gradle projects of whatever kind lying around -- we need you!

Thanks to Laszlo, we have integration with Gradle for the first time in the
upcoming release scheduled to be released in March. We need as many as
possible to try out the Gradle features, i.e., simply open your existing
projects into the latest NetBeans builds and see if there are any problems
so they can be fixed in time.

Interested? Please respond to this e-mail indicating your intention to try
out your existing Gradle projects in the upcoming release of Apache
NetBeans and we'll work on this together from there initially via this mail
thread.

For example, without any problems at all, I was able to open and work with
this random project I found on GitHub: