[jira] [Updated] (NETBEANS-2004) No real Support for Gradle Modular Projects.

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi updated NETBEANS-2004:
--
Summary: No real Support for Gradle Modular Projects.  (was: Gradle modular 
project shows errors in all classes, but tasks run fine )

> No real Support for Gradle Modular Projects.
> 
>
> Key: NETBEANS-2004
> URL: https://issues.apache.org/jira/browse/NETBEANS-2004
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> 20190127-unknown-revn)
> Java: 11.0.2; OpenJDK 64-Bit Server VM 11.0.2+7
> Runtime: OpenJDK Runtime Environment 11.0.2+7
>Reporter: Jose Pereda
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: Bildschirmfoto 2019-02-06 um 17.22.17.png, Captura de 
> pantalla 2019-01-27 a las 19.55.13.png, gradleJava.zip
>
>
> Opening a gradle non-modular project works fine, but when the project is 
> modular, it shows errors all over the place.
> However, Clean, Build, Run, or any of the gradle tasks work fine. 
> !Captura de pantalla 2019-01-27 a las 19.55.13.png|width=1328,height=789!
>  
> See OpenJFX samples 
> [non-modular|https://github.com/openjfx/samples/tree/master/IDE/NetBeans/Non-Modular/Gradle/hellofx]
>  and 
> [modular|https://github.com/openjfx/samples/tree/master/IDE/NetBeans/Modular/Gradle/hellofx].
>  



--
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] [Assigned] (NETBEANS-2004) Gradle modular project shows errors in all classes, but tasks run fine

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi reassigned NETBEANS-2004:
-

Assignee: Laszlo Kishalmi

> Gradle modular project shows errors in all classes, but tasks run fine 
> ---
>
> Key: NETBEANS-2004
> URL: https://issues.apache.org/jira/browse/NETBEANS-2004
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> 20190127-unknown-revn)
> Java: 11.0.2; OpenJDK 64-Bit Server VM 11.0.2+7
> Runtime: OpenJDK Runtime Environment 11.0.2+7
>Reporter: Jose Pereda
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: Bildschirmfoto 2019-02-06 um 17.22.17.png, Captura de 
> pantalla 2019-01-27 a las 19.55.13.png, gradleJava.zip
>
>
> Opening a gradle non-modular project works fine, but when the project is 
> modular, it shows errors all over the place.
> However, Clean, Build, Run, or any of the gradle tasks work fine. 
> !Captura de pantalla 2019-01-27 a las 19.55.13.png|width=1328,height=789!
>  
> See OpenJFX samples 
> [non-modular|https://github.com/openjfx/samples/tree/master/IDE/NetBeans/Non-Modular/Gradle/hellofx]
>  and 
> [modular|https://github.com/openjfx/samples/tree/master/IDE/NetBeans/Modular/Gradle/hellofx].
>  



--
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-1824) java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags

2019-02-10 Thread Bernard (JIRA)


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

Bernard commented on NETBEANS-1824:
---

Thanks for the Jira comment. But what about the NetBeans issue? Is anybody 
looking at this? If not, what is the reason for this?

> java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags
> ---
>
> Key: NETBEANS-1824
> URL: https://issues.apache.org/jira/browse/NETBEANS-1824
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
>Reporter: Bernard
>Priority: Critical
> Attachments: JiraSeachExpression.PNG, messages.log
>
>
> java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags
> My IDE is frozen with  NetBeans using CPU on all 8 cores at 100%.
> The log is filled up with messages as below.
> On the screen, there is a dialog "Save (Not Responding)" where it asks to 
> confirm saving 2 Java files. I clicked "Save All" but this kept popping up 
> unresponsive after the IDE lost focus and then re-gained focus in a cycle 
> many times.
> I don't know what the primary issue is - the HIG CPU usage for perhaps 
> another reason or the errors in the log file. I cannot do anything at all 
> because JVisualVM cannot get a handle on NetBeans and waits forever computing 
> a description.
> Therefore, I would think that solving the ClassNotFoundException has the 
> higher priority. It fills up the logs and prevents discovery of other issues. 
> All 3 log files are full of that exception.
>  
> BTW Jira is too hard to use, I cannot search with it in a meaningful way. If 
> I search for anything, then I get results from other projects as well as 
> default which is stupid. The lack of an automatic duplicate search alone has 
> the potential to kill the entire project. Atlassian Jira is the wrong tool 
> for NetBeans. NetBeans needs bugzilla,
> INFO [com.sun.tools.javac.processing.JavacProcessingEnvironment]: Annotation 
> processing error:
> java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags
>     at java.lang.ClassLoader.findClass(ClassLoader.java:530)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>     at lombok.launch.ShadowClassLoader.loadClass(ShadowClassLoader.java:422)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>     at java.lang.Class.forName0(Native Method)
>     at java.lang.Class.forName(Class.java:264)
>     at 
> lombok.javac.JavacTreeMaker$SchroedingerType.getFieldCached(JavacTreeMaker.java:156)
>     at lombok.javac.JavacTreeMaker$TypeTag.typeTag(JavacTreeMaker.java:244)
>     at lombok.javac.Javac.(Javac.java:155)
> Caused: java.lang.ExceptionInInitializerError
>     at lombok.javac.handlers.HandleGetter.(HandleGetter.java:303)
>     at java.lang.Class.forName0(Native Method)
>     at java.lang.Class.forName(Class.java:348)
>     at lombok.core.SpiLoadUtil$1$1.next(SpiLoadUtil.java:111)
>     at 
> lombok.javac.HandlerLibrary.loadAnnotationHandlers(HandlerLibrary.java:171)
>     at lombok.javac.HandlerLibrary.load(HandlerLibrary.java:156)
>     at lombok.javac.JavacTransformer.(JavacTransformer.java:44)
>     at lombok.javac.apt.LombokProcessor.init(LombokProcessor.java:87)
>     at 
> lombok.core.AnnotationProcessor$JavacDescriptor.want(AnnotationProcessor.java:87)
>     at lombok.core.AnnotationProcessor.init(AnnotationProcessor.java:140)
>     at 
> lombok.launch.AnnotationProcessorHider$AnnotationProcessor.init(AnnotationProcessor.java:69)
> [catch] at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment$ProcessorState.(JavacProcessingEnvironment.java:683)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.next(JavacProcessingEnvironment.java:783)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:878)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.access$2300(JavacProcessingEnvironment.java:112)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1236)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1315)
>     at 
> com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1341)
>     at 
> com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1231)
>     at com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:397)
>     at com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:320)
>     at 
> org.netbeans.modules.java.source.parsing.JavacParser.moveToPhase(JavacParser.java:620)
>     at 
> 

[jira] [Created] (NETBEANS-2106) Illegal reflective access operation occurs while launching netbeans 10

2019-02-10 Thread M. Nejat AYDIN (JIRA)
M. Nejat AYDIN created NETBEANS-2106:


 Summary: Illegal reflective access operation occurs while 
launching netbeans 10
 Key: NETBEANS-2106
 URL: https://issues.apache.org/jira/browse/NETBEANS-2106
 Project: NetBeans
  Issue Type: Bug
  Components: core
Affects Versions: 10.0
 Environment: Product Version: Apache NetBeans IDE 10.0 (Build 
incubator-netbeans-release-380-on-20181217)
Java: 12-ea; OpenJDK 64-Bit Server VM 12-ea+30
Runtime: OpenJDK Runtime Environment 12-ea+30
System: Linux version 4.20.6-1-default running on amd64; UTF-8; en_US (nb)
User directory: /home/developer/.netbeans/10.0
Cache directory: /home/developer/.cache/netbeans/10.0
Reporter: M. Nejat AYDIN


The following message is put to stderr when launching the netbeans from 
terminal. IDE launches and runs without an issue.

WARNING: An illegal reflective access operation has occurred 
WARNING: Illegal reflective access by org.netbeans.core.windows.view.ui.MainWind
ow (jar:file:/home/developer/Apache-NetBeans-10.0/platform/modules/org-netbeans-
core-windows.jar!/) to field sun.awt.X11.XToolkit.awtAppClassName 
WARNING: Please consider reporting this to the maintainers of org.netbeans.core.
windows.view.ui.MainWindow 
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflect
ive access operations 
WARNING: All illegal access operations will be denied in a future release



--
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-2105) Tunnel Broker IPV6 then Ipv7

2019-02-10 Thread Victor Corral (JIRA)
Victor Corral created NETBEANS-2105:
---

 Summary: Tunnel Broker IPV6 then Ipv7
 Key: NETBEANS-2105
 URL: https://issues.apache.org/jira/browse/NETBEANS-2105
 Project: NetBeans
  Issue Type: Wish
 Environment: Red hat cygwin,msys2, Ubuntu, openSUSE,Mandriva,Fedora
Reporter: Victor Corral


I I'm trying 2 release the IPv6 to take out the ipv4 using my cellspot router 
and tunnel broker with Hurricane Electric I'm currently also signed up with 
icann trying to release my ipv7 using Dyne bolic and pure Dyne to respond to 
the rfc 0006. I started with trying to make Apache work with VMware along with 
hyper-v and I got to the point where I needed to download Windows 7 so that I 
can make the disc that I created to make this possible instead of downloading 
Windows 7 I ended up leaving that for a second go ahead of myself and I now 
have an account with Hurricane Electric in which I am taking classes so that I 
can change the ipv4 to a full IPv6 and I am trying to gain 99.99 percent 
interconnect partner with Google I am currently trying to finish the Android 
open source project by linking the Android open source to that distribution of 
dynebolic and to complete my Collective whole let me explain I am completing 
also or trying to complete the Hack Book at HOA-project.net as my collective 
whole and everything in HOA being my derivative works. To complete this I first 
am building my higher command line the detail in. Then creating a nest using 
dynebolic 2. There are 3 versions that I know of of dynebolic and also 3 
versions of puredyne. I am using God wins credential store to issue 
authentication to all devices and with kubernetes I will deploy my pods of 
using Google Dockers to deploy funky m iOS 1 click install on an iPhone using 
libimobile device. All of this along with my media lab that I create with the 
Xboxes to create netsukuku a p2p 100% decentralized and distributed network. 
The hardest part of all of this would be staying in compliance with all the 
licenses . you see I am building crosstool-ng but the issue with crosstool-Mr 
is to use it everything must be of the Linux kernel version 2 in order to use 
their patches. Also using AS as my cross Asemblers and cross links



--
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-2018) Gradle plugin error in development version on finish building

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi commented on NETBEANS-2018:
---

It seems something strange is happening during test execution. Meaning there is 
no current test suite when the the session is about to be closed.

If you could provide a minimal project with which this can be reproduced, then 
probably we can solve this issue. It might not necessarily in the Gradle 
support code.

> Gradle plugin error in development version on finish building
> -
>
> Key: NETBEANS-2018
> URL: https://issues.apache.org/jira/browse/NETBEANS-2018
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: Next
> Environment: Windows 8.1 x64
> OpenJDK 1.8.0_202 x64
> Netbeans dev #986
>Reporter: Oleg Schelykalnov
>Assignee: Laszlo Kishalmi
>Priority: Major
>  Labels: gradle
>
> When Gradle finished to build project I got error.
> IDE log from "View data" error window:
> {noformat}
>  INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: 
> Complete indexing of 3 source roots took: 1,220 ms (New or modified files: 0, 
> Deleted files: 0) [Adding listeners took: 0 ms]
>  SEVERE [global]
>  org.gradle.internal.event.ListenerNotificationException: Failed to notify 
> progress listener.
>  at 
> org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:48)
>  at 
> org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:230)
>  at 
> org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:149)
>  at 
> org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:140)
>  at 
> org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:37)
>  at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>  at com.sun.proxy.$Proxy56.statusChanged(Unknown Source)
>  at 
> org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.broadcastTestProgressEvent(BuildProgressListenerAdapter.java:107)
>  at 
> org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.doBroadcast(BuildProgressListenerAdapter.java:81)
>  at 
> org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.onEvent(BuildProgressListenerAdapter.java:72)
>  at 
> org.gradle.tooling.internal.consumer.parameters.FailsafeBuildProgressListenerAdapter.onEvent(FailsafeBuildProgressListenerAdapter.java:39)
>  at 
> org.gradle.tooling.internal.consumer.parameters.FailsafeBuildProgressListenerAdapter.onEvent(FailsafeBuildProgressListenerAdapter.java:39)
>  at 
> org.gradle.tooling.internal.provider.ProviderConnection$BuildProgressListenerInvokingBuildEventConsumer.dispatch(ProviderConnection.java:275)
>  at 
> org.gradle.launcher.daemon.client.DaemonClient.monitorBuild(DaemonClient.java:222)
>  at 
> org.gradle.launcher.daemon.client.DaemonClient.executeBuild(DaemonClient.java:179)
>  at 
> org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:142)
>  at 
> org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:93)
>  at 
> org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:60)
>  at 
> org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:41)
>  at 
> org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:59)
>  at 
> org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:38)
>  at 
> org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:180)
>  at 
> org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:124)
>  at 
> org.gradle.tooling.internal.provider.DefaultConnection.getModel(DefaultConnection.java:208)
>  at 
> org.gradle.tooling.internal.consumer.connection.CancellableModelBuilderBackedModelProducer.produceModel(CancellableModelBuilderBackedModelProducer.java:53)
>  at 
> org.gradle.tooling.internal.consumer.connection.PluginClasspathInjectionSupportedCheckModelProducer.produceModel(PluginClasspathInjectionSupportedCheckModelProducer.java:41)
>  at 
> org.gradle.tooling.internal.consumer.connection.AbstractConsumerConnection.run(AbstractConsumerConnection.java:59)
>  at 
> org.gradle.tooling.internal.consumer.connection.ParameterValidatingConsumerConnection.run(ParameterValidatingConsumerConnection.java:47)
>  at 
> 

[jira] [Assigned] (NETBEANS-2018) Gradle plugin error in development version on finish building

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi reassigned NETBEANS-2018:
-

Assignee: Laszlo Kishalmi

> Gradle plugin error in development version on finish building
> -
>
> Key: NETBEANS-2018
> URL: https://issues.apache.org/jira/browse/NETBEANS-2018
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Gradle
>Affects Versions: Next
> Environment: Windows 8.1 x64
> OpenJDK 1.8.0_202 x64
> Netbeans dev #986
>Reporter: Oleg Schelykalnov
>Assignee: Laszlo Kishalmi
>Priority: Major
>  Labels: gradle
>
> When Gradle finished to build project I got error.
> IDE log from "View data" error window:
> {noformat}
>  INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: 
> Complete indexing of 3 source roots took: 1,220 ms (New or modified files: 0, 
> Deleted files: 0) [Adding listeners took: 0 ms]
>  SEVERE [global]
>  org.gradle.internal.event.ListenerNotificationException: Failed to notify 
> progress listener.
>  at 
> org.gradle.internal.event.AbstractBroadcastDispatch.dispatch(AbstractBroadcastDispatch.java:48)
>  at 
> org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:230)
>  at 
> org.gradle.internal.event.BroadcastDispatch$SingletonDispatch.dispatch(BroadcastDispatch.java:149)
>  at 
> org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:140)
>  at 
> org.gradle.internal.event.ListenerBroadcast.dispatch(ListenerBroadcast.java:37)
>  at 
> org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
>  at com.sun.proxy.$Proxy56.statusChanged(Unknown Source)
>  at 
> org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.broadcastTestProgressEvent(BuildProgressListenerAdapter.java:107)
>  at 
> org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.doBroadcast(BuildProgressListenerAdapter.java:81)
>  at 
> org.gradle.tooling.internal.consumer.parameters.BuildProgressListenerAdapter.onEvent(BuildProgressListenerAdapter.java:72)
>  at 
> org.gradle.tooling.internal.consumer.parameters.FailsafeBuildProgressListenerAdapter.onEvent(FailsafeBuildProgressListenerAdapter.java:39)
>  at 
> org.gradle.tooling.internal.consumer.parameters.FailsafeBuildProgressListenerAdapter.onEvent(FailsafeBuildProgressListenerAdapter.java:39)
>  at 
> org.gradle.tooling.internal.provider.ProviderConnection$BuildProgressListenerInvokingBuildEventConsumer.dispatch(ProviderConnection.java:275)
>  at 
> org.gradle.launcher.daemon.client.DaemonClient.monitorBuild(DaemonClient.java:222)
>  at 
> org.gradle.launcher.daemon.client.DaemonClient.executeBuild(DaemonClient.java:179)
>  at 
> org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:142)
>  at 
> org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:93)
>  at 
> org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:60)
>  at 
> org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:41)
>  at 
> org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:59)
>  at 
> org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:38)
>  at 
> org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:180)
>  at 
> org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:124)
>  at 
> org.gradle.tooling.internal.provider.DefaultConnection.getModel(DefaultConnection.java:208)
>  at 
> org.gradle.tooling.internal.consumer.connection.CancellableModelBuilderBackedModelProducer.produceModel(CancellableModelBuilderBackedModelProducer.java:53)
>  at 
> org.gradle.tooling.internal.consumer.connection.PluginClasspathInjectionSupportedCheckModelProducer.produceModel(PluginClasspathInjectionSupportedCheckModelProducer.java:41)
>  at 
> org.gradle.tooling.internal.consumer.connection.AbstractConsumerConnection.run(AbstractConsumerConnection.java:59)
>  at 
> org.gradle.tooling.internal.consumer.connection.ParameterValidatingConsumerConnection.run(ParameterValidatingConsumerConnection.java:47)
>  at 
> org.gradle.tooling.internal.consumer.DefaultBuildLauncher$1.run(DefaultBuildLauncher.java:89)
>  at 
> org.gradle.tooling.internal.consumer.DefaultBuildLauncher$1.run(DefaultBuildLauncher.java:83)
>  at 
> org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:84)
>  at 
> 

[jira] [Updated] (NETBEANS-2048) java.util.concurrent.RejectedExecutionException: Endpoint is not open

2019-02-10 Thread Jennifer Zilar (JIRA)


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

Jennifer Zilar updated NETBEANS-2048:
-
Flagged: Impediment

> java.util.concurrent.RejectedExecutionException: Endpoint is not open
> -
>
> Key: NETBEANS-2048
> URL: https://issues.apache.org/jira/browse/NETBEANS-2048
> Project: NetBeans
>  Issue Type: Bug
>  Components: serverplugins - WildFly
>Affects Versions: 10.0
>Reporter: Jennifer Zilar
>Priority: Major
>  Labels: error, netbeans, wildfly
> Attachments: messages.log
>
>
> I was starting the Wildfly server on Netbeans 10.0 when I saw an error. The 
> log is attached.



--
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-1824) java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags

2019-02-10 Thread Eric Bresie (JIRA)


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

Eric Bresie updated NETBEANS-1824:
--
Attachment: JiraSeachExpression.PNG

> java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags
> ---
>
> Key: NETBEANS-1824
> URL: https://issues.apache.org/jira/browse/NETBEANS-1824
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
>Reporter: Bernard
>Priority: Critical
> Attachments: JiraSeachExpression.PNG, messages.log
>
>
> java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags
> My IDE is frozen with  NetBeans using CPU on all 8 cores at 100%.
> The log is filled up with messages as below.
> On the screen, there is a dialog "Save (Not Responding)" where it asks to 
> confirm saving 2 Java files. I clicked "Save All" but this kept popping up 
> unresponsive after the IDE lost focus and then re-gained focus in a cycle 
> many times.
> I don't know what the primary issue is - the HIG CPU usage for perhaps 
> another reason or the errors in the log file. I cannot do anything at all 
> because JVisualVM cannot get a handle on NetBeans and waits forever computing 
> a description.
> Therefore, I would think that solving the ClassNotFoundException has the 
> higher priority. It fills up the logs and prevents discovery of other issues. 
> All 3 log files are full of that exception.
>  
> BTW Jira is too hard to use, I cannot search with it in a meaningful way. If 
> I search for anything, then I get results from other projects as well as 
> default which is stupid. The lack of an automatic duplicate search alone has 
> the potential to kill the entire project. Atlassian Jira is the wrong tool 
> for NetBeans. NetBeans needs bugzilla,
> INFO [com.sun.tools.javac.processing.JavacProcessingEnvironment]: Annotation 
> processing error:
> java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags
>     at java.lang.ClassLoader.findClass(ClassLoader.java:530)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>     at lombok.launch.ShadowClassLoader.loadClass(ShadowClassLoader.java:422)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>     at java.lang.Class.forName0(Native Method)
>     at java.lang.Class.forName(Class.java:264)
>     at 
> lombok.javac.JavacTreeMaker$SchroedingerType.getFieldCached(JavacTreeMaker.java:156)
>     at lombok.javac.JavacTreeMaker$TypeTag.typeTag(JavacTreeMaker.java:244)
>     at lombok.javac.Javac.(Javac.java:155)
> Caused: java.lang.ExceptionInInitializerError
>     at lombok.javac.handlers.HandleGetter.(HandleGetter.java:303)
>     at java.lang.Class.forName0(Native Method)
>     at java.lang.Class.forName(Class.java:348)
>     at lombok.core.SpiLoadUtil$1$1.next(SpiLoadUtil.java:111)
>     at 
> lombok.javac.HandlerLibrary.loadAnnotationHandlers(HandlerLibrary.java:171)
>     at lombok.javac.HandlerLibrary.load(HandlerLibrary.java:156)
>     at lombok.javac.JavacTransformer.(JavacTransformer.java:44)
>     at lombok.javac.apt.LombokProcessor.init(LombokProcessor.java:87)
>     at 
> lombok.core.AnnotationProcessor$JavacDescriptor.want(AnnotationProcessor.java:87)
>     at lombok.core.AnnotationProcessor.init(AnnotationProcessor.java:140)
>     at 
> lombok.launch.AnnotationProcessorHider$AnnotationProcessor.init(AnnotationProcessor.java:69)
> [catch] at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment$ProcessorState.(JavacProcessingEnvironment.java:683)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.next(JavacProcessingEnvironment.java:783)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:878)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.access$2300(JavacProcessingEnvironment.java:112)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1236)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1315)
>     at 
> com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1341)
>     at 
> com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1231)
>     at com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:397)
>     at com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:320)
>     at 
> org.netbeans.modules.java.source.parsing.JavacParser.moveToPhase(JavacParser.java:620)
>     at 
> org.netbeans.modules.java.source.parsing.CompilationInfoImpl.toPhase(CompilationInfoImpl.java:361)
>     at 
> 

[jira] [Commented] (NETBEANS-1824) java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags

2019-02-10 Thread Eric Bresie (JIRA)


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

Eric Bresie commented on NETBEANS-1824:
---

Regarding Jira Usage...

Jira is not so hard to use once you get the hang of it...In the search box in 
the upper corner, you could search for a key word and then once an issue list 
shows up, you can modify the search to be more specific to what project.  So 
for example, the search expression can be "text ~ 
"com.sun.tools.javac.code.TypeTags" and project = NetBeans ".  See attached 
(not specific to the bug but is for Jira usage purposes)  

Keep in mind in the advances search string, there is "autocomplete" as you type 
so you can make complex search expressions.  

> java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags
> ---
>
> Key: NETBEANS-1824
> URL: https://issues.apache.org/jira/browse/NETBEANS-1824
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
>Reporter: Bernard
>Priority: Critical
> Attachments: messages.log
>
>
> java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags
> My IDE is frozen with  NetBeans using CPU on all 8 cores at 100%.
> The log is filled up with messages as below.
> On the screen, there is a dialog "Save (Not Responding)" where it asks to 
> confirm saving 2 Java files. I clicked "Save All" but this kept popping up 
> unresponsive after the IDE lost focus and then re-gained focus in a cycle 
> many times.
> I don't know what the primary issue is - the HIG CPU usage for perhaps 
> another reason or the errors in the log file. I cannot do anything at all 
> because JVisualVM cannot get a handle on NetBeans and waits forever computing 
> a description.
> Therefore, I would think that solving the ClassNotFoundException has the 
> higher priority. It fills up the logs and prevents discovery of other issues. 
> All 3 log files are full of that exception.
>  
> BTW Jira is too hard to use, I cannot search with it in a meaningful way. If 
> I search for anything, then I get results from other projects as well as 
> default which is stupid. The lack of an automatic duplicate search alone has 
> the potential to kill the entire project. Atlassian Jira is the wrong tool 
> for NetBeans. NetBeans needs bugzilla,
> INFO [com.sun.tools.javac.processing.JavacProcessingEnvironment]: Annotation 
> processing error:
> java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags
>     at java.lang.ClassLoader.findClass(ClassLoader.java:530)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>     at lombok.launch.ShadowClassLoader.loadClass(ShadowClassLoader.java:422)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>     at java.lang.Class.forName0(Native Method)
>     at java.lang.Class.forName(Class.java:264)
>     at 
> lombok.javac.JavacTreeMaker$SchroedingerType.getFieldCached(JavacTreeMaker.java:156)
>     at lombok.javac.JavacTreeMaker$TypeTag.typeTag(JavacTreeMaker.java:244)
>     at lombok.javac.Javac.(Javac.java:155)
> Caused: java.lang.ExceptionInInitializerError
>     at lombok.javac.handlers.HandleGetter.(HandleGetter.java:303)
>     at java.lang.Class.forName0(Native Method)
>     at java.lang.Class.forName(Class.java:348)
>     at lombok.core.SpiLoadUtil$1$1.next(SpiLoadUtil.java:111)
>     at 
> lombok.javac.HandlerLibrary.loadAnnotationHandlers(HandlerLibrary.java:171)
>     at lombok.javac.HandlerLibrary.load(HandlerLibrary.java:156)
>     at lombok.javac.JavacTransformer.(JavacTransformer.java:44)
>     at lombok.javac.apt.LombokProcessor.init(LombokProcessor.java:87)
>     at 
> lombok.core.AnnotationProcessor$JavacDescriptor.want(AnnotationProcessor.java:87)
>     at lombok.core.AnnotationProcessor.init(AnnotationProcessor.java:140)
>     at 
> lombok.launch.AnnotationProcessorHider$AnnotationProcessor.init(AnnotationProcessor.java:69)
> [catch] at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment$ProcessorState.(JavacProcessingEnvironment.java:683)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.next(JavacProcessingEnvironment.java:783)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:878)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.access$2300(JavacProcessingEnvironment.java:112)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1236)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1315)
>     at 
> 

[jira] [Commented] (NETBEANS-1118) Unable to Install Netbean

2019-02-10 Thread Eric Bresie (JIRA)


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

Eric Bresie commented on NETBEANS-1118:
---

Can you provide any additional details on this? 

Assume this could be an environment setup issue but it's hard to tell from just 
the title.  What version of java and netbeans are involved?

 Is this still an issue?  If not then maybe this one could be closed.

 

 

> Unable to Install Netbean
> -
>
> Key: NETBEANS-1118
> URL: https://issues.apache.org/jira/browse/NETBEANS-1118
> Project: NetBeans
>  Issue Type: Task
>  Components: platform - JDK Problems
>Affects Versions: Next
>Reporter: Bijoo Krishna Menon
>Priority: Major
>




--
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-1100) NetBeans 9.0 doesn't start with JDK 10.0.2 on Windows 10

2019-02-10 Thread Eric Bresie (JIRA)


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

Eric Bresie commented on NETBEANS-1100:
---

Just curious, is this maybe an environment setup issue?  In other words maybe 
JAVA_HOME or PATH needs to be set to find Java in some way?  With a shell or 
command prompt open, does java -version provide any valid java version details? 

Could this be a 32 vs 64 byte version of things (i.e. having one version of 
java and another of netbeans)?

> NetBeans 9.0 doesn't start with JDK 10.0.2 on Windows 10
> 
>
> Key: NETBEANS-1100
> URL: https://issues.apache.org/jira/browse/NETBEANS-1100
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - JDK Problems
>Affects Versions: 9.0
> Environment: MacOSX
> JDK 10.0.1
> Apache NetBeans 9.0 (released 29 July 2018)
>Reporter: John Kostaras
>Priority: Major
> Fix For: Next
>
>
> I recently installed JDK 10.0.2 on a Windows 10 machine that had no Java.
> I configured released NB 9.0 to run with this version in netbeans.conf.
> When I double clicked on netbeans64.exe nothing happens (I can only see the 
> splash screen and then nothing). No logs.
> JDK10 works fine in this machine.
>  



--
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-1359) Profiling the IDE hangs when saving snapshot

2019-02-10 Thread Eric Bresie (JIRA)


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

Eric Bresie commented on NETBEANS-1359:
---

This may be something to capture as a newer higher level umbrella item with 
linked sub-items where applicable but,

Based on some aspects of what I'm seeing here, am I correct in saying that 
portions of Netbeans may not be fully migrated to account for the 
"modularization" which comes with newer Java versions?  As part of this some 
previously available java internal api interfaces are no longer as available as 
they use to be which may result in some exceptions in different places.  

> Profiling the IDE hangs when saving snapshot
> 
>
> Key: NETBEANS-1359
> URL: https://issues.apache.org/jira/browse/NETBEANS-1359
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - JDK Problems
>Affects Versions: 10.0
>Reporter: Glenn Holmer
>Assignee: Glenn Holmer
>Priority: Blocker
>  Labels: netcat
> Fix For: 10.0
>
> Attachments: stacktrace.txt
>
>
> 1) Click "Profile the IDE" icon in the Performance toolbar to start profiling 
> the IDE.
> 2) Open some projects, files within them, etc. to create some activity for 
> the profiler.
> 3) Click the icon again (which is now labelled "Stop IDE Profiling and Take a 
> Snapshot").
> This last action should create and open a profiler snapshot, but the "Saving 
> snapshot" progress bar in the status area of NetBeans never goes anywhere and 
> a snapshot is not opened.
>  



--
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-1965) Export public & friend packages for Payara Plugin

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi updated NETBEANS-1965:
--
Labels: Export-Package Exported-Packages  (was: Export-Package 
Exported-Packages pull-request-available)

> Export public & friend packages for Payara Plugin
> -
>
> Key: NETBEANS-1965
> URL: https://issues.apache.org/jira/browse/NETBEANS-1965
> Project: NetBeans
>  Issue Type: Task
>Affects Versions: 10.0
>Reporter: Gaurav Gupta
>Assignee: Gaurav Gupta
>Priority: Minor
>  Labels: Export-Package, Exported-Packages
> Fix For: 11.0
>
>  Time Spent: 3h 10m
>  Remaining Estimate: 0h
>




--
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-2070) CLONE - UpgradeWindows Launchers

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi resolved NETBEANS-2070.
---
Resolution: Implemented

Result of cloning it's parent. It is actually no longer needed in NetBeans 11.0

> CLONE - UpgradeWindows Launchers
> 
>
> Key: NETBEANS-2070
> URL: https://issues.apache.org/jira/browse/NETBEANS-2070
> Project: NetBeans
>  Issue Type: Task
>  Components: platform - LaunchersCLI
>Reporter: Laszlo Kishalmi
>Priority: Major
>  Labels: Windows., pull-request-available
> Fix For: 10.0
>
>
> Dear Jan,
> I'd ask a favor to create and upload the Windows launchers for the 10.0 
> release as you did for 9.0. I'm afraid NETBEAN-1145 is not going to be put in 
> process for the 10.0 release.
> Thank you very much.



--
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-2070) CLONE - UpgradeWindows Launchers

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi updated NETBEANS-2070:
--
Issue Type: Task  (was: Sub-task)
Parent: (was: NETBEANS-2052)

> CLONE - UpgradeWindows Launchers
> 
>
> Key: NETBEANS-2070
> URL: https://issues.apache.org/jira/browse/NETBEANS-2070
> Project: NetBeans
>  Issue Type: Task
>  Components: platform - LaunchersCLI
>Reporter: Laszlo Kishalmi
>Priority: Major
>  Labels: Windows., pull-request-available
> Fix For: 10.0
>
>
> Dear Jan,
> I'd ask a favor to create and upload the Windows launchers for the 10.0 
> release as you did for 9.0. I'm afraid NETBEAN-1145 is not going to be put in 
> process for the 10.0 release.
> Thank you very much.



--
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-1848) Snapshot of APIs as of release 10.0

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi resolved NETBEANS-1848.
---
   Resolution: Fixed
Fix Version/s: 10.0

Marked resolved as the corresponding PR got merged.

> Snapshot of APIs as of release 10.0
> ---
>
> Key: NETBEANS-1848
> URL: https://issues.apache.org/jira/browse/NETBEANS-1848
> Project: NetBeans
>  Issue Type: Sub-task
>Reporter: Laszlo Kishalmi
>Assignee: Jaroslav Tulach
>Priority: Major
>  Labels: pull-request-available
> Fix For: 10.0
>
>
> Creating this issue as a note for PR-1064.
> $ git checkout 10.0
> $ ant clean; ant build
> $ ant gen-sigtests-release
> # I had to fix the nbbuild/build.xml a bit to make this work
> $ git stash
> $ git checkout master
> $ git pull
> $ git checkout -b SnapshotOfAPIsAsOfRelease100
> $ git stash pop
> $ git add .
> $ git commit -m "Snapshot of APIs as of 
> 910bd74bf46d079e49925f702432c74d54ec705c (tag: 10.0-vc5, tag: 10.0, 
> release100)"



--
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-1768) CodeCoverage doesn't work when custom outputDirectory is used in a PluginExecution

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi resolved NETBEANS-1768.
---
   Resolution: Fixed
Fix Version/s: 11.0

Marked resolved as the corresponding PR got merged.

> CodeCoverage doesn't work when custom outputDirectory is used in a 
> PluginExecution
> --
>
> Key: NETBEANS-1768
> URL: https://issues.apache.org/jira/browse/NETBEANS-1768
> Project: NetBeans
>  Issue Type: Bug
>  Components: maven - codecoverage
>Affects Versions: 10.0
>Reporter: John McDonnell
>Assignee: John McDonnell
>Priority: Major
>  Labels: pull-request-available
> Fix For: 11.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The Maven JaCoCo plugin support overriding the default directory location but 
> providing a outputDirectory configuration parameter on the plugin execution 
> properties.
>  
> At present NetBeans won't check the plugin executions to see if they override 
> output directory, and as a result the code coverage in the IDE wont work when 
> this happens.



--
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-1278) Schema2Bean doesn't support remote schemas and DTDs

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi commented on NETBEANS-1278:
---

This issue is stranding with a PR. It seems the PR shall not be merged. Shall 
we close this issue and the PR? Or there is anything new which could be 
revealed around this?

> Schema2Bean doesn't support remote schemas and DTDs
> ---
>
> Key: NETBEANS-1278
> URL: https://issues.apache.org/jira/browse/NETBEANS-1278
> Project: NetBeans
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 9.0
>Reporter: Emmanuel Hugonnet
>Assignee: Emmanuel Hugonnet
>Priority: Major
>  Labels: pull-request-available
> Fix For: Next
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Schema2Bean doesn't support remote XML schemas and DTDs.
> Adding that support would enable us to generate code without having to 
> 'integrate' those schemas in our code which is helpfull for J2EE /JavaEE 
> modules since they rely on those files while they are not under ASL



--
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-1035) Make HTML api public

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi updated NETBEANS-1035:
--
Labels:   (was: pull-request-available)

> Make HTML api public
> 
>
> Key: NETBEANS-1035
> URL: https://issues.apache.org/jira/browse/NETBEANS-1035
> Project: NetBeans
>  Issue Type: Wish
>  Components: web - HTML Editor
>Affects Versions: 8.2, 9.0
> Environment: Linux
>Reporter: Peter Nabbefeld
>Priority: Critical
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> There are already 21 "friends" using html.editor and html.editor.lib - IMHO a 
> good indicator it should be public.
>  
> However, I do need the API for implementing a Wicket module, so , if it will 
> take too long to make it public, probably make 
> org.netbeans.modules.web.wicket another friend of these modules and tell me 
> how to use it within a Maven based NetBeans module.



--
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



[incubator-netbeans] branch master updated: [NETBEANS-1768] Adding additional check for plugin executions if the JaCoCo outputDirectory is customised within an execution

2019-02-10 Thread lkishalmi
This is an automated email from the ASF dual-hosted git repository.

lkishalmi pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-netbeans.git


The following commit(s) were added to refs/heads/master by this push:
 new 6067b98  [NETBEANS-1768] Adding additional check for plugin executions 
if the JaCoCo outputDirectory is customised within an execution
6067b98 is described below

commit 6067b9860ed2b2047f4f0c85dcd215bd97e08efb
Author: John McDonnell 
AuthorDate: Sun Dec 2 19:27:48 2018 +

[NETBEANS-1768] Adding additional check for plugin executions if the JaCoCo 
outputDirectory is customised within an execution
---
 .../org/netbeans/modules/maven/coverage/MavenCoverageProvider.java   | 5 +
 1 file changed, 5 insertions(+)

diff --git 
a/java/maven.coverage/src/org/netbeans/modules/maven/coverage/MavenCoverageProvider.java
 
b/java/maven.coverage/src/org/netbeans/modules/maven/coverage/MavenCoverageProvider.java
index 5663591..6111409 100644
--- 
a/java/maven.coverage/src/org/netbeans/modules/maven/coverage/MavenCoverageProvider.java
+++ 
b/java/maven.coverage/src/org/netbeans/modules/maven/coverage/MavenCoverageProvider.java
@@ -135,6 +135,11 @@ public final class MavenCoverageProvider implements 
CoverageProvider {
 return null;
 }
 }
+File outputFile = FileUtil.normalizeFile(new 
File(outputDirectory));
+if (!outputFile.exists()) {
+// NETBEANS-1768 checking the plugin executions if the 
outputDirectory is customised
+outputDirectory = PluginPropertyUtils.getPluginProperty(p, 
GROUP_JOCOCO, ARTIFACT_JOCOCO, "outputDirectory", "report", null);
+}
 return FileUtil.normalizeFile(new File(outputDirectory, 
"jacoco.xml"));
 } else {
 String outputDirectory = 
PluginPropertyUtils.getReportPluginProperty(p, GROUP_COBERTURA, 
ARTIFACT_COBERTURA, "outputDirectory", null);


-
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-1478) Try to us javax.management API stead of sun.management.ThreadInfoCompositeData packages in self sampling

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi resolved NETBEANS-1478.
---
   Resolution: Fixed
Fix Version/s: 11.0

Marked resolved as the corresponding PR got merged.

> Try to us  javax.management API stead of 
> sun.management.ThreadInfoCompositeData packages in self sampling
> -
>
> Key: NETBEANS-1478
> URL: https://issues.apache.org/jira/browse/NETBEANS-1478
> Project: NetBeans
>  Issue Type: Improvement
>  Components: platform - Other
>Affects Versions: 10.0
>Reporter: Sven Reimers
>Assignee: Sven Reimers
>Priority: Major
>  Labels: pull-request-available
> Fix For: 11.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> As pointed out in NETBEANS-1359 self sampling should try to not use internal 
> sun.management but instead official java.management API.
> {code:java}
> private static final String[][] methods = new String[][]{
>   {"sun.management.ThreadInfoCompositeData", "toCompositeData"}, // NOI18N 
> Sun JVM
>   {"com.ibm.lang.management.ManagementUtils", "toThreadInfoCompositeData"} // 
> NOI18N IBM J9
> };{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] [Resolved] (NETBEANS-635) Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi resolved NETBEANS-635.
--
   Resolution: Fixed
Fix Version/s: 11.0

Marked resolved as the corresponding PR got merged.

> Surefire 2.19.1 (and later) stacktrace hyperlinks don't work with Maven
> ---
>
> Key: NETBEANS-635
> URL: https://issues.apache.org/jira/browse/NETBEANS-635
> Project: NetBeans
>  Issue Type: Bug
>  Components: projects - Maven
>Affects Versions: 8.2, 9.0
>Reporter: jmborer
>Priority: Major
>  Labels: pull-request-available
> Fix For: 11.0
>
> Attachments: mavenproject3.zip, surefire-2.18.1-.png, 
> surefire-2.18.1-logging-output.txt, surefire-2.18.1-output.txt, 
> surefire-2.19.1-.png, surefire-2.19.1-logging-output.txt, 
> surefire-2.19.1-output.txt, surefire-2.22.1-.png, 
> surefire-2.22.1-logging-output.txt, surefire-2.22.1-output.txt, 
> surefire-3.0.0-M3-logging-output.txt, surefire-3.0.0-M3-output.txt, 
> target-2.18.1.zip, target-2.19.1.zip, target-2.22.1.zip
>
>  Time Spent: 5.5h
>  Remaining Estimate: 0h
>
> When running tests with surefire 2.19.1, to see the stacktrace, make sure the 
> plugin is configured as following:
> {code:java}
> 
>     org.apache.maven.plugins
>     maven-surefire-plugin
>      2.19.1
>      
>          false
>      
>  {code}
> Then you will see the stacktraces in the output. Even though they are 
> recognized as being hyperlinks, when you click on them, nothing happens and 
> in the status bar of Netbeans it says that the source file cannot be found.
> This works perfectly with surefire 2.18.1. Something changed between these 
> versions.
> Related topics:
> [1] [https://netbeans.org/bugzilla/show_bug.cgi?id=257563]
> [2] [https://netbeans.org/bugzilla/show_bug.cgi?id=222587]
> [3] [https://netbeans.org/bugzilla/show_bug.cgi?id=262207]
>  
>  



--
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] [Closed] (NETBEANS-143) HTML/Java API shall contain NetBeans name

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi closed NETBEANS-143.

Resolution: Fixed

The PR has been integrated for a long time. Let's close this one.

> HTML/Java API shall contain NetBeans name
> -
>
> Key: NETBEANS-143
> URL: https://issues.apache.org/jira/browse/NETBEANS-143
> Project: NetBeans
>  Issue Type: Bug
>  Components: platform - HTML4J
>Reporter: Jaroslav Tulach
>Assignee: Jaroslav Tulach
>Priority: Trivial
>
> Bertrand wrote:
> On Wed, Nov 15, 2017 at 9:40 AM, Jaroslav Tulach
>  wrote:
> > ...People usually associate NetBeans with the image of an IDE. Or (at most)
> > with the image of general desktop application platform. However HTML/Java
> > API is different - it is heavily portable API that works everywrhere - it
> > is almost like "Cordova for Java"...
> From an Apache point of view it's important IMO that projects be
> associated with their (P)PMCs, so NetBeans in your case.
> I understand what you're saying about that module being fairly
> independent of the IDE - I suppose that can be expressed in the
> modules description.



--
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-1663) JUnit 5 run single test does not work for @ParameterizedTest, and go to source from test results doesn't work for these tests

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi resolved NETBEANS-1663.
---
   Resolution: Fixed
Fix Version/s: 11.0

Marked resolved as the corresponding PR got merged.

> JUnit 5 run single test does not work for @ParameterizedTest, and go to 
> source from test results doesn't work for these tests
> -
>
> Key: NETBEANS-1663
> URL: https://issues.apache.org/jira/browse/NETBEANS-1663
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - JUnit
>Affects Versions: 10.0
>Reporter: Stig Rohde Døssing
>Assignee: Stig Rohde Døssing
>Priority: Minor
>  Labels: pull-request-available
> Fix For: 11.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> In https://issues.apache.org/jira/browse/NETBEANS-6 some code was added that 
> decides whether a code is a JUnit 5 test or not, by whether its annotation 
> has {{@Testable}}
> as a "parent" (for lack of a better term). This is too conservative, 
> {{@Testable}} is a meta-annotation and can appear anywhere in the parent 
> hierarchy for test method annotations. For example, {{@ParameterizedTest}} 
> has {{@TestTemplate}} as a parent, which has {{@Testable}} as a parent.
> The code should be updated to look through the entire annotation hierarchy to 
> figure out if {{@Testable}} appears as a parent.
> Also when a {{@ParameterizedTest}} is run, and the test results window is 
> used to go to the test method, the IDE throws an exception. This happens 
> because the test name of a parameterized test is e.g. 
> "myMethod{myParamType}[0]", rather than just "myMethod". The lookup code 
> assumes that the test name will appear verbatim in the source.
> I think it makes sense to differentiate between the display name of a test 
> method, and the actual method name. Adjusting 
> org.netbeans.modules.gsf.testrunner.api.Testcase to allow this would let us 
> fix this issue, while also making it easier to implement support for e.g. 
> https://junit.org/junit5/docs/5.0.3/api/org/junit/jupiter/api/DisplayName.html
>  at a later date.



--
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-338) Find/Replace dialog does not render correctly

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi commented on NETBEANS-338:
--

Is this still happens on NetBeans 10.0 and Java 11?
Also are you using some custom LAF?

> Find/Replace dialog does not render correctly
> -
>
> Key: NETBEANS-338
> URL: https://issues.apache.org/jira/browse/NETBEANS-338
> Project: NetBeans
>  Issue Type: Bug
>  Components: editor - Search
> Environment: Product Version: Apache NetBeans IDE Dev (Build 
> 20180117-unknown-revn)
> Java: 9.0.4; Java HotSpot(TM) 64-Bit Server VM 9.0.4+11
> Runtime: Java(TM) SE Runtime Environment 9.0.4+11
> System: Windows 10 version 10.0 running on amd64; Cp1252; en_CA (nb)
> User directory: C:\Users\Gili\AppData\Roaming\NetBeans\dev
> Cache directory: C:\Users\Gili\AppData\Local\NetBeans\Cache\dev
>Reporter: Gili
>Priority: Trivial
>  Labels: Java9, Windows, regression
> Attachments: screenshot.png
>
>
> In the attached screenshot, notice that the horizontal separator between the 
> two combo-boxes is cut off. Expanding the combo-box causes the line to 
> render, but once it is collapsed again the line disappears. This used to work 
> in Netbeans 8.2 (though this was with JDK 8 while now I am using JDK 9)



--
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-1130) Netbeans Icon is "incorrect" in Windows Task Bar

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi resolved NETBEANS-1130.
---
   Resolution: Fixed
Fix Version/s: 10.0

Should work and in 10.0 we got new hi-res icons as well.

> Netbeans Icon is "incorrect" in Windows Task Bar
> 
>
> Key: NETBEANS-1130
> URL: https://issues.apache.org/jira/browse/NETBEANS-1130
> Project: NetBeans
>  Issue Type: Bug
>Affects Versions: 9.0
>Reporter: Paul Szudzik
>Priority: Trivial
>  Labels: easyfix, windows
> Fix For: 10.0, 9.0
>
> Attachments: Screenshot from 2018-08-26 17-26-04.png
>
>
> The new Netbeans Icon is not displayed on the Windows Taskbar when the 
> program runs.
> Under Linux, the new Icon shows up nicely on the active task bar.



--
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-1392) Clean is not performed before build

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi resolved NETBEANS-1392.
---
Resolution: Not A Bug

Clean and build and build are two different actions in NetBeans. Many depending 
actions use the simple build action which does not do the clean for the sake of 
speed.

> Clean is not performed before build
> ---
>
> Key: NETBEANS-1392
> URL: https://issues.apache.org/jira/browse/NETBEANS-1392
> Project: NetBeans
>  Issue Type: Bug
>Reporter: Rodrigo Teixeira Andreotti
>Priority: Trivial
> Attachments: CoS.PNG
>
>
> The clean is not performed as a part of the build (before compile) after 
> disable CoS.



--
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-2099) System.out.flush() doesn't flush all data to output window

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi commented on NETBEANS-2099:
---

What build System do you use for running this Application? Ant or Maven?

> System.out.flush() doesn't flush all data to output window
> --
>
> Key: NETBEANS-2099
> URL: https://issues.apache.org/jira/browse/NETBEANS-2099
> Project: NetBeans
>  Issue Type: Improvement
>  Components: platform - Output Window
>Affects Versions: 9.0, 10.0
> Environment: Product Version: Apache NetBeans IDE 10.0 (Build 
> incubator-netbeans-release-380-on-20181217)
> Java: 11.0.1; OpenJDK 64-Bit Server VM 11.0.1+13
> Runtime: OpenJDK Runtime Environment 11.0.1+13
> System: Windows 8.1 version 6.3 running on amd64; Cp1252; en_US (nb)
>Reporter: Stephan van Hulst
>Priority: Minor
>
> Consider the following application:
> {code:java}
> public static void main(String... args) {
>     System.out.print("Hello\nWorld!");
>     System.out.flush();
> }{code}
> After executing the first statement, the following line is printed to the 
> output window:
> {code}
> Hello
> {code}
> After executing the second statement, I expect the remainder of the printed 
> string to appear in the output window:
> {code}
> Hello
> World!
> {code}
> The flush does not appear to have any effect, however.
> When executing this program from the Windows command line, it works as 
> expected.
> Since the documentation of {{OutputStream.flush()}} mentions that the 
> behavior of flush is operating system dependent, this is not really a bug, 
> but it would be really nice if it flushed to the output window the same way 
> it flushes to the command line 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] [Assigned] (NETBEANS-2099) System.out.flush() doesn't flush all data to output window

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi reassigned NETBEANS-2099:
-

Assignee: Laszlo Kishalmi

> System.out.flush() doesn't flush all data to output window
> --
>
> Key: NETBEANS-2099
> URL: https://issues.apache.org/jira/browse/NETBEANS-2099
> Project: NetBeans
>  Issue Type: Improvement
>  Components: platform - Output Window
>Affects Versions: 9.0, 10.0
> Environment: Product Version: Apache NetBeans IDE 10.0 (Build 
> incubator-netbeans-release-380-on-20181217)
> Java: 11.0.1; OpenJDK 64-Bit Server VM 11.0.1+13
> Runtime: OpenJDK Runtime Environment 11.0.1+13
> System: Windows 8.1 version 6.3 running on amd64; Cp1252; en_US (nb)
>Reporter: Stephan van Hulst
>Assignee: Laszlo Kishalmi
>Priority: Minor
>
> Consider the following application:
> {code:java}
> public static void main(String... args) {
>     System.out.print("Hello\nWorld!");
>     System.out.flush();
> }{code}
> After executing the first statement, the following line is printed to the 
> output window:
> {code}
> Hello
> {code}
> After executing the second statement, I expect the remainder of the printed 
> string to appear in the output window:
> {code}
> Hello
> World!
> {code}
> The flush does not appear to have any effect, however.
> When executing this program from the Windows command line, it works as 
> expected.
> Since the documentation of {{OutputStream.flush()}} mentions that the 
> behavior of flush is operating system dependent, this is not really a bug, 
> but it would be really nice if it flushed to the output window the same way 
> it flushes to the command line 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-2039) Add run and debug action to Spring Boot Gradle projects

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi resolved NETBEANS-2039.
---
Resolution: Fixed

Resolved as the corresponding PR has been merged.

> Add run and debug action to Spring Boot Gradle projects
> ---
>
> Key: NETBEANS-2039
> URL: https://issues.apache.org/jira/browse/NETBEANS-2039
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Laszlo Kishalmi
>Assignee: Laszlo Kishalmi
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




--
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-2044) Store Gradle project actions in gradle.properties

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi resolved NETBEANS-2044.
---
   Resolution: Fixed
Fix Version/s: 11.0

Resolved as the corresponding PR has been merged.

> Store Gradle project actions in gradle.properties
> -
>
> Key: NETBEANS-2044
> URL: https://issues.apache.org/jira/browse/NETBEANS-2044
> Project: NetBeans
>  Issue Type: Improvement
>  Components: projects - Gradle
>Reporter: Laszlo Kishalmi
>Assignee: Laszlo Kishalmi
>Priority: Major
>  Labels: pull-request-available
> Fix For: 11.0
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Be less intrustive, do not leave custom nb-actions.xml in the project root, 
> "hide" customized actions in gradle.properties



--
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-2104) Gradle project shows description instead of name in Projects view

2019-02-10 Thread Laszlo Kishalmi (JIRA)


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

Laszlo Kishalmi resolved NETBEANS-2104.
---
Resolution: Not A Problem

Well it is intentionally used this way, many projects uses the description 
field to provide a kind of display name for their projects. Though this 
behavior can be turned off:
!image-2019-02-10-06-23-17-007.png!
by unclicking the Use Project Description as Project Name

> Gradle project shows description instead of name in Projects view
> -
>
> Key: NETBEANS-2104
> URL: https://issues.apache.org/jira/browse/NETBEANS-2104
> Project: NetBeans
>  Issue Type: Bug
>Reporter: Jose Pereda
>Assignee: Laszlo Kishalmi
>Priority: Major
> Attachments: gradle description issue.png
>
>
> If a Gradle project's build file contains a `description` property, the 
> description value is used instead of the project's name in the Projects view.
> !gradle description issue.png|width=240,height=178!
> I'm not sure if this is intentional, but I wouldn't expect it, as a 
> description can be very verbose. I'd rather use the root project's name, or 
> if it is not set, the name of the root folder. And maybe add the description 
> to the tooltip.
>  
>  



--
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-2104) Gradle project shows description instead of name in Projects view

2019-02-10 Thread Jose Pereda (JIRA)
Jose Pereda created NETBEANS-2104:
-

 Summary: Gradle project shows description instead of name in 
Projects view
 Key: NETBEANS-2104
 URL: https://issues.apache.org/jira/browse/NETBEANS-2104
 Project: NetBeans
  Issue Type: Bug
Reporter: Jose Pereda
Assignee: Laszlo Kishalmi
 Attachments: gradle description issue.png

If a Gradle project's build file contains a `description` property, the 
description value is used instead of the project's name in the Projects view.

!gradle description issue.png|width=240,height=178!

I'm not sure if this is intentional, but I wouldn't expect it, as a description 
can be very verbose. I'd rather use the root project's name, or if it is not 
set, the name of the root folder. And maybe add the description to the tooltip.

 

 



--
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-2103) WARNING: An illegal reflective access operation has occurred

2019-02-10 Thread Mingun (JIRA)
Mingun created NETBEANS-2103:


 Summary: WARNING: An illegal reflective access operation has 
occurred
 Key: NETBEANS-2103
 URL: https://issues.apache.org/jira/browse/NETBEANS-2103
 Project: NetBeans
  Issue Type: Bug
  Components: platform - Graph
Affects Versions: 9.0
 Environment: From NetBeans About:

Product Version: Apache NetBeans IDE 9.0 (Build 
incubator-netbeans-release-334-on-20180708)
Java: 10.0.2; Java HotSpot(TM) 64-Bit Server VM 10.0.2+13
Runtime: Java(TM) SE Runtime Environment 10.0.2+13
System: Windows 10 version 10.0 running on amd64; Cp1251; ru_RU (nb)
User directory: C:\Users\Mingun\AppData\Roaming\NetBeans\9.0
Cache directory: C:\Users\Mingun\AppData\Local\NetBeans\Cache\9.0
Reporter: Mingun


Steps to reproduce:
# Complete tutorial 
[https://platform.netbeans.org/tutorials/nbm-visual_library2.html] up to step 6
# Run application from IDE and try to collapse node
# See following in the *Output* window:
{noformat}
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
org.openide.util.RequestProcessor$TopLevelThreadGroup 
(file:/D:/Programs/netbeans9/platform/lib/org-openide-util.jar) to method 
sun.awt.AppContext.getAppContext()
WARNING: Please consider reporting this to the maintainers of 
org.openide.util.RequestProcessor$TopLevelThreadGroup
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
{noformat}



--
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-1824) java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags

2019-02-10 Thread Bernard (JIRA)


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

Bernard updated NETBEANS-1824:
--
Priority: Critical  (was: Major)

> java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags
> ---
>
> Key: NETBEANS-1824
> URL: https://issues.apache.org/jira/browse/NETBEANS-1824
> Project: NetBeans
>  Issue Type: Bug
>  Components: java - Editor
>Affects Versions: 9.0
>Reporter: Bernard
>Priority: Critical
> Attachments: messages.log
>
>
> java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags
> My IDE is frozen with  NetBeans using CPU on all 8 cores at 100%.
> The log is filled up with messages as below.
> On the screen, there is a dialog "Save (Not Responding)" where it asks to 
> confirm saving 2 Java files. I clicked "Save All" but this kept popping up 
> unresponsive after the IDE lost focus and then re-gained focus in a cycle 
> many times.
> I don't know what the primary issue is - the HIG CPU usage for perhaps 
> another reason or the errors in the log file. I cannot do anything at all 
> because JVisualVM cannot get a handle on NetBeans and waits forever computing 
> a description.
> Therefore, I would think that solving the ClassNotFoundException has the 
> higher priority. It fills up the logs and prevents discovery of other issues. 
> All 3 log files are full of that exception.
>  
> BTW Jira is too hard to use, I cannot search with it in a meaningful way. If 
> I search for anything, then I get results from other projects as well as 
> default which is stupid. The lack of an automatic duplicate search alone has 
> the potential to kill the entire project. Atlassian Jira is the wrong tool 
> for NetBeans. NetBeans needs bugzilla,
> INFO [com.sun.tools.javac.processing.JavacProcessingEnvironment]: Annotation 
> processing error:
> java.lang.ClassNotFoundException: com.sun.tools.javac.code.TypeTags
>     at java.lang.ClassLoader.findClass(ClassLoader.java:530)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>     at lombok.launch.ShadowClassLoader.loadClass(ShadowClassLoader.java:422)
>     at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>     at java.lang.Class.forName0(Native Method)
>     at java.lang.Class.forName(Class.java:264)
>     at 
> lombok.javac.JavacTreeMaker$SchroedingerType.getFieldCached(JavacTreeMaker.java:156)
>     at lombok.javac.JavacTreeMaker$TypeTag.typeTag(JavacTreeMaker.java:244)
>     at lombok.javac.Javac.(Javac.java:155)
> Caused: java.lang.ExceptionInInitializerError
>     at lombok.javac.handlers.HandleGetter.(HandleGetter.java:303)
>     at java.lang.Class.forName0(Native Method)
>     at java.lang.Class.forName(Class.java:348)
>     at lombok.core.SpiLoadUtil$1$1.next(SpiLoadUtil.java:111)
>     at 
> lombok.javac.HandlerLibrary.loadAnnotationHandlers(HandlerLibrary.java:171)
>     at lombok.javac.HandlerLibrary.load(HandlerLibrary.java:156)
>     at lombok.javac.JavacTransformer.(JavacTransformer.java:44)
>     at lombok.javac.apt.LombokProcessor.init(LombokProcessor.java:87)
>     at 
> lombok.core.AnnotationProcessor$JavacDescriptor.want(AnnotationProcessor.java:87)
>     at lombok.core.AnnotationProcessor.init(AnnotationProcessor.java:140)
>     at 
> lombok.launch.AnnotationProcessorHider$AnnotationProcessor.init(AnnotationProcessor.java:69)
> [catch] at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment$ProcessorState.(JavacProcessingEnvironment.java:683)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.next(JavacProcessingEnvironment.java:783)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:878)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.access$2300(JavacProcessingEnvironment.java:112)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1236)
>     at 
> com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1315)
>     at 
> com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1341)
>     at 
> com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1231)
>     at com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:397)
>     at com.sun.tools.javac.api.JavacTaskImpl.enter(JavacTaskImpl.java:320)
>     at 
> org.netbeans.modules.java.source.parsing.JavacParser.moveToPhase(JavacParser.java:620)
>     at 
> org.netbeans.modules.java.source.parsing.CompilationInfoImpl.toPhase(CompilationInfoImpl.java:361)
>     at 
> org.netbeans.api.java.source.CompilationController.toPhase(CompilationController.java:84)
>     at 
> 

[incubator-netbeans-website] branch asf-site updated: Automated site publishing by Jenkins build 591

2019-02-10 Thread git-site-role
This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-netbeans-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
 new 3e909a2  Automated site publishing by Jenkins build 591
3e909a2 is described below

commit 3e909a297bdc4db3df3f2d02eb162094cc612519
Author: jenkins 
AuthorDate: Sun Feb 10 10:28:01 2019 +

Automated site publishing by Jenkins build 591
---
 .../kb/docs/webclient/html5-gettingstarted.html| 295 +++--
 1 file changed, 214 insertions(+), 81 deletions(-)

diff --git a/content/kb/docs/webclient/html5-gettingstarted.html 
b/content/kb/docs/webclient/html5-gettingstarted.html
index ed2510c..58f42f1 100644
--- a/content/kb/docs/webclient/html5-gettingstarted.html
+++ b/content/kb/docs/webclient/html5-gettingstarted.html
@@ -216,9 +216,18 @@ The IDE will open the Chrome Web Store in the default 
browser. If Chrome is not
 Choose File  New Project to open the New Project wizard.
 
 
-Select HTML5/JS Application in the 
HTML/JavaScript category. Click Next.
-image::images/html5-newproject1.png[title="HTML5 Application template in the 
New Project wizard"]
+Select HTML5/JS Application in the 
HTML/JavaScript category. Click Next.
 
+
+
+
+
+
+
+Figure 1. HTML5 Application template in the New Project 
wizard
+
+
+
 
 Specify a Name and Location for the project. Click Next.
 
@@ -228,7 +237,7 @@ image::images/html5-newproject1.png[title="HTML5 
Application template in the New
 For this exercise the name is not important.
 
 
-
+
 
 Select No Site Template. Click Finish.
 
@@ -238,7 +247,7 @@ image::images/html5-newproject1.png[title="HTML5 
Application template in the New
 When you click Finish the IDE creates a new HTML5 project and opens  
index.html  in the editor.
 
 
-
+
 
 Confirm that Chrome with NetBeans Integration is selected in the dropdown 
list in the toolbar.
 
@@ -246,31 +255,41 @@ image::images/html5-newproject1.png[title="HTML5 
Application template in the New
 Click Run in the toolbar.
 
 
-Click Go to Chrome Web Store in the Install Chrome Extension dialog box.
-image::images/html5-offline-extension1.png[title="Install Chrome Extension 
dialog box"]
+Click Go to Chrome Web Store in the Install Chrome Extension dialog box.
 
 
 
+
+
+
+
+Figure 2. Install Chrome Extension dialog box
+
 
 When you click Go to Chrome Web Store the NetBeans Connector page in the 
Chrome Web Store opens in the Chrome browser.
 
 
-Note. The Install Chrome Extension displays a button that 
you will click after the extension is installed.
+Note: The Install Chrome Extension displays a button that you will click 
after the extension is installed.
 
 
 
 
 
-Figure 1. Install Chrome Extension dialog box
+Figure 3. Install Chrome Extension dialog box
 
 
-
+
 
-Go to the Chrome browser and click Add to Chrome in the NetBeans Connector 
page. Click Add when you are prompted to confirm that you want to add the 
extension.
-image::images/html5-chrome-netbeanshome.png[title="NetBeans Connector page in 
the Chrome Web Store"]
+Go to the Chrome browser and click Add to Chrome in the NetBeans Connector 
page. Click Add when you are prompted to confirm that you want to add the 
extension.
 
 
 
+
+
+
+
+Figure 4. NetBeans Connector page in the Chrome Web 
Store
+
 
 When the extension is installed you will see a notification that the 
extension was added and that the NetBeans Connector icon will be visible in the 
URL location bar when you run a NetBeans HTML5 project in the Chrome 
browser.
 
@@ -278,10 +297,10 @@ 
image::images/html5-chrome-netbeanshome.png[title="NetBeans Connector page in th
 
 
 
-Figure 2. Confirmation in that extension was installed
+Figure 5. Confirmation in that extension was installed
 
 
-
+
 
 In the IDE, Click Re-Run Project in the Install Chrome Extension dialog 
box.
 
@@ -300,7 +319,7 @@ image::images/html5-chrome-netbeanshome.png[title="NetBeans 
Connector page in th
 
 
 
-Figure 3. NetBeans Connector extension is enabled in Chrome 
Extensions
+Figure 6. NetBeans Connector extension is enabled in Chrome 
Extensions
 
 
 
@@ -323,11 +342,16 @@ Alternatively, you can install the NetBeans Connector 
extension directly from th
 Search the Chrome Web Store for the Netbeans Connector extension.
 
 
-Click Add To Chrome in the search results page and click Add when you are 
prompted to add the extension.
-image::images/html5-install-extension1.png[title="NetBeans Connector extension 
in Chrome Web Store"]
+Click Add To Chrome in the search results page and click Add when you are 
prompted to add the extension.
 
 
 
+
+
+
+
+Figure 7. NetBeans Connector extension in Chrome Web 
Store
+
 
 
 Offline Installation of the 
Extension
@@ -337,17 +361,44 @@ 
image::images/html5-install-extension1.png[title="NetBeans Connector extension i
 
 
 
-Click Not Connected in the Install Chrome Extension dialog box.

[incubator-netbeans-website] branch master updated: Updated html5-getting started

2019-02-10 Thread vieiro
This is an automated email from the ASF dual-hosted git repository.

vieiro pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-netbeans-website.git


The following commit(s) were added to refs/heads/master by this push:
 new 1d3e21f  Updated html5-getting started
1d3e21f is described below

commit 1d3e21f6065098129d6f8ba242a905c7620af9d8
Author: Antonio Vieiro 
AuthorDate: Sun Feb 10 11:25:09 2019 +0100

Updated html5-getting started
---
 .../docs/webclient/html5-gettingstarted.asciidoc   | 86 +++---
 1 file changed, 77 insertions(+), 9 deletions(-)

diff --git 
a/netbeans.apache.org/src/content/kb/docs/webclient/html5-gettingstarted.asciidoc
 
b/netbeans.apache.org/src/content/kb/docs/webclient/html5-gettingstarted.asciidoc
index a5725b4..a0b011a 100644
--- 
a/netbeans.apache.org/src/content/kb/docs/webclient/html5-gettingstarted.asciidoc
+++ 
b/netbeans.apache.org/src/content/kb/docs/webclient/html5-gettingstarted.asciidoc
@@ -67,31 +67,42 @@ NOTE: The IDE will open the Chrome Web Store in the default 
browser. If Chrome i
 
 1. Choose File > New Project to open the New Project wizard.
 2. Select *HTML5/JS Application* in the *HTML/JavaScript* category. Click Next.
+
 image::images/html5-newproject1.png[title="HTML5 Application template in the 
New Project wizard"]
+
+[start=3]
 3. Specify a Name and Location for the project. Click Next.
 
 For this exercise the name is not important.
 
+[start=4]
 4. Select No Site Template. Click Finish.
 
 When you click Finish the IDE creates a new HTML5 project and opens  
``index.html``  in the editor.
 
+[start=5]
 5. Confirm that Chrome with NetBeans Integration is selected in the dropdown 
list in the toolbar.
 6. Click Run in the toolbar.
 7. Click Go to Chrome Web Store in the Install Chrome Extension dialog box.
+
 image::images/html5-offline-extension1.png[title="Install Chrome Extension 
dialog box"]
 
 When you click Go to Chrome Web Store the NetBeans Connector page in the 
Chrome Web Store opens in the Chrome browser.
 
-*Note.* The Install Chrome Extension displays a button that you will click 
after the extension is installed.
+Note: The Install Chrome Extension displays a button that you will click after 
the extension is installed.
 
 image::images/html5-rerun-dialog.png[title="Install Chrome Extension dialog 
box"]
+
+[start=8]
 8. Go to the Chrome browser and click Add to Chrome in the NetBeans Connector 
page. Click Add when you are prompted to confirm that you want to add the 
extension.
+
 image::images/html5-chrome-netbeanshome.png[title="NetBeans Connector page in 
the Chrome Web Store"]
 
 When the extension is installed you will see a notification that the extension 
was added and that the NetBeans Connector icon will be visible in the URL 
location bar when you run a NetBeans HTML5 project in the Chrome browser.
 
 image::images/html5-install-extension2.png[title="Confirmation in that 
extension was installed"]
+
+[start=9]
 9. In the IDE, Click Re-Run Project in the Install Chrome Extension dialog box.
 
 When you click Re-Run Project a new tab will open in the Chrome browser and 
you will see the index page of the HTML5 application.
@@ -107,6 +118,7 @@ NOTE: Alternatively, you can install the NetBeans Connector 
extension directly f
 1. Start the Chrome browser and go to the 
link:https://chrome.google.com/webstore/[+Chrome Web Store+].
 2. Search the Chrome Web Store for the Netbeans Connector extension.
 3. Click Add To Chrome in the search results page and click Add when you are 
prompted to add the extension. 
+
 image::images/html5-install-extension1.png[title="NetBeans Connector extension 
in Chrome Web Store"]
 
 === Offline Installation of the Extension
@@ -114,15 +126,25 @@ 
image::images/html5-install-extension1.png[title="NetBeans Connector extension i
 If you are unable to connect to the Chrome Web Store you can install the 
NetBeans Connector extension that is bundled with the IDE. If you run a 
NetBeans HTML5 project and you are prompted to install the NetBeans Connector 
extension, you can perform the following steps to install the extension if you 
are not able to access the Chrome Web Store.
 
 1. Click Not Connected in the Install Chrome Extension dialog box.
+
 image::images/html5-offline-extension1.png[title="Install Chrome extension 
dialog box"]
+
+[start=2]
 2. Click *locate* in the dialog box to open the NetBeans IDE installation 
folder on your local system that contains the * 
``netbeans-chrome-connector.crx`` * extension.
+
 image::images/html5-offline-extension2.png[title="NetBeans Connector extension 
is enabled in Chrome Extensions"]
+
+[start=3]
 3. Open the Chrome extensions page ( ``chrome://extensions/`` ) in your Chrome 
browser.
+
 image::images/html5-offline-extension3.png[title="NetBeans Connector extension 
is enabled in Chrome Extensions"]
+
+[start=4]
 4. Drag the  ``netbeans-chrome-connector.crx``  extension into the Extensions 

[incubator-netbeans-website] branch asf-site updated: Automated site publishing by Jenkins build 589

2019-02-10 Thread git-site-role
This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-netbeans-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
 new e2d7e0c  Automated site publishing by Jenkins build 589
e2d7e0c is described below

commit e2d7e0c7af662372032d0632bf360cd950343f43
Author: jenkins 
AuthorDate: Sun Feb 10 10:15:46 2019 +

Automated site publishing by Jenkins build 589
---
 .../docs/php/configure-php-environment-mac-os.html | 164 +--
 .../docs/php/configure-php-environment-ubuntu.html | 141 +
 .../php/configure-php-environment-windows.html | 165 ++--
 content/kb/docs/php/index.html |   4 +-
 content/kb/docs/php/project-setup.html | 173 -
 content/kb/docs/php/quickstart.html|  77 ++---
 6 files changed, 493 insertions(+), 231 deletions(-)

diff --git a/content/kb/docs/php/configure-php-environment-mac-os.html 
b/content/kb/docs/php/configure-php-environment-mac-os.html
index 0be106c..251375c 100644
--- a/content/kb/docs/php/configure-php-environment-mac-os.html
+++ b/content/kb/docs/php/configure-php-environment-mac-os.html
@@ -81,16 +81,8 @@
 Configuring PHP, Apache, MySQL, and Xdebug for 
PHP development in MAC OS X
 
 
-  
-
-  
-  
-  This tutorial needs a review. 
- You can https://issues.apache.org/jira/projects/NETBEANS/issues;>open a JIRA 
issue, 
- or https://github.com/apache/incubator-netbeans-website/blob/master/netbeans.apache.org/src/content/kb/docs/php/configure-php-environment-mac-os.asciidoc;
 title="Edit this tutorial in github">edit it in GitHub 
- following these contribution guidelines.
-  
-
+  
+ Last 
reviewed on 2019-02-02
   
 
 
@@ -107,7 +99,7 @@
 
 
 
-This tutorial shows you how to set up PHP on the http://www.mamp.info/en/index.php;>MAMP (M*acintosh, 
A*pache, *M*ySQL, *P*HP) package, which includes the Apache web server, the 
MySQL database server, and the PHP engine. MAMP is intended as a PHP 
development environment for the Mac, which can work seamlessly with the 
NetBeans IDE.
+This tutorial shows you how to set up PHP on the http://www.mamp.info/en/index.php;>MAMP (Macintosh, Apache, MySQL, 
PHP) package, which includes the Apache web server, the MySQL database server, 
and the PHP engine. MAMP is intended as a PHP development environment for the 
Mac, which can work seamlessly with the NetBeans IDE.
 
 
 http://www.Xdebug.org/;>Xdebug is an extension for PHP that 
aids in providing information valuable for debugging PHP scripts. The NetBeans 
debugger works on top of the Xdebug extension, providing an effective debugging 
tool in your development environment.
@@ -157,20 +149,46 @@ The MAMP package includes the Apache web server, PHP 
engine, and MySQL database.
 Download the latest version of http://www.mamp.info/en/download.html;>MAMP.
 
 
-Extract the downloaded file and run the .dmg file. When the 
installer displays, drag MAMP into your /Applications folder.
-image::images/mamp-install.png[title="MAMP installer panel showing MAMP and 
MAMP-Pro options"]
+Extract the downloaded file and run the .dmg file. When the 
installer displays, drag MAMP into your /Applications folder.
 
+
+
+
+
+
+
+Figure 1. MAMP installer panel showing MAMP and MAMP-Pro 
options
+
+
+
 
 Navigate to /Applications/MAMP and double-click 
MAMP.app. The MAMP Control Panel opens.
 
 
 
 
-You can also install the MAMP Control dashboard widget as described in 
MAMP/README.rtf, which enables you to start and stop servers.
-image::images/mamp-control-panel.png[]
-4. Click Preferences to open the Preferences panel, then select the Ports tab.
-5. Click Set to Default Apache and MySQL ports. Apache port is reset to 80 and 
MySQL to 3306.
-image::images/mamp-control-panel-preferences-ports.png[title="MAMP control 
panel with Ports tab, after ports have been changed to default values"]
+You can also install the MAMP Control dashboard widget as described in 
MAMP/README.rtf, which enables you to start and stop servers.
+
+
+
+
+
+
+
+
+
+Click Preferences to open the Preferences panel, then select the Ports 
tab.
+
+
+Click Set to Default Apache and MySQL ports. Apache port is reset to 80 and 
MySQL to 3306.
+
+
+
+
+
+
+
+Figure 2. MAMP control panel with Ports tab, after ports 
have been changed to default values
 
 
 
@@ -202,12 +220,21 @@ 
image::images/mamp-control-panel-preferences-ports.png[title="MAMP control panel
 *Administrator User Name: *root
 
 
-*Administrator Password: *root
-image::images/mysql-basic-properties.png[title="MySQL Basic Properties dialog 

[incubator-netbeans-website] branch master updated: [NETBEANS-1867] Some PHP tutorials (#315)

2019-02-10 Thread vieiro
This is an automated email from the ASF dual-hosted git repository.

vieiro pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-netbeans-website.git


The following commit(s) were added to refs/heads/master by this push:
 new 88ed888  [NETBEANS-1867] Some PHP tutorials (#315)
88ed888 is described below

commit 88edee9abe2a3c60e3e4df068699c491cd77
Author: Antonio Vieiro 
AuthorDate: Sun Feb 10 11:13:20 2019 +0100

[NETBEANS-1867] Some PHP tutorials (#315)
---
 .../php/configure-php-environment-mac-os.asciidoc  | 41 ++--
 .../php/configure-php-environment-ubuntu.asciidoc  | 77 +-
 .../php/configure-php-environment-windows.asciidoc | 53 ++-
 .../src/content/kb/docs/php/index.asciidoc |  1 +
 .../src/content/kb/docs/php/project-setup.asciidoc | 48 --
 .../src/content/kb/docs/php/quickstart.asciidoc| 24 +--
 6 files changed, 181 insertions(+), 63 deletions(-)

diff --git 
a/netbeans.apache.org/src/content/kb/docs/php/configure-php-environment-mac-os.asciidoc
 
b/netbeans.apache.org/src/content/kb/docs/php/configure-php-environment-mac-os.asciidoc
index fbea25c..ca5145b 100644
--- 
a/netbeans.apache.org/src/content/kb/docs/php/configure-php-environment-mac-os.asciidoc
+++ 
b/netbeans.apache.org/src/content/kb/docs/php/configure-php-environment-mac-os.asciidoc
@@ -28,8 +28,9 @@
 :toc-title:
 :description: Configuring PHP, Apache, MySQL, and Xdebug for PHP development 
in MAC OS X - Apache NetBeans
 :keywords: Apache NetBeans, Tutorials, Configuring PHP, Apache, MySQL, and 
Xdebug for PHP development in MAC OS X
+:reviewed: 2019-02-02
 
-This tutorial shows you how to set up PHP on the 
link:http://www.mamp.info/en/index.php[+MAMP+] (*M*acintosh,* A*pache, *M*ySQL, 
*P*HP) package, which includes the Apache web server, the MySQL database 
server, and the PHP engine. MAMP is intended as a PHP development environment 
for the Mac, which can work seamlessly with the NetBeans IDE.
+This tutorial shows you how to set up PHP on the 
link:http://www.mamp.info/en/index.php[+MAMP+] (Macintosh, Apache, MySQL, PHP) 
package, which includes the Apache web server, the MySQL database server, and 
the PHP engine. MAMP is intended as a PHP development environment for the Mac, 
which can work seamlessly with the NetBeans IDE.
 
 link:http://www.Xdebug.org/[+Xdebug+] is an extension for PHP that aids in 
providing information valuable for debugging PHP scripts. The NetBeans debugger 
works on top of the Xdebug extension, providing an effective debugging tool in 
your development environment.
 
@@ -47,13 +48,20 @@ NOTE: The MAMP package includes the Apache web server, PHP 
engine, and MySQL dat
 
 1. Download the latest version of 
link:http://www.mamp.info/en/download.html[+MAMP+].
 2. Extract the downloaded file and run the `.dmg` file. When the installer 
displays, drag MAMP into your `/Applications` folder. 
+
 image::images/mamp-install.png[title="MAMP installer panel showing MAMP and 
MAMP-Pro options"]
+
+[start=3]
 3. Navigate to `/Applications/MAMP` and double-click `MAMP.app`. The MAMP 
Control Panel opens. 
 
 You can also install the MAMP Control dashboard widget as described in 
`MAMP/README.rtf`, which enables you to start and stop servers. 
+
 image::images/mamp-control-panel.png[]
+
+[start=4]
 4. Click Preferences to open the Preferences panel, then select the Ports tab.
 5. Click Set to Default Apache and MySQL ports. Apache port is reset to 80 and 
MySQL to 3306. 
+
 image::images/mamp-control-panel-preferences-ports.png[title="MAMP control 
panel with Ports tab, after ports have been changed to default values"]
 
 == Registering MAMP's MySQL Database
@@ -69,16 +77,26 @@ The IDE interfaces with databases from the Services window 
(⌘-5). You can regi
 * *Server Port Number: *`3306`
 * *Administrator User Name: *`root`
 * *Administrator Password: *`root`
+
 image::images/mysql-basic-properties.png[title="MySQL Basic Properties dialog 
containing MAMP's default connectivity settings"]
+
+[start=3]
 3. Select the Admin Properties tab to display settings that enable you to 
start and stop the database server from the IDE. MAMP maintains shell scripts 
in its `bin` folder. You can find scripts for starting and stopping servers 
there. For the path to the Admin tool, you have a choice; you can link to 
`MAMP.app` so that you can use the IDE to open MAMP's control panel. To do so, 
enter `/Applications/MAMP/MAMP.app`. However, an alternative option would be to 
use the link:http://dev.mysql.c [...]
 
 * *Path/URL to admin tool: *`/Applications/MySQL Tools/MySQLWorkbench.app` 
_(default installation for MySQL Workbench)_
 * *Path to start command: *`/Applications/MAMP/bin/startMysql.sh`
 * *Path to stop command: *`/Applications/MAMP/bin/stopMysql.sh`
+
 image::images/mysql-admin-props.png[title="MySQL Admin Properties dialog 
containing sample administration settings"]
+
+[start=4]
 4. If you choose to