[jira] [Commented] (NETBEANS-2608) Graphics: Can't tell when a project has an error

2020-01-07 Thread Lou Hamersly (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17010095#comment-17010095
 ] 

Lou Hamersly commented on NETBEANS-2608:


Wow that took a long time... this is probably resolved with NETBEANS-2417, 
though. [~arren]

> Graphics: Can't tell when a project has an error
> 
>
> Key: NETBEANS-2608
> URL: https://issues.apache.org/jira/browse/NETBEANS-2608
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.0
>Reporter: Shevek
>Priority: Major
> Attachments: nb-gradle-icons.png
>
>
> I care about only one thing in the project summary: Does a project have an 
> error.
> Look at the attached image, and tell me at a glance which subprojects have 
> errors?
> I can't see because there's too much other noise in confusing colours.
> Please can you remove all unnecessary noise from the project icon EXCEPT red 
> for error, and something NOT-in-the-red-spectrum for OK.
> The kind of dark orange coffee cup makes the icon totally useless.
> Imagine 200 of these icons on a 4K screen.
> I don't care if it's a gradle project or a maven project, whether anyone 
> thinks it contains XML or EJBs, or is upside down or written in greek. I KNOW 
> that stuff anyway, it's not a rapidly changing property of a project. What I 
> want the IDE to tell me is "Does this contain an error". There's no other 
> useful information there.
> Please note, just for the record: None of these subprojects have errors, it's 
> a NetBeans synchronization or source-rescanning bug that it thinks they do. 
> When I ask it to compile, it's fine. But that's not what this ticket is about.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-2417) update Gradle logo/icon

2019-10-10 Thread Lou Hamersly (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949117#comment-16949117
 ] 

Lou Hamersly commented on NETBEANS-2417:


[~lkishalmi] Just my own opinion and maybe a minority, but I do like the blue 
icons better. White's a little too close to a grey/disabled look IMO.

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, gradle1.png, 
> gradle2.png, image-2019-07-02-10-27-44-307.png, 
> image-2019-07-02-10-31-08-337.png, image-2019-07-02-10-33-19-023.png, 
> image-2019-07-02-10-49-16-797.png, image-2019-07-02-11-47-13-922.png, 
> image-2019-07-02-11-48-06-685.png, image-2019-07-02-11-49-01-655.png, 
> image-2019-07-02-11-50-09-232.png, image-2019-07-02-11-55-58-042.png, 
> image-2019-07-02-20-55-48-539.png, image-2019-10-07-19-58-12-859.png, 
> image-2019-10-07-19-58-34-360.png, image-2019-10-07-19-59-08-294.png, 
> image-2019-10-07-19-59-20-982.png, image-2019-10-07-19-59-37-293.png, 
> image-2019-10-07-20-00-15-046.png, image-2019-10-07-20-00-35-172.png, 
> nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

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



[jira] [Commented] (NETBEANS-2417) update Gradle logo/icon

2019-09-10 Thread Lou Hamersly (Jira)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16927247#comment-16927247
 ] 

Lou Hamersly commented on NETBEANS-2417:


Monitoring this every so often for activity, so if any additional help is 
needed I might take a few days, but I should be along eventually. 

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, gradle1.png, 
> gradle2.png, image-2019-07-02-10-27-44-307.png, 
> image-2019-07-02-10-31-08-337.png, image-2019-07-02-10-33-19-023.png, 
> image-2019-07-02-10-49-16-797.png, image-2019-07-02-11-47-13-922.png, 
> image-2019-07-02-11-48-06-685.png, image-2019-07-02-11-49-01-655.png, 
> image-2019-07-02-11-50-09-232.png, image-2019-07-02-11-55-58-042.png, 
> image-2019-07-02-20-55-48-539.png, nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

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

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



[jira] [Commented] (NETBEANS-2417) update Gradle logo/icon

2019-07-19 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16889294#comment-16889294
 ] 

Lou Hamersly commented on NETBEANS-2417:


I see, they're under gradle.javaee on the 111 branch. Easy enough to overwrite 
with the ones of the same name from 
groovy/gradle/src/org/netbeans/modules/gradle/resources.

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, gradle1.png, 
> gradle2.png, image-2019-07-02-10-27-44-307.png, 
> image-2019-07-02-10-31-08-337.png, image-2019-07-02-10-33-19-023.png, 
> image-2019-07-02-10-49-16-797.png, image-2019-07-02-11-47-13-922.png, 
> image-2019-07-02-11-48-06-685.png, image-2019-07-02-11-49-01-655.png, 
> image-2019-07-02-11-50-09-232.png, image-2019-07-02-11-55-58-042.png, 
> image-2019-07-02-20-55-48-539.png, nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

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



[jira] [Commented] (NETBEANS-2417) update Gradle logo/icon

2019-07-17 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16887415#comment-16887415
 ] 

Lou Hamersly commented on NETBEANS-2417:


> Also, I'm noticing in y'all's screenshots that the old logo is still in use 
>in the new project dialog for 'web application'. Did we miss a file? 

Good catch! 

I see we did miss one, I can get that fixed. We could put the globe in the 
upper-left-corner, but I think I agree with Jennifer that maybe we should just 
leave it out entirely. (It would probably need to be resized even smaller and 
we've seen how that can be problematic...) 

I think those are webProjectIcon.png and webProjectIcon_dark.png inside 
gradle/resources?

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, gradle1.png, 
> gradle2.png, image-2019-07-02-10-27-44-307.png, 
> image-2019-07-02-10-31-08-337.png, image-2019-07-02-10-33-19-023.png, 
> image-2019-07-02-10-49-16-797.png, image-2019-07-02-11-47-13-922.png, 
> image-2019-07-02-11-48-06-685.png, image-2019-07-02-11-49-01-655.png, 
> image-2019-07-02-11-50-09-232.png, image-2019-07-02-11-55-58-042.png, 
> image-2019-07-02-20-55-48-539.png, nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

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



[jira] [Comment Edited] (NETBEANS-2417) update Gradle logo/icon

2019-07-07 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879949#comment-16879949
 ] 

Lou Hamersly edited comment on NETBEANS-2417 at 7/7/19 8:43 PM:


Slightly different process but I think this is what you're looking for, dark 
eye fix + light leg fix. Best version yet I think, Nimbus/Darcula: 

!gradle2.png!

If you want to build yourself: 

https://github.com/apache/netbeans/pull/1269


was (Author: louhy):
Slightly different process but I think this is what you're looking for, dark 
eye fix + light leg fix. Best version yet I think, Nimbus/Darcula: 

!gradle2.png!

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, gradle1.png, 
> gradle2.png, image-2019-07-02-10-27-44-307.png, 
> image-2019-07-02-10-31-08-337.png, image-2019-07-02-10-33-19-023.png, 
> image-2019-07-02-10-49-16-797.png, image-2019-07-02-11-47-13-922.png, 
> image-2019-07-02-11-48-06-685.png, image-2019-07-02-11-49-01-655.png, 
> image-2019-07-02-11-50-09-232.png, image-2019-07-02-11-55-58-042.png, 
> image-2019-07-02-20-55-48-539.png, nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2417) update Gradle logo/icon

2019-07-07 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879949#comment-16879949
 ] 

Lou Hamersly commented on NETBEANS-2417:


Slightly different process but I think this is what you're looking for, dark 
eye fix + light leg fix. Best version yet I think, Nimbus/Darcula: 

!gradle2.png!

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, gradle1.png, 
> gradle2.png, image-2019-07-02-10-27-44-307.png, 
> image-2019-07-02-10-31-08-337.png, image-2019-07-02-10-33-19-023.png, 
> image-2019-07-02-10-49-16-797.png, image-2019-07-02-11-47-13-922.png, 
> image-2019-07-02-11-48-06-685.png, image-2019-07-02-11-49-01-655.png, 
> image-2019-07-02-11-50-09-232.png, image-2019-07-02-11-55-58-042.png, 
> image-2019-07-02-20-55-48-539.png, nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Updated] (NETBEANS-2417) update Gradle logo/icon

2019-07-07 Thread Lou Hamersly (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lou Hamersly updated NETBEANS-2417:
---
Attachment: gradle2.png

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, gradle1.png, 
> gradle2.png, image-2019-07-02-10-27-44-307.png, 
> image-2019-07-02-10-31-08-337.png, image-2019-07-02-10-33-19-023.png, 
> image-2019-07-02-10-49-16-797.png, image-2019-07-02-11-47-13-922.png, 
> image-2019-07-02-11-48-06-685.png, image-2019-07-02-11-49-01-655.png, 
> image-2019-07-02-11-50-09-232.png, image-2019-07-02-11-55-58-042.png, 
> image-2019-07-02-20-55-48-539.png, nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2417) update Gradle logo/icon

2019-07-07 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879814#comment-16879814
 ] 

Lou Hamersly commented on NETBEANS-2417:


[~lkishalmi] I think I kind of see what you mean if you're talking about the 
right side of the capture I posted above (very subtle). I'm not sure how much 
of that is due to that shade of grey's interaction (possibly transparency 
related) with the color limitations (branding guidelines). If you're saying you 
prefer those, I could try redoing them using another method like you suggested 
to try and get the aliasing to look better, but you'll have to let me know. 

Pixel wise, I don't see an obvious difference between mine (white/dark) and the 
sample you posted. I do see a slight brightness difference where the top is a 
touch lighter. Not sure why that would be, as I had used the official assets 
they provide for this kind of thing. 

!gradle1.png!

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, gradle1.png, 
> image-2019-07-02-10-27-44-307.png, image-2019-07-02-10-31-08-337.png, 
> image-2019-07-02-10-33-19-023.png, image-2019-07-02-10-49-16-797.png, 
> image-2019-07-02-11-47-13-922.png, image-2019-07-02-11-48-06-685.png, 
> image-2019-07-02-11-49-01-655.png, image-2019-07-02-11-50-09-232.png, 
> image-2019-07-02-11-55-58-042.png, image-2019-07-02-20-55-48-539.png, 
> nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Updated] (NETBEANS-2417) update Gradle logo/icon

2019-07-07 Thread Lou Hamersly (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lou Hamersly updated NETBEANS-2417:
---
Attachment: gradle1.png

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, gradle1.png, 
> image-2019-07-02-10-27-44-307.png, image-2019-07-02-10-31-08-337.png, 
> image-2019-07-02-10-33-19-023.png, image-2019-07-02-10-49-16-797.png, 
> image-2019-07-02-11-47-13-922.png, image-2019-07-02-11-48-06-685.png, 
> image-2019-07-02-11-49-01-655.png, image-2019-07-02-11-50-09-232.png, 
> image-2019-07-02-11-55-58-042.png, image-2019-07-02-20-55-48-539.png, 
> nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2417) update Gradle logo/icon

2019-07-03 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878218#comment-16878218
 ] 

Lou Hamersly commented on NETBEANS-2417:


I thought the point was that it should be ~8 pixels wide (like the "M") to be 
consistent. So then, what you're suggesting basically blocks this entire 
change. I'm not sure why it matters that Maven was first, Ant was "more first" 
and the icons do their own thing entirely, right? 

Also NETBEANS-2608 remains an issue that would be nice to address 
simultaneously, the problem there is icons in the Projects view with 
significant red in them. 

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, 
> image-2019-07-02-10-27-44-307.png, image-2019-07-02-10-31-08-337.png, 
> image-2019-07-02-10-33-19-023.png, image-2019-07-02-10-49-16-797.png, 
> image-2019-07-02-11-47-13-922.png, image-2019-07-02-11-48-06-685.png, 
> image-2019-07-02-11-49-01-655.png, image-2019-07-02-11-50-09-232.png, 
> image-2019-07-02-11-55-58-042.png, image-2019-07-02-20-55-48-539.png, 
> nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Comment Edited] (NETBEANS-2417) update Gradle logo/icon

2019-07-02 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877389#comment-16877389
 ] 

Lou Hamersly edited comment on NETBEANS-2417 at 7/3/19 12:58 AM:
-

[~matthiasblaesing] From when I was working with this previously, the elephant 
isn't going to resemble anything if it's smaller than this (like those little 
tiny "m" icons). (If I understand your comment correctly?)

Also I do want to call attention to this issue brought up by [~arren]: 
https://issues.apache.org/jira/browse/NETBEANS-2608 

If the coffee cup's red is the primary color of the icon, the red error 
indicators will likely remain difficult to see amongst a long list of projects. 
 

Additional caps with errors for comparison: 

!image-2019-07-02-20-55-48-539.png!

Otherwise I pretty much agree with Laszlo's analysis above (but not sure I see 
the anti-aliasing issue here). 


was (Author: louhy):
 

[~matthiasblaesing] From when I was working with this previously, the elephant 
isn't going to resemble anything if it's smaller than this (like those little 
tiny "m" icons).

Also I do want to call attention to this issue brought up by [~arren]: 
https://issues.apache.org/jira/browse/NETBEANS-2608 

If the coffee cup's red is the primary color of the icon, the red error 
indicators will likely remain difficult to see amongst a long list of projects. 
 

Additional caps with errors for comparison: 

!image-2019-07-02-20-55-48-539.png!

Otherwise I pretty much agree with Laszlo's analysis above (but not sure I see 
the anti-aliasing issue here). 

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, 
> image-2019-07-02-10-27-44-307.png, image-2019-07-02-10-31-08-337.png, 
> image-2019-07-02-10-33-19-023.png, image-2019-07-02-10-49-16-797.png, 
> image-2019-07-02-11-47-13-922.png, image-2019-07-02-11-48-06-685.png, 
> image-2019-07-02-11-49-01-655.png, image-2019-07-02-11-50-09-232.png, 
> image-2019-07-02-11-55-58-042.png, image-2019-07-02-20-55-48-539.png, 
> nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2417) update Gradle logo/icon

2019-07-02 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16877389#comment-16877389
 ] 

Lou Hamersly commented on NETBEANS-2417:


 

[~matthiasblaesing] From when I was working with this previously, the elephant 
isn't going to resemble anything if it's smaller than this (like those little 
tiny "m" icons).

Also I do want to call attention to this issue brought up by [~arren]: 
https://issues.apache.org/jira/browse/NETBEANS-2608 

If the coffee cup's red is the primary color of the icon, the red error 
indicators will likely remain difficult to see amongst a long list of projects. 
 

Additional caps with errors for comparison: 

!image-2019-07-02-20-55-48-539.png!

Otherwise I pretty much agree with Laszlo's analysis above (but not sure I see 
the anti-aliasing issue here). 

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, 
> image-2019-07-02-10-27-44-307.png, image-2019-07-02-10-31-08-337.png, 
> image-2019-07-02-10-33-19-023.png, image-2019-07-02-10-49-16-797.png, 
> image-2019-07-02-11-47-13-922.png, image-2019-07-02-11-48-06-685.png, 
> image-2019-07-02-11-49-01-655.png, image-2019-07-02-11-50-09-232.png, 
> image-2019-07-02-11-55-58-042.png, image-2019-07-02-20-55-48-539.png, 
> nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Updated] (NETBEANS-2417) update Gradle logo/icon

2019-07-02 Thread Lou Hamersly (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lou Hamersly updated NETBEANS-2417:
---
Attachment: image-2019-07-02-20-55-48-539.png

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, 
> image-2019-07-02-10-27-44-307.png, image-2019-07-02-10-31-08-337.png, 
> image-2019-07-02-10-33-19-023.png, image-2019-07-02-10-49-16-797.png, 
> image-2019-07-02-11-47-13-922.png, image-2019-07-02-11-48-06-685.png, 
> image-2019-07-02-11-49-01-655.png, image-2019-07-02-11-50-09-232.png, 
> image-2019-07-02-11-55-58-042.png, image-2019-07-02-20-55-48-539.png, 
> nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Updated] (NETBEANS-2417) update Gradle logo/icon

2019-07-02 Thread Lou Hamersly (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lou Hamersly updated NETBEANS-2417:
---
Attachment: nbIcons.png

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, 
> image-2019-07-02-10-27-44-307.png, image-2019-07-02-10-31-08-337.png, 
> image-2019-07-02-10-33-19-023.png, image-2019-07-02-10-49-16-797.png, 
> image-2019-07-02-11-47-13-922.png, image-2019-07-02-11-48-06-685.png, 
> image-2019-07-02-11-49-01-655.png, image-2019-07-02-11-50-09-232.png, 
> image-2019-07-02-11-55-58-042.png, image-2019-07-02-20-55-48-539.png, 
> nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Updated] (NETBEANS-2417) update Gradle logo/icon

2019-07-02 Thread Lou Hamersly (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lou Hamersly updated NETBEANS-2417:
---
Attachment: (was: nbIcons.png)

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, 
> image-2019-07-02-10-27-44-307.png, image-2019-07-02-10-31-08-337.png, 
> image-2019-07-02-10-33-19-023.png, image-2019-07-02-10-49-16-797.png, 
> image-2019-07-02-11-47-13-922.png, image-2019-07-02-11-48-06-685.png, 
> image-2019-07-02-11-49-01-655.png, image-2019-07-02-11-50-09-232.png, 
> image-2019-07-02-11-55-58-042.png, nb1.png, nb2.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Updated] (NETBEANS-2417) update Gradle logo/icon

2019-07-02 Thread Lou Hamersly (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lou Hamersly updated NETBEANS-2417:
---
Attachment: nbIcons.png

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: Maven-Base-Is-Type-Overlay-Is-Maven.png, 
> image-2019-07-02-10-27-44-307.png, image-2019-07-02-10-31-08-337.png, 
> image-2019-07-02-10-33-19-023.png, image-2019-07-02-10-49-16-797.png, 
> image-2019-07-02-11-47-13-922.png, image-2019-07-02-11-48-06-685.png, 
> image-2019-07-02-11-49-01-655.png, image-2019-07-02-11-50-09-232.png, 
> image-2019-07-02-11-55-58-042.png, nb1.png, nb2.png, nbIcons.png
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Comment Edited] (NETBEANS-2638) NullPointerException within GradleBaseProjectBuilder

2019-06-08 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16859275#comment-16859275
 ] 

Lou Hamersly edited comment on NETBEANS-2638 at 6/8/19 5:23 PM:


I don't _think_ this is really Android related, it just happens to be an 
Android project. Under the main project (/jmonkeyengine), I believe you can do 
the following to reproduce: 

1) Set buildAndroidExamples = true in the root project's gradle.properties file:
 # specify if SDK and Native libraries get built
 buildNativeProjects = false
 *buildAndroidExamples = true*

2) Set a valid Android SDK path in the *local.properties* file located in the 
root project folder. (I don't do Android so this was a sidetrack to get, but if 
you already have it...) 

3) As shown in the issue above, I increased the SDK version to 27 from 23 so 
the android-examples subproject starts like this: 

apply plugin: 'com.android.application'

android {
 *compileSdkVersion 27*
 *buildToolsVersion "27.0.3"*

The 3rd step may not even be necessary, I just reverted it back and I'm still 
getting the NPE. 

When starting a manual build of jme3-android examples from NB with those 
changes, I was able to reproduce this again just now. Also I'm not sure if it 
happened the first time immediately (unless I just missed it), so it might take 
a few attempts to get it to show up. But I'm definitely getting it consistently 
now on manual builds. I know I ran with stacktraces enabled a few times using 
Run Gradle->Tasks->"build" with Stack Trace set to FULL in the dropdown, so 
that may have been a trigger. 

Note: I had moved on to other things since reporting this, so I had to recreate 
the conditions just now, hopefully I'm not forgetting something. 

!nb1.png!


was (Author: louhy):
Under the main project (/jmonkeyengine), I believe you can do the following to 
reproduce: 

1) Set buildAndroidExamples = true in the root project's gradle.properties file:
# specify if SDK and Native libraries get built
buildNativeProjects = false
*buildAndroidExamples = true*

2) Set a valid Android SDK path in the *local.properties* file located in the 
root project folder. (I don't do Android so this was a sidetrack to get, but if 
you already have it...) 

3) As shown in the issue above, I increased the SDK version to 27 from 23 so 
the android-examples subproject starts like this: 

apply plugin: 'com.android.application'

android {
 *compileSdkVersion 27*
 *buildToolsVersion "27.0.3"*

The 3rd step may not even be necessary, I just reverted it back and I'm still 
getting the NPE. 

When starting a manual build of jme3-android examples from NB with those 
changes, I was able to reproduce this again just now. Also I'm not sure if it 
happened the first time immediately (unless I just missed it), so it might take 
a few attempts to get it to show up. But I'm definitely getting it consistently 
now on manual builds. I know I ran with stacktraces enabled a few times using 
Run Gradle->Tasks->"build" with Stack Trace set to FULL in the dropdown, so 
that may have been a trigger. 

Note: I had moved on to other things since reporting this, so I had to recreate 
the conditions just now, hopefully I'm not forgetting something. 

!nb1.png!

> NullPointerException within GradleBaseProjectBuilder
> 
>
> Key: NETBEANS-2638
> URL: https://issues.apache.org/jira/browse/NETBEANS-2638
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
> Environment: Linux
>Reporter: Lou Hamersly
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: nb1.png
>
>
> Encountered this error reported by NetBeans 11 with Groovy/Gradle plugin 
> 1.0.1: 
> {noformat}
> java.lang.NullPointerException
>  at java.base/java.util.AbstractCollection.addAll(AbstractCollection.java:351)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.processDependencies(GradleBaseProjectBuilder.java:128)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.build(GradleBaseProjectBuilder.java:75)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder$Extractor.extract(GradleBaseProjectBuilder.java:288)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.createGradleProject(GradleProjectCache.java:432)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.loadGradleProject(GradleProjectCache.java:257)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.access$100(GradleProjectCache.java:85)
> [catch] at 
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:348)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:326)
>  at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>  at 

[jira] [Commented] (NETBEANS-2638) NullPointerException within GradleBaseProjectBuilder

2019-06-08 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16859275#comment-16859275
 ] 

Lou Hamersly commented on NETBEANS-2638:


Under the main project (/jmonkeyengine), I believe you can do the following to 
reproduce: 

1) Set buildAndroidExamples = true in the root project's gradle.properties file:
# specify if SDK and Native libraries get built
buildNativeProjects = false
*buildAndroidExamples = true*

2) Set a valid Android SDK path in the *local.properties* file located in the 
root project folder. (I don't do Android so this was a sidetrack to get, but if 
you already have it...) 

3) As shown in the issue above, I increased the SDK version to 27 from 23 so 
the android-examples subproject starts like this: 

apply plugin: 'com.android.application'

android {
 *compileSdkVersion 27*
 *buildToolsVersion "27.0.3"*

The 3rd step may not even be necessary, I just reverted it back and I'm still 
getting the NPE. 

When starting a manual build of jme3-android examples from NB with those 
changes, I was able to reproduce this again just now. Also I'm not sure if it 
happened the first time immediately (unless I just missed it), so it might take 
a few attempts to get it to show up. But I'm definitely getting it consistently 
now on manual builds. I know I ran with stacktraces enabled a few times using 
Run Gradle->Tasks->"build" with Stack Trace set to FULL in the dropdown, so 
that may have been a trigger. 

Note: I had moved on to other things since reporting this, so I had to recreate 
the conditions just now, hopefully I'm not forgetting something. 

!nb1.png!

> NullPointerException within GradleBaseProjectBuilder
> 
>
> Key: NETBEANS-2638
> URL: https://issues.apache.org/jira/browse/NETBEANS-2638
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
> Environment: Linux
>Reporter: Lou Hamersly
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: nb1.png
>
>
> Encountered this error reported by NetBeans 11 with Groovy/Gradle plugin 
> 1.0.1: 
> {noformat}
> java.lang.NullPointerException
>  at java.base/java.util.AbstractCollection.addAll(AbstractCollection.java:351)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.processDependencies(GradleBaseProjectBuilder.java:128)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.build(GradleBaseProjectBuilder.java:75)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder$Extractor.extract(GradleBaseProjectBuilder.java:288)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.createGradleProject(GradleProjectCache.java:432)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.loadGradleProject(GradleProjectCache.java:257)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.access$100(GradleProjectCache.java:85)
> [catch] at 
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:348)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:326)
>  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){noformat}
> This was encountered building the jme3-android-examples subproject located in 
> this repository: [https://github.com/jMonkeyEngine/jmonkeyengine] 
> Unfortunately some setup (Android SDK related) would be involved to reproduce 
> (I may be able to help test), however since this appears to be "source set" 
> related, glancing at the code I suspect it may have something to do with 
> relative paths used in the build file. Build file used for the subproject is 
> below. 
> (Note  - the version number on the 4th/5th line was changed from 23 to 27 
> from the repo's version to bypass a compile issue. This NPE was encountered 
> with the below build file.)
>  
> {code:java}
> apply plugin: 'com.android.application'
> android {
>  compileSdkVersion 27
>  buildToolsVersion "27.0.3"
> lintOptions {
>  // Fix nifty gui referencing "java.awt" package.
>  disable 'InvalidPackage'
>  abortOnError false
>  }
> defaultConfig {
>  applicationId "org.jmonkeyengine.jme3androidexamples"
>  minSdkVersion 15 // Android 4.0.3 ICE CREAM SANDWICH
>  targetSdkVersion 22 // Android 5.1 LOLLIPOP
>  versionCode 1
>  versionName "1.0" // TODO: from settings.gradle
>  }
> buildTypes {
>  release {
>  minifyEnabled false
>  proguardFiles getDefaultProguardFile('proguard-android.txt'), 
> 'proguard-rules.pro'
>  }
>  }
> 

[jira] [Updated] (NETBEANS-2638) NullPointerException within GradleBaseProjectBuilder

2019-06-08 Thread Lou Hamersly (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lou Hamersly updated NETBEANS-2638:
---
Attachment: nb1.png

> NullPointerException within GradleBaseProjectBuilder
> 
>
> Key: NETBEANS-2638
> URL: https://issues.apache.org/jira/browse/NETBEANS-2638
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
> Environment: Linux
>Reporter: Lou Hamersly
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: nb1.png
>
>
> Encountered this error reported by NetBeans 11 with Groovy/Gradle plugin 
> 1.0.1: 
> {noformat}
> java.lang.NullPointerException
>  at java.base/java.util.AbstractCollection.addAll(AbstractCollection.java:351)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.processDependencies(GradleBaseProjectBuilder.java:128)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.build(GradleBaseProjectBuilder.java:75)
>  at 
> org.netbeans.modules.gradle.api.GradleBaseProjectBuilder$Extractor.extract(GradleBaseProjectBuilder.java:288)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.createGradleProject(GradleProjectCache.java:432)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.loadGradleProject(GradleProjectCache.java:257)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache.access$100(GradleProjectCache.java:85)
> [catch] at 
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:348)
>  at 
> org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:326)
>  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){noformat}
> This was encountered building the jme3-android-examples subproject located in 
> this repository: [https://github.com/jMonkeyEngine/jmonkeyengine] 
> Unfortunately some setup (Android SDK related) would be involved to reproduce 
> (I may be able to help test), however since this appears to be "source set" 
> related, glancing at the code I suspect it may have something to do with 
> relative paths used in the build file. Build file used for the subproject is 
> below. 
> (Note  - the version number on the 4th/5th line was changed from 23 to 27 
> from the repo's version to bypass a compile issue. This NPE was encountered 
> with the below build file.)
>  
> {code:java}
> apply plugin: 'com.android.application'
> android {
>  compileSdkVersion 27
>  buildToolsVersion "27.0.3"
> lintOptions {
>  // Fix nifty gui referencing "java.awt" package.
>  disable 'InvalidPackage'
>  abortOnError false
>  }
> defaultConfig {
>  applicationId "org.jmonkeyengine.jme3androidexamples"
>  minSdkVersion 15 // Android 4.0.3 ICE CREAM SANDWICH
>  targetSdkVersion 22 // Android 5.1 LOLLIPOP
>  versionCode 1
>  versionName "1.0" // TODO: from settings.gradle
>  }
> buildTypes {
>  release {
>  minifyEnabled false
>  proguardFiles getDefaultProguardFile('proguard-android.txt'), 
> 'proguard-rules.pro'
>  }
>  }
> sourceSets {
>  main {
>  java {
>  srcDir 'src/main/java'
>  }
>  assets {
>  srcDir 'src/assets'
>  srcDir '../jme3-testdata/src/main/resources'
>  srcDir '../jme3-examples/src/main/resources'
>  }
>  }
>  }
> }
> dependencies {
>  compile fileTree(dir: 'libs', include: ['*.jar'])
>  testCompile 'junit:junit:4.12'
>  compile 'com.android.support:appcompat-v7:23.3.0'
> compile project(':jme3-core')
>  compile project(':jme3-android')
>  compile project(':jme3-android-native')
>  compile project(':jme3-effects')
>  compile project(':jme3-bullet')
>  compile project(':jme3-bullet-native-android')
>  compile project(':jme3-networking')
>  compile project(':jme3-niftygui')
>  compile project(':jme3-plugins')
>  compile project(':jme3-terrain')
>  compile fileTree(dir: '../jme3-examples/build/libs', include: ['*.jar'], 
> exclude: ['*sources*.*'])
> // compile project(':jme3-examples')
> }
> {code}
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2629) "Error Node" shown when using relative path in srcDir parameter

2019-06-06 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858236#comment-16858236
 ] 

Lou Hamersly commented on NETBEANS-2629:


I agree in principle that this should be discouraged. My first instinct was 
that the project should be modified so a relative path like this isn't 
necessary. Unfortunately based on the quick testing I did, I believe this 
project may have a reason to use a relative path (maybe a little too deep to 
get into here). I haven't explored whether there's a reasonable workaround yet. 

Also I can imagine one argument: "It works fine in Gradle outside of NetBeans, 
so why shouldn't NB support it?" I don't know if I have a strong opinion on the 
matter right now, but I thought I should at least report the issue.

> "Error Node" shown when using relative path in srcDir parameter
> ---
>
> Key: NETBEANS-2629
> URL: https://issues.apache.org/jira/browse/NETBEANS-2629
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Reporter: Lou Hamersly
>Assignee: Laszlo Kishalmi
>Priority: Major
>  Labels: pull-request-available
> Attachments: Screenshot from 2019-06-02 14-18-24.png
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Error Node is displayed in Projects tab when using a relative path to a src 
> folder. An absolute path doesn't work either. 
> {code:java}
> sourceSets {
>   main {
> java {
>   srcDir 'src/main/java'
>   srcDir '../jme3-bullet/src/common/java'
> }
>   }
> }{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Created] (NETBEANS-2638) NullPointerException within GradleBaseProjectBuilder

2019-06-03 Thread Lou Hamersly (JIRA)
Lou Hamersly created NETBEANS-2638:
--

 Summary: NullPointerException within GradleBaseProjectBuilder
 Key: NETBEANS-2638
 URL: https://issues.apache.org/jira/browse/NETBEANS-2638
 Project: NetBeans
  Issue Type: Bug
  Components: projects - Gradle
 Environment: Linux
Reporter: Lou Hamersly


Encountered this error reported by NetBeans 11 with Groovy/Gradle plugin 1.0.1: 
{noformat}
java.lang.NullPointerException
 at java.base/java.util.AbstractCollection.addAll(AbstractCollection.java:351)
 at 
org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.processDependencies(GradleBaseProjectBuilder.java:128)
 at 
org.netbeans.modules.gradle.api.GradleBaseProjectBuilder.build(GradleBaseProjectBuilder.java:75)
 at 
org.netbeans.modules.gradle.api.GradleBaseProjectBuilder$Extractor.extract(GradleBaseProjectBuilder.java:288)
 at 
org.netbeans.modules.gradle.GradleProjectCache.createGradleProject(GradleProjectCache.java:432)
 at 
org.netbeans.modules.gradle.GradleProjectCache.loadGradleProject(GradleProjectCache.java:257)
 at 
org.netbeans.modules.gradle.GradleProjectCache.access$100(GradleProjectCache.java:85)
[catch] at 
org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:348)
 at 
org.netbeans.modules.gradle.GradleProjectCache$ProjectLoaderTask.call(GradleProjectCache.java:326)
 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){noformat}
This was encountered building the jme3-android-examples subproject located in 
this repository: [https://github.com/jMonkeyEngine/jmonkeyengine] 

Unfortunately some setup (Android SDK related) would be involved to reproduce 
(I may be able to help test), however since this appears to be "source set" 
related, glancing at the code I suspect it may have something to do with 
relative paths used in the build file. Build file used for the subproject is 
below. 

(Note  - the version number on the 4th/5th line was changed from 23 to 27 from 
the repo's version to bypass a compile issue. This NPE was encountered with the 
below build file.)

 
{code:java}
apply plugin: 'com.android.application'
android {
 compileSdkVersion 27
 buildToolsVersion "27.0.3"
lintOptions {
 // Fix nifty gui referencing "java.awt" package.
 disable 'InvalidPackage'
 abortOnError false
 }
defaultConfig {
 applicationId "org.jmonkeyengine.jme3androidexamples"
 minSdkVersion 15 // Android 4.0.3 ICE CREAM SANDWICH
 targetSdkVersion 22 // Android 5.1 LOLLIPOP
 versionCode 1
 versionName "1.0" // TODO: from settings.gradle
 }
buildTypes {
 release {
 minifyEnabled false
 proguardFiles getDefaultProguardFile('proguard-android.txt'), 
'proguard-rules.pro'
 }
 }
sourceSets {
 main {
 java {
 srcDir 'src/main/java'
 }
 assets {
 srcDir 'src/assets'
 srcDir '../jme3-testdata/src/main/resources'
 srcDir '../jme3-examples/src/main/resources'
 }
 }
 }
}
dependencies {
 compile fileTree(dir: 'libs', include: ['*.jar'])
 testCompile 'junit:junit:4.12'
 compile 'com.android.support:appcompat-v7:23.3.0'
compile project(':jme3-core')
 compile project(':jme3-android')
 compile project(':jme3-android-native')
 compile project(':jme3-effects')
 compile project(':jme3-bullet')
 compile project(':jme3-bullet-native-android')
 compile project(':jme3-networking')
 compile project(':jme3-niftygui')
 compile project(':jme3-plugins')
 compile project(':jme3-terrain')
 compile fileTree(dir: '../jme3-examples/build/libs', include: ['*.jar'], 
exclude: ['*sources*.*'])
// compile project(':jme3-examples')
}
{code}
 

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Created] (NETBEANS-2629) "Error Node" shown when using relative path in srcDir parameter

2019-06-02 Thread Lou Hamersly (JIRA)
Lou Hamersly created NETBEANS-2629:
--

 Summary: "Error Node" shown when using relative path in srcDir 
parameter
 Key: NETBEANS-2629
 URL: https://issues.apache.org/jira/browse/NETBEANS-2629
 Project: NetBeans
  Issue Type: Bug
  Components: projects - Gradle
Reporter: Lou Hamersly
 Attachments: Screenshot from 2019-06-02 14-18-24.png

Error Node is displayed in Projects tab when using a relative path to a src 
folder. An absolute path doesn't work either. 
{code:java}
sourceSets {
  main {
java {
  srcDir 'src/main/java'
  srcDir '../jme3-bullet/src/common/java'
}
  }
}{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2417) update Gradle logo/icon

2019-05-31 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16853505#comment-16853505
 ] 

Lou Hamersly commented on NETBEANS-2417:


[~codeJENNerator] Well, feel free to use what I put in the PR if it helps, the 
rest in your hands now. :)

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: nb1.png, nb2.png
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2417) update Gradle logo/icon

2019-05-30 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16852539#comment-16852539
 ] 

Lou Hamersly commented on NETBEANS-2417:


I've reached out to see if we can get any license clarification, etc. I guess 
we'll see what happens.

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: nb1.png, nb2.png
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2417) update Gradle logo/icon

2019-05-29 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851375#comment-16851375
 ] 

Lou Hamersly commented on NETBEANS-2417:


I'll give it some time to see if someone volunteers to help (I'm afraid of 
lawyer stuff), but in the mean time here's a teaser of what we'll be missing 
out on without elephants...

(Also, conveniently, the request in another issue to remove or change the red 
Java icon actually resolved the branding guideline question I had above.)

!nb2.png!

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: nb1.png, nb2.png
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Updated] (NETBEANS-2417) update Gradle logo/icon

2019-05-29 Thread Lou Hamersly (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lou Hamersly updated NETBEANS-2417:
---
Attachment: nb2.png

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: nb1.png, nb2.png
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2608) Graphics: Can't tell when a project has an error

2019-05-29 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851331#comment-16851331
 ] 

Lou Hamersly commented on NETBEANS-2608:


Yeah, I think it'll look nicer and fit better with Gradle's guidelines anyway. 
If we can get it past legal stuff! Ran into some questions there and may need 
help.

> Graphics: Can't tell when a project has an error
> 
>
> Key: NETBEANS-2608
> URL: https://issues.apache.org/jira/browse/NETBEANS-2608
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.0
>Reporter: Shevek
>Priority: Major
> Attachments: nb-gradle-icons.png
>
>
> I care about only one thing in the project summary: Does a project have an 
> error.
> Look at the attached image, and tell me at a glance which subprojects have 
> errors?
> I can't see because there's too much other noise in confusing colours.
> Please can you remove all unnecessary noise from the project icon EXCEPT red 
> for error, and something NOT-in-the-red-spectrum for OK.
> The kind of dark orange coffee cup makes the icon totally useless.
> Imagine 200 of these icons on a 4K screen.
> I don't care if it's a gradle project or a maven project, whether anyone 
> thinks it contains XML or EJBs, or is upside down or written in greek. I KNOW 
> that stuff anyway, it's not a rapidly changing property of a project. What I 
> want the IDE to tell me is "Does this contain an error". There's no other 
> useful information there.
> Please note, just for the record: None of these subprojects have errors, it's 
> a NetBeans synchronization or source-rescanning bug that it thinks they do. 
> When I ask it to compile, it's fine. But that's not what this ticket is about.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2417) update Gradle logo/icon

2019-05-29 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16851307#comment-16851307
 ] 

Lou Hamersly commented on NETBEANS-2417:


Hmm, hopefully we can get it worked out... maybe [~codeJENNerator] can help? If 
not there is some contact info on the branding page we could try. Not sure what 
the best solution is. 
{quote}Gradle and the Gradlephant logo are registered trademark of Gradle, Inc. 
and its subsidiaries in the United States and/or other countries. By using the 
Gradle marks you agree to follow these guidelines as well as our Terms of 
Service and all our rules and policies. Gradle reserves the right to cancel, 
modify, or change the permission in these guidelines at any time at its sole 
discretion. For further information about use of the Gradle name and 
trademarks, please contact [i...@gradle.com|mailto:i...@gradle.com].

If you are having trouble with the guidelines in any way, or are unsure if your 
usage best represents the Gradle brand, please contact our design team at 
[brand...@gradle.com|mailto:brand...@gradle.com].
{quote}

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
>  Labels: pull-request-available
> Attachments: nb1.png
>
>  Time Spent: 1h
>  Remaining Estimate: 0h
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2608) Graphics: Can't tell when a project has an error

2019-05-29 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850718#comment-16850718
 ] 

Lou Hamersly commented on NETBEANS-2608:


[~GeertjanWielenga] [~lkishalmi] I just went ahead with a PR to check out for 
this and NETBEANS-2417 ... hopefully that's cool. :)

> Graphics: Can't tell when a project has an error
> 
>
> Key: NETBEANS-2608
> URL: https://issues.apache.org/jira/browse/NETBEANS-2608
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.0
>Reporter: Shevek
>Priority: Major
> Attachments: nb-gradle-icons.png
>
>
> I care about only one thing in the project summary: Does a project have an 
> error.
> Look at the attached image, and tell me at a glance which subprojects have 
> errors?
> I can't see because there's too much other noise in confusing colours.
> Please can you remove all unnecessary noise from the project icon EXCEPT red 
> for error, and something NOT-in-the-red-spectrum for OK.
> The kind of dark orange coffee cup makes the icon totally useless.
> Imagine 200 of these icons on a 4K screen.
> I don't care if it's a gradle project or a maven project, whether anyone 
> thinks it contains XML or EJBs, or is upside down or written in greek. I KNOW 
> that stuff anyway, it's not a rapidly changing property of a project. What I 
> want the IDE to tell me is "Does this contain an error". There's no other 
> useful information there.
> Please note, just for the record: None of these subprojects have errors, it's 
> a NetBeans synchronization or source-rescanning bug that it thinks they do. 
> When I ask it to compile, it's fine. But that's not what this ticket is about.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2608) Graphics: Can't tell when a project has an error

2019-05-29 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850708#comment-16850708
 ] 

Lou Hamersly commented on NETBEANS-2608:


I already did this (locally) with the new Gradle logo as referred to in the 
linked issue NETBEANS-2417. 

Should I submit a PR with just the plain logos, no "coffee"? I agree with the 
point in the issue about the color clashing. The new Gradle logo is meant for 
light and dark backgrounds, and it looks great. It's blue so it'll address this 
issue.

> Graphics: Can't tell when a project has an error
> 
>
> Key: NETBEANS-2608
> URL: https://issues.apache.org/jira/browse/NETBEANS-2608
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 11.0
>Reporter: Shevek
>Priority: Major
> Attachments: nb-gradle-icons.png
>
>
> I care about only one thing in the project summary: Does a project have an 
> error.
> Look at the attached image, and tell me at a glance which subprojects have 
> errors?
> I can't see because there's too much other noise in confusing colours.
> Please can you remove all unnecessary noise from the project icon EXCEPT red 
> for error, and something NOT-in-the-red-spectrum for OK.
> The kind of dark orange coffee cup makes the icon totally useless.
> Imagine 200 of these icons on a 4K screen.
> I don't care if it's a gradle project or a maven project, whether anyone 
> thinks it contains XML or EJBs, or is upside down or written in greek. I KNOW 
> that stuff anyway, it's not a rapidly changing property of a project. What I 
> want the IDE to tell me is "Does this contain an error". There's no other 
> useful information there.
> Please note, just for the record: None of these subprojects have errors, it's 
> a NetBeans synchronization or source-rescanning bug that it thinks they do. 
> When I ask it to compile, it's fine. But that's not what this ticket is about.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2371) Gradle projects not properly loaded

2019-05-28 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850251#comment-16850251
 ] 

Lou Hamersly commented on NETBEANS-2371:


After some more days of use, I've found that it's actually not always possible 
to reproduce these flags. At the moment, I'm actually failing to do so. So I'm 
not sure if your issue is as unpredictable as that Shevek, but I do still think 
that we've seen the same issue. Another thing I thought of which may reproduce 
the problem is switching to another Git branch with a good amount of changes. 
If I find a more reliable way to reproduce this I'll follow up.

> Gradle projects not properly loaded
> ---
>
> Key: NETBEANS-2371
> URL: https://issues.apache.org/jira/browse/NETBEANS-2371
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0
> Environment: Netbeans 11
> Gradle 5
> Java 11
>Reporter: Netbeans User 2019
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: org-netbeans-modules-gradle-java.nbm
>
>
> - gradle module (plugin) has problem to resolve dependencies in multi project 
> as seems I can removed reds only if I go over each one subproject and do 
> clean and build (clean and build on root has no affects) and additionally it 
> seems that for some test resources even this was not enough, but it seems 
> that works old trick so creation folder and adding some new class (possible 
> even delete) and possibly with including "refresh" from Action items window.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2371) Gradle projects not properly loaded

2019-05-23 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847206#comment-16847206
 ] 

Lou Hamersly commented on NETBEANS-2371:


The recent 1.0.1 patch did fix a worse issue I posted the other day, but I 
think I'm seeing the same issue as Shevek here with the same repo: 
[https://github.com/jMonkeyEngine/jmonkeyengine] 

I've been able to reproduce it here (on Linux) like this: 
 * Load root project and all subprojects (close jme3-android-examples, I think 
this error can be ignored as unrelated)
 * There may be a few flagged red immediately; opening any file (I don't even 
need to build or edit/save) makes the flag vanish
 * Do a "gradle clean" from the project root
 * Wait a bit, red flags start popping up. A build on the subproject tends to 
remove the flag.
 * Open up one of the red flagged files. If there aren't missing import errors, 
I've seen this pretty reliably (post 1.0.1 patch) cause the "fake" error flag 
to vanish a second or two later.
 * Sometimes I'll need to do a manual clean/build inside NetBeans to resolve 
missing import errors, seems to be after a gradle clean from command line.

Jumping around between those steps, at least on my system, I can get these fake 
error flags to appear fairly reliably in at least one of the subprojects. Not 
sure if the "errors" after a command line build and clean can be helped, but 
maybe it'll help you track down a way to get NB to clear the flags on its own. 

> Gradle projects not properly loaded
> ---
>
> Key: NETBEANS-2371
> URL: https://issues.apache.org/jira/browse/NETBEANS-2371
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0
> Environment: Netbeans 11
> Gradle 5
> Java 11
>Reporter: Netbeans User 2019
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: org-netbeans-modules-gradle-java.nbm
>
>
> - gradle module (plugin) has problem to resolve dependencies in multi project 
> as seems I can removed reds only if I go over each one subproject and do 
> clean and build (clean and build on root has no affects) and additionally it 
> seems that for some test resources even this was not enough, but it seems 
> that works old trick so creation folder and adding some new class (possible 
> even delete) and possibly with including "refresh" from Action items window.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Resolved] (NETBEANS-2561) Gradle sub-projects report missing packages, but successful builds

2019-05-23 Thread Lou Hamersly (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lou Hamersly resolved NETBEANS-2561.

Resolution: Fixed

The recent Gradle/Groovy 1.0.1 patch resolved this with the exception of an 
error in the android examples subproject, which seems to have unrelated issues.

> Gradle sub-projects report missing packages, but successful builds
> --
>
> Key: NETBEANS-2561
> URL: https://issues.apache.org/jira/browse/NETBEANS-2561
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0
> Environment: Linux / Windows
>Reporter: Lou Hamersly
>Priority: Major
> Attachments: jme3-2.png, jme3.png
>
>
> NetBeans 11 (w/Gradle integration) is reporting missing imports when loading 
> an open source project.
> I'm fairly sure it's just an issue with the new Groovy/Gradle plugin, having 
> tried different configurations listed below. Also the Gradle build works fine 
> from the command line, including running examples. A few others have seen the 
> same problem and I've repeated it on two machines, so it's definitely not 
> some localized issue.
> Configurations tested so far: 
> NetBeans 10 OpenJDK 8 Gradle 4.10.2 (using old Gradle plugin) - Success
> NetBeans 10 OpenJDK 11 Gradle 4.10.2 (using old Gradle plugin) - Success*
> NetBeans 11 OpenJDK 11 Gradle 4.10.2 - Errors reported (see screencap)*
> NetBeans 11 OpenJDK 12 Gradle 4.10.2 - Errors reported (see screencap)
> *Javadoc crash in one project due to apparent bug in JDK 9-11 but not a NB 
> issue
> With a "Clean and Build Project" (on the root or subprojects), Gradle output 
> _reports_ build success, but NB still doesn't see the missing project 
> dependencies. Using the "run" task on the examples project also works (right 
> click jme3-examples sub-project->Run Gradle->Tasks->run), despite essential 
> packages being reported missing.
> Unfortunately I haven't yet been able to create a minimal project to 
> reproduce the issues, but it should be fairly easy to reproduce by opening 
> the root project and all subprojects in NB 11. 
> [https://github.com/jMonkeyEngine/jmonkeyengine] 
> I'm willing to try tracking down what's going on here, but might need some 
> advice on a good method for doing so.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2561) Gradle sub-projects report missing packages, but successful builds

2019-05-21 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16844529#comment-16844529
 ] 

Lou Hamersly commented on NETBEANS-2561:


Potentially... definitely at least a little. :) I was seeing some "reds" which 
went away after triggering a build of the subproject. But the ones in the 
screencaps wouldn't go away no matter what I tried, so those are what I was 
concerned with. 

Interestingly, I've built the master branch locally and tried running that. 
With that version most of the errors have gone away (what's left is the Android 
subproject with a Gradle plugin issue, but I'm not sure of the cause there). 

> Gradle sub-projects report missing packages, but successful builds
> --
>
> Key: NETBEANS-2561
> URL: https://issues.apache.org/jira/browse/NETBEANS-2561
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0
> Environment: Linux / Windows
>Reporter: Lou Hamersly
>Priority: Major
> Attachments: jme3-2.png, jme3.png
>
>
> NetBeans 11 (w/Gradle integration) is reporting missing imports when loading 
> an open source project.
> I'm fairly sure it's just an issue with the new Groovy/Gradle plugin, having 
> tried different configurations listed below. Also the Gradle build works fine 
> from the command line, including running examples. A few others have seen the 
> same problem and I've repeated it on two machines, so it's definitely not 
> some localized issue.
> Configurations tested so far: 
> NetBeans 10 OpenJDK 8 Gradle 4.10.2 (using old Gradle plugin) - Success
> NetBeans 10 OpenJDK 11 Gradle 4.10.2 (using old Gradle plugin) - Success*
> NetBeans 11 OpenJDK 11 Gradle 4.10.2 - Errors reported (see screencap)*
> NetBeans 11 OpenJDK 12 Gradle 4.10.2 - Errors reported (see screencap)
> *Javadoc crash in one project due to apparent bug in JDK 9-11 but not a NB 
> issue
> With a "Clean and Build Project" (on the root or subprojects), Gradle output 
> _reports_ build success, but NB still doesn't see the missing project 
> dependencies. Using the "run" task on the examples project also works (right 
> click jme3-examples sub-project->Run Gradle->Tasks->run), despite essential 
> packages being reported missing.
> Unfortunately I haven't yet been able to create a minimal project to 
> reproduce the issues, but it should be fairly easy to reproduce by opening 
> the root project and all subprojects in NB 11. 
> [https://github.com/jMonkeyEngine/jmonkeyengine] 
> I'm willing to try tracking down what's going on here, but might need some 
> advice on a good method for doing so.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Commented] (NETBEANS-2417) update Gradle logo/icon

2019-05-20 Thread Lou Hamersly (JIRA)


[ 
https://issues.apache.org/jira/browse/NETBEANS-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16844417#comment-16844417
 ] 

Lou Hamersly commented on NETBEANS-2417:


Actually that "stale" icon issue was either user error or something off with my 
build at the time. So I think it's just the first "branding rules" issue that's 
unclear here.

> update Gradle logo/icon
> ---
>
> Key: NETBEANS-2417
> URL: https://issues.apache.org/jira/browse/NETBEANS-2417
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Jennifer Strater
>Assignee: Jennifer Strater
>Priority: Trivial
> Attachments: nb1.png
>
>
> Thanks again for adding support for Gradle to Netbeans.
> The logo included in Netbeans for Gradle is the pre-2015 Gradleware logo. 
> We've recently published the newest Gradle elephant logos to 
> [https://gradle.com/brand/]. I'd be happy to help make this change if that's 
> easier for everyone.
> Please let me know how I should proceed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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



[jira] [Updated] (NETBEANS-2561) Gradle sub-projects report missing packages, but successful builds

2019-05-20 Thread Lou Hamersly (JIRA)


 [ 
https://issues.apache.org/jira/browse/NETBEANS-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lou Hamersly updated NETBEANS-2561:
---
Environment: Linux / Windows  (was: Linux Mint / Linux Solus (others 
reporting were likely on Windows))

> Gradle sub-projects report missing packages, but successful builds
> --
>
> Key: NETBEANS-2561
> URL: https://issues.apache.org/jira/browse/NETBEANS-2561
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: 11.0
> Environment: Linux / Windows
>Reporter: Lou Hamersly
>Priority: Major
> Attachments: jme3-2.png, jme3.png
>
>
> NetBeans 11 (w/Gradle integration) is reporting missing imports when loading 
> an open source project.
> I'm fairly sure it's just an issue with the new Groovy/Gradle plugin, having 
> tried different configurations listed below. Also the Gradle build works fine 
> from the command line, including running examples. A few others have seen the 
> same problem and I've repeated it on two machines, so it's definitely not 
> some localized issue.
> Configurations tested so far: 
> NetBeans 10 OpenJDK 8 Gradle 4.10.2 (using old Gradle plugin) - Success
> NetBeans 10 OpenJDK 11 Gradle 4.10.2 (using old Gradle plugin) - Success*
> NetBeans 11 OpenJDK 11 Gradle 4.10.2 - Errors reported (see screencap)*
> NetBeans 11 OpenJDK 12 Gradle 4.10.2 - Errors reported (see screencap)
> *Javadoc crash in one project due to apparent bug in JDK 9-11 but not a NB 
> issue
> With a "Clean and Build Project" (on the root or subprojects), Gradle output 
> _reports_ build success, but NB still doesn't see the missing project 
> dependencies. Using the "run" task on the examples project also works (right 
> click jme3-examples sub-project->Run Gradle->Tasks->run), despite essential 
> packages being reported missing.
> Unfortunately I haven't yet been able to create a minimal project to 
> reproduce the issues, but it should be fairly easy to reproduce by opening 
> the root project and all subprojects in NB 11. 
> [https://github.com/jMonkeyEngine/jmonkeyengine] 
> I'm willing to try tracking down what's going on here, but might need some 
> advice on a good method for doing so.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

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