You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@netbeans.apache.org by "Mark A. Claassen" <MC...@ocie.net> on 2019/04/08 18:49:48 UTC
Netbeans 11 and Gradle
I am giving Netbeans 11 a try and really appreciate the JavaEE support that is now just included. Thanks.
I also appreciate that Gradle is included, but I have having some problems.
I can submit some bugs, but I thought I would start here first to see if anyone else is having better luck.
---1---
I have a Gradle project called "Builder" with lots of sub projects.
(The "Builder" project is a standalone Gradle project that points to files in other directories and builds my distribution) The properties dialog shows the name as "Builder", but in the Netbeans file tree, it shows as "Root Project"
(This did not happen with the gradle plugin I used in previous versions)
---2---
When I try to open a build.gradle file, it opens a tab with no name on it and it shows a broken 'local history' of the file and not the file itself.
There is no button to switch back to the source. In fact, I have found no way to edit this in the Netbeans at all and have to use an external text editor to edit the file.
(This did not happen with the Gradle plugin I used in previous versions)
---3---
I have few helper Java classes that I put in the 'buildSrc' directory of my "Builder" project.
When I run my Gradle build, these build just fine, but the Netbeans Java editor is totally confused with these files and therefore cannot see any other classes because the system classes; not even files in the same package (directory).
I have a feeling Netbeans is just confused about what package these files are in.
(This, I think, did happen with the older plugin)
Does anyone else use Gradle? Have you had better luck than me?
Thanks,
Mark Claassen
Senior Software Engineer
Donnell Systems, Inc.
130 South Main Street
Leighton Plaza Suite 375
South Bend, IN 46601
E-mail: mailto:mclaassen@ocie.net
Voice: (574)232-3784
Fax: (574)232-4014
-------------------------------------------
Confidentiality Notice: OCIESERVICE
-------------------------------------------
The contents of this e-mail message and any attachments are intended solely for the addressee(s) named in this message. This communication is intended to be and to remain confidential. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not deliver, distribute, copy, disclose the contents or take any action in reliance upon the information contained in the communication or any attachments.
RE: Netbeans 11 and Gradle
Posted by "Mark A. Claassen" <MC...@ocie.net>.
For anyone following this, I reported this issue as: https://issues.apache.org/jira/browse/NETBEANS-2378
Mark Claassen
Senior Software Engineer
Donnell Systems, Inc.
130 South Main Street
Leighton Plaza Suite 375
South Bend, IN 46601
E-mail: mailto:mclaassen@ocie.net
Voice: (574)232-3784
Fax: (574)232-4014
-------------------------------------------
Confidentiality Notice: OCIESERVICE
-------------------------------------------
The contents of this e-mail message and any attachments are intended solely for the addressee(s) named in this message. This communication is intended to be and to remain confidential. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not deliver, distribute, copy, disclose the contents or take any action in reliance upon the information contained in the communication or any attachments.
From: Mark A. Claassen <MC...@ocie.net>
Sent: Monday, April 8, 2019 3:11 PM
To: Scott Palmer <sw...@gmail.com>
Cc: users@netbeans.apache.org
Subject: RE: Netbeans 11 and Gradle
Thanks for the tip on #1, I had a description in there that I forgot about! The old plugin must not have read that.
Since it is working for you, I tried some different things. When I went to Tools -> Options and clicked on Groovy, it “activated” groovy. Now the editor is working.
Now, if only #3 was solved…
Thank you so much!
Mark Claassen
Senior Software Engineer
Donnell Systems, Inc.
130 South Main Street
Leighton Plaza Suite 375
South Bend, IN 46601
E-mail: mailto:mclaassen@ocie.net
Voice: (574)232-3784
Fax: (574)232-4014
-------------------------------------------
Confidentiality Notice: OCIESERVICE
-------------------------------------------
The contents of this e-mail message and any attachments are intended solely for the addressee(s) named in this message. This communication is intended to be and to remain confidential. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not deliver, distribute, copy, disclose the contents or take any action in reliance upon the information contained in the communication or any attachments.
From: Scott Palmer <sw...@gmail.com>>
Sent: Monday, April 8, 2019 2:59 PM
To: Mark A. Claassen <MC...@ocie.net>>
Cc: users@netbeans.apache.org<ma...@netbeans.apache.org>
Subject: Re: Netbeans 11 and Gradle
Hi Mark,
I use Gradle exclusively. (To the point where if I have to work on a project that isn’t using Gradle the first thing I do is convert it to Gradle so I don’t have to suffer further ;-).)
#1 - Check the project description as defined in the build.gradle file. Then check the option: Java->Gradle->Appearance->”Use Project Description as Project Name”
#2 - I don’t see this. When opening a build.gradle file, the project name is used as the document title. Editing works as expected and the project is automatically refreshed when changes are saved.
#3 - This is an issue. It seems added source folders don’t work smoothly. In my case I have Java source folders that are populated during the build, but NB never notices that there are files in them, even after I force a build to populate the folder.
Regards,
Scott
On Apr 8, 2019, at 2:49 PM, Mark A. Claassen <MC...@ocie.net>> wrote:
I am giving Netbeans 11 a try and really appreciate the JavaEE support that is now just included. Thanks.
I also appreciate that Gradle is included, but I have having some problems.
I can submit some bugs, but I thought I would start here first to see if anyone else is having better luck.
---1---
I have a Gradle project called "Builder" with lots of sub projects.
(The "Builder" project is a standalone Gradle project that points to files in other directories and builds my distribution) The properties dialog shows the name as “Builder”, but in the Netbeans file tree, it shows as "Root Project"
(This did not happen with the gradle plugin I used in previous versions)
---2---
When I try to open a build.gradle file, it opens a tab with no name on it and it shows a broken 'local history' of the file and not the file itself.
There is no button to switch back to the source. In fact, I have found no way to edit this in the Netbeans at all and have to use an external text editor to edit the file.
(This did not happen with the Gradle plugin I used in previous versions)
---3---
I have few helper Java classes that I put in the 'buildSrc' directory of my "Builder" project.
When I run my Gradle build, these build just fine, but the Netbeans Java editor is totally confused with these files and therefore cannot see any other classes because the system classes; not even files in the same package (directory).
I have a feeling Netbeans is just confused about what package these files are in.
(This, I think, did happen with the older plugin)
Does anyone else use Gradle? Have you had better luck than me?
Thanks,
Mark Claassen
Senior Software Engineer
Donnell Systems, Inc.
130 South Main Street
Leighton Plaza Suite 375
South Bend, IN 46601
E-mail: mailto:mclaassen@ocie.net
Voice: (574)232-3784
Fax: (574)232-4014
-------------------------------------------
Confidentiality Notice: OCIESERVICE
-------------------------------------------
The contents of this e-mail message and any attachments are intended solely for the addressee(s) named in this message. This communication is intended to be and to remain confidential. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not deliver, distribute, copy, disclose the contents or take any action in reliance upon the information contained in the communication or any attachments.
RE: Netbeans 11 and Gradle
Posted by "Mark A. Claassen" <MC...@ocie.net>.
Thanks for the tip on #1, I had a description in there that I forgot about! The old plugin must not have read that.
Since it is working for you, I tried some different things. When I went to Tools -> Options and clicked on Groovy, it “activated” groovy. Now the editor is working.
Now, if only #3 was solved…
Thank you so much!
Mark Claassen
Senior Software Engineer
Donnell Systems, Inc.
130 South Main Street
Leighton Plaza Suite 375
South Bend, IN 46601
E-mail: mailto:mclaassen@ocie.net
Voice: (574)232-3784
Fax: (574)232-4014
-------------------------------------------
Confidentiality Notice: OCIESERVICE
-------------------------------------------
The contents of this e-mail message and any attachments are intended solely for the addressee(s) named in this message. This communication is intended to be and to remain confidential. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not deliver, distribute, copy, disclose the contents or take any action in reliance upon the information contained in the communication or any attachments.
From: Scott Palmer <sw...@gmail.com>
Sent: Monday, April 8, 2019 2:59 PM
To: Mark A. Claassen <MC...@ocie.net>
Cc: users@netbeans.apache.org
Subject: Re: Netbeans 11 and Gradle
Hi Mark,
I use Gradle exclusively. (To the point where if I have to work on a project that isn’t using Gradle the first thing I do is convert it to Gradle so I don’t have to suffer further ;-).)
#1 - Check the project description as defined in the build.gradle file. Then check the option: Java->Gradle->Appearance->”Use Project Description as Project Name”
#2 - I don’t see this. When opening a build.gradle file, the project name is used as the document title. Editing works as expected and the project is automatically refreshed when changes are saved.
#3 - This is an issue. It seems added source folders don’t work smoothly. In my case I have Java source folders that are populated during the build, but NB never notices that there are files in them, even after I force a build to populate the folder.
Regards,
Scott
On Apr 8, 2019, at 2:49 PM, Mark A. Claassen <MC...@ocie.net>> wrote:
I am giving Netbeans 11 a try and really appreciate the JavaEE support that is now just included. Thanks.
I also appreciate that Gradle is included, but I have having some problems.
I can submit some bugs, but I thought I would start here first to see if anyone else is having better luck.
---1---
I have a Gradle project called "Builder" with lots of sub projects.
(The "Builder" project is a standalone Gradle project that points to files in other directories and builds my distribution) The properties dialog shows the name as “Builder”, but in the Netbeans file tree, it shows as "Root Project"
(This did not happen with the gradle plugin I used in previous versions)
---2---
When I try to open a build.gradle file, it opens a tab with no name on it and it shows a broken 'local history' of the file and not the file itself.
There is no button to switch back to the source. In fact, I have found no way to edit this in the Netbeans at all and have to use an external text editor to edit the file.
(This did not happen with the Gradle plugin I used in previous versions)
---3---
I have few helper Java classes that I put in the 'buildSrc' directory of my "Builder" project.
When I run my Gradle build, these build just fine, but the Netbeans Java editor is totally confused with these files and therefore cannot see any other classes because the system classes; not even files in the same package (directory).
I have a feeling Netbeans is just confused about what package these files are in.
(This, I think, did happen with the older plugin)
Does anyone else use Gradle? Have you had better luck than me?
Thanks,
Mark Claassen
Senior Software Engineer
Donnell Systems, Inc.
130 South Main Street
Leighton Plaza Suite 375
South Bend, IN 46601
E-mail: mailto:mclaassen@ocie.net
Voice: (574)232-3784
Fax: (574)232-4014
-------------------------------------------
Confidentiality Notice: OCIESERVICE
-------------------------------------------
The contents of this e-mail message and any attachments are intended solely for the addressee(s) named in this message. This communication is intended to be and to remain confidential. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not deliver, distribute, copy, disclose the contents or take any action in reliance upon the information contained in the communication or any attachments.
Re: Netbeans 11 and Gradle
Posted by Scott Palmer <sw...@gmail.com>.
Hi Mark,
I use Gradle exclusively. (To the point where if I have to work on a project that isn’t using Gradle the first thing I do is convert it to Gradle so I don’t have to suffer further ;-).)
#1 - Check the project description as defined in the build.gradle file. Then check the option: Java->Gradle->Appearance->”Use Project Description as Project Name”
#2 - I don’t see this. When opening a build.gradle file, the project name is used as the document title. Editing works as expected and the project is automatically refreshed when changes are saved.
#3 - This is an issue. It seems added source folders don’t work smoothly. In my case I have Java source folders that are populated during the build, but NB never notices that there are files in them, even after I force a build to populate the folder.
Regards,
Scott
> On Apr 8, 2019, at 2:49 PM, Mark A. Claassen <MC...@ocie.net> wrote:
>
> I am giving Netbeans 11 a try and really appreciate the JavaEE support that is now just included. Thanks.
>
> I also appreciate that Gradle is included, but I have having some problems.
> I can submit some bugs, but I thought I would start here first to see if anyone else is having better luck.
>
> ---1---
> I have a Gradle project called "Builder" with lots of sub projects.
> (The "Builder" project is a standalone Gradle project that points to files in other directories and builds my distribution) The properties dialog shows the name as “Builder”, but in the Netbeans file tree, it shows as "Root Project"
> (This did not happen with the gradle plugin I used in previous versions)
>
> ---2---
> When I try to open a build.gradle file, it opens a tab with no name on it and it shows a broken 'local history' of the file and not the file itself.
> There is no button to switch back to the source. In fact, I have found no way to edit this in the Netbeans at all and have to use an external text editor to edit the file.
> (This did not happen with the Gradle plugin I used in previous versions)
>
> ---3---
> I have few helper Java classes that I put in the 'buildSrc' directory of my "Builder" project.
> When I run my Gradle build, these build just fine, but the Netbeans Java editor is totally confused with these files and therefore cannot see any other classes because the system classes; not even files in the same package (directory).
> I have a feeling Netbeans is just confused about what package these files are in.
> (This, I think, did happen with the older plugin)
>
> Does anyone else use Gradle? Have you had better luck than me?
>
> Thanks,
>
>
> Mark Claassen
> Senior Software Engineer
>
> Donnell Systems, Inc.
> 130 South Main Street
> Leighton Plaza Suite 375
> South Bend, IN 46601
> E-mail: mailto:mclaassen@ocie.net <ma...@ocie.net>
> Voice: (574)232-3784
> Fax: (574)232-4014
>
> -------------------------------------------
> Confidentiality Notice: OCIESERVICE
> -------------------------------------------
> The contents of this e-mail message and any attachments are intended solely for the addressee(s) named in this message. This communication is intended to be and to remain confidential. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and its attachments. Do not deliver, distribute, copy, disclose the contents or take any action in reliance upon the information contained in the communication or any attachments.