[jira] [Updated] (NETBEANS-2976) EE Deployment module not working with git-commit-id-plugin and finalName
[
https://issues.apache.org/jira/browse/NETBEANS-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John updated NETBEANS-2976:
---
Affects Version/s: 12.1
16
17
19
> EE Deployment module not working with git-commit-id-plugin and finalName
>
>
> Key: NETBEANS-2976
> URL: https://issues.apache.org/jira/browse/NETBEANS-2976
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 11.1, 12.1, 16, 17, 19
> Environment: Ubuntu Linux 19.04, Netbeans 11.1, Oracle JDK 1.8.0_201
>Reporter: John
>Priority: Minor
>
> I have nested maven projects that uses plugin
> `pl.project13.maven:git-commit-id-plugin` in the parent pom, and a child
> project overriding it's artifact name in it's pom. When the `finalName`
> setting in the child project contains properties created by the plugin, the
> NB deployment module can't find the packaged ear for test deployment.
>
> Here is the parent pom.xml:
>
> {code:java}
>
> pl.project13.maven
> git-commit-id-plugin
> 2.2.6
>
>
> get-the-git-infos
>
>revision
>
> initialize
>
>
> validate-the-git-infos
>
>validateRevision
>
> package
>
>
>
> ${project.basedir}/.git
> git
> MMdd'T'HHmm
> false
> false
> false
> false
> true
> true
> false
> false false
> true
> true
>
> ^git.commit.id.abbrev$
> ^git.commit.time$
> ^git.build.version$
> ^git.branch$
>
>
> {code}
>
>
> Here is the child pom.xml:
>
> {code:java}
>
>
> ${project.artifactId}${project.version}${git.branch}${git.commit.time}${git.commit.id.abbrev}
> {code}
>
> {{And IDE.log:}}
> {code:java}
> INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment]
> org.netbeans.modules.j2ee.deployment.impl.TargetServer$NoArchiveException: No
> archive for deployment
> at
> org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:675)
> [catch] at
> org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:221)
> at
> org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:185)
> at
> org.netbeans.modules.maven.j2ee.execution.CoSAlternativeExecutorImpl.execute(CoSAlternativeExecutorImpl.java:67)
> at
> org.netbeans.modules.maven.cos.CoSAlternativeExecutor.execute(CoSAlternativeExecutor.java:64)
> at
> org.netbeans.modules.maven.cos.CosChecker.checkRunMainClass(CosChecker.java:186)
> at
> org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(CosChecker.java:140)
> at
> org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:213)
> at
> org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:128){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
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-2976) EE Deployment module not working with git-commit-id-plugin and finalName
[
https://issues.apache.org/jira/browse/NETBEANS-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17730994#comment-17730994
]
John commented on NETBEANS-2976:
Still an issue with Netbeans 18.
> EE Deployment module not working with git-commit-id-plugin and finalName
>
>
> Key: NETBEANS-2976
> URL: https://issues.apache.org/jira/browse/NETBEANS-2976
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 11.1
> Environment: Ubuntu Linux 19.04, Netbeans 11.1, Oracle JDK 1.8.0_201
>Reporter: John
>Priority: Minor
>
> I have nested maven projects that uses plugin
> `pl.project13.maven:git-commit-id-plugin` in the parent pom, and a child
> project overriding it's artifact name in it's pom. When the `finalName`
> setting in the child project contains properties created by the plugin, the
> NB deployment module can't find the packaged ear for test deployment.
>
> Here is the parent pom.xml:
>
> {code:java}
>
> pl.project13.maven
> git-commit-id-plugin
> 2.2.6
>
>
> get-the-git-infos
>
>revision
>
> initialize
>
>
> validate-the-git-infos
>
>validateRevision
>
> package
>
>
>
> ${project.basedir}/.git
> git
> MMdd'T'HHmm
> false
> false
> false
> false
> true
> true
> false
> false false
> true
> true
>
> ^git.commit.id.abbrev$
> ^git.commit.time$
> ^git.build.version$
> ^git.branch$
>
>
> {code}
>
>
> Here is the child pom.xml:
>
> {code:java}
>
>
> ${project.artifactId}${project.version}${git.branch}${git.commit.time}${git.commit.id.abbrev}
> {code}
>
> {{And IDE.log:}}
> {code:java}
> INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment]
> org.netbeans.modules.j2ee.deployment.impl.TargetServer$NoArchiveException: No
> archive for deployment
> at
> org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:675)
> [catch] at
> org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:221)
> at
> org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:185)
> at
> org.netbeans.modules.maven.j2ee.execution.CoSAlternativeExecutorImpl.execute(CoSAlternativeExecutorImpl.java:67)
> at
> org.netbeans.modules.maven.cos.CoSAlternativeExecutor.execute(CoSAlternativeExecutor.java:64)
> at
> org.netbeans.modules.maven.cos.CosChecker.checkRunMainClass(CosChecker.java:186)
> at
> org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(CosChecker.java:140)
> at
> org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:213)
> at
> org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:128){code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
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-3273) Cannot run Payara 5 under JDK 8
[ https://issues.apache.org/jira/browse/NETBEANS-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John updated NETBEANS-3273: --- Affects Version/s: 12.6 > Cannot run Payara 5 under JDK 8 > --- > > Key: NETBEANS-3273 > URL: https://issues.apache.org/jira/browse/NETBEANS-3273 > Project: NetBeans > Issue Type: Bug > Components: serverplugins - GlassFish >Affects Versions: 11.1, 11.2, 12.4, 12.6 >Reporter: Stephen Parry >Priority: Major > > On Linux (not sure about other platforms), running Payara using JDK 8 gives > the following error on Services -> server -> Payara -> start: > Unrecognized option: --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > Steps to reproduce: > # Ensure host system has JDK 11 (as default) and JDK 8 installed > # Clean install NB 11.1 or 11.2 with JDK 11 as chosen JVM and activate all > modules > # Use platform manager to add JDK 8 as new platform. > # Add a Payara 5.192 or 5.193 server > # Services -> Server -> Payara Server -> Properties -> Java -> Java Platform: > JDK 8 -> Close > # Services -> Server -> Payara Server -> Start > Expected behaviour: > Successful startup messages in Payara Server console > Actual behaviour: > Failure messages in Payara Server console: > Unrecognized option: --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > This is a known issue in the original Payara eclipse plugin tooling, see: > [https://github.com/payara/ecosystem-eclipse-plugin/issues/11|https://github.com/payara/ecosystem-eclipse-plugin/issues/11] -- This message was sent by Atlassian Jira (v8.20.1#820001) - 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-3273) Cannot run Payara 5 under JDK 8
[
https://issues.apache.org/jira/browse/NETBEANS-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17476428#comment-17476428
]
John commented on NETBEANS-3273:
This is still a problem with Netbeans 12.6.
*System:*
Ubuntu 21.10
{*}IDE{*}:
*Product Version:* Apache NetBeans IDE 12.6
*Java:* 18-ea; OpenJDK 64-Bit Server VM 18-ea+15-Ubuntu-4
*Runtime:* OpenJDK Runtime Environment 18-ea+15-Ubuntu-4
*System:* Linux version 5.13.0-25-generic running on amd64; UTF-8; en_US (nb)
*User directory:* /home/john/.netbeans/12.6
*Cache directory:* /home/john/.cache/netbeans/12.6
*Server:*
Payara 5.2021.9
*JDK Platforms:*
JDK 1.8:
{{$ /usr/lib/jvm/java-1.8.0-openjdk-amd64/bin/java -version}}
{{openjdk version "1.8.0_312"}}
{{OpenJDK Runtime Environment (build 1.8.0_312-8u312-b07-0ubuntu1~21.10-b07)}}
{{OpenJDK 64-Bit Server VM (build 25.312-b07, mixed mode)}}
JDK 18 (Default):
{{$ /usr/lib/jvm/java-18-openjdk-amd64/bin/java -version}}
{{openjdk version "18-ea" 2022-03-15}}
{{OpenJDK Runtime Environment (build 18-ea+15-Ubuntu-4)}}
{{OpenJDK 64-Bit Server VM (build 18-ea+15-Ubuntu-4, mixed mode, sharing)}}
> Cannot run Payara 5 under JDK 8
> ---
>
> Key: NETBEANS-3273
> URL: https://issues.apache.org/jira/browse/NETBEANS-3273
> Project: NetBeans
> Issue Type: Bug
> Components: serverplugins - GlassFish
>Affects Versions: 11.1, 11.2, 12.4
>Reporter: Stephen Parry
>Priority: Major
>
> On Linux (not sure about other platforms), running Payara using JDK 8 gives
> the following error on Services -> server -> Payara -> start:
> Unrecognized option: --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Steps to reproduce:
> # Ensure host system has JDK 11 (as default) and JDK 8 installed
> # Clean install NB 11.1 or 11.2 with JDK 11 as chosen JVM and activate all
> modules
> # Use platform manager to add JDK 8 as new platform.
> # Add a Payara 5.192 or 5.193 server
> # Services -> Server -> Payara Server -> Properties -> Java -> Java Platform:
> JDK 8 -> Close
> # Services -> Server -> Payara Server -> Start
> Expected behaviour:
> Successful startup messages in Payara Server console
> Actual behaviour:
> Failure messages in Payara Server console:
> Unrecognized option: --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> This is a known issue in the original Payara eclipse plugin tooling, see:
> [https://github.com/payara/ecosystem-eclipse-plugin/issues/11|https://github.com/payara/ecosystem-eclipse-plugin/issues/11]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
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-6272) Auto-indent function or pressing tab character in java editor throws NoSuchMethodError
[ https://issues.apache.org/jira/browse/NETBEANS-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John updated NETBEANS-6272: --- Attachment: netbeans-enter-error.gif > Auto-indent function or pressing tab character in java editor throws > NoSuchMethodError > -- > > Key: NETBEANS-6272 > URL: https://issues.apache.org/jira/browse/NETBEANS-6272 > Project: NetBeans > Issue Type: Bug > Components: editor - Formatting Indentation >Affects Versions: 12.6 >Reporter: Petr Miksik >Priority: Major > Attachments: ide.log, java_source.png, netbeans-enter-error.gif, > ui.log > > > When running NetBeans under JDK 1.8, the auto-indentation or inserting a tab > character on a new line throws a NoSuchMethodError, if the source file is > managed by a versioning system (see the attached picture). Running NetBeans > under JDK 11 or higher is OK. -- This message was sent by Atlassian Jira (v8.20.1#820001) - 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-6272) Auto-indent function or pressing tab character in java editor throws NoSuchMethodError
[
https://issues.apache.org/jira/browse/NETBEANS-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456828#comment-17456828
]
John commented on NETBEANS-6272:
I get the following error when hitting ENTER, and then the cursor fails to both
auto-indent and manually indent until I add a character after the cursor.
{code:java}
java.lang.NoSuchMethodError: java.nio.CharBuffer.flip()Ljava/nio/CharBuffer;
at
org.netbeans.modules.java.source.parsing.FileObjects.memoryFileObject(FileObjects.java:516)
at
org.netbeans.modules.java.source.parsing.FileObjects.memoryFileObject(FileObjects.java:490)
at
org.netbeans.modules.java.source.save.Reindenter.initRegionData(Reindenter.java:268)
at
org.netbeans.modules.java.source.save.Reindenter.reindent(Reindenter.java:121)
at
org.netbeans.modules.editor.indent.TaskHandler$MimeItem.runTask(TaskHandler.java:548)
at
org.netbeans.modules.editor.indent.TaskHandler.runTasks(TaskHandler.java:309)
at
org.netbeans.modules.editor.indent.IndentImpl.reindent(IndentImpl.java:282)
at org.netbeans.modules.editor.indent.api.Indent.reindent(Indent.java:146)
at org.netbeans.modules.editor.indent.api.Indent.reindent(Indent.java:130)
at
org.netbeans.editor.BaseKit$InsertBreakAction.performLineBreakInsertion(BaseKit.java:1624)
at
org.netbeans.editor.BaseKit$InsertBreakAction.access$400(BaseKit.java:1439)
at org.netbeans.editor.BaseKit$InsertBreakAction$2.run(BaseKit.java:1529)
at
org.netbeans.editor.GuardedDocument.runAtomicAsUser(GuardedDocument.java:333)
at
org.netbeans.editor.BaseKit$InsertBreakAction.actionPerformed(BaseKit.java:1520)
at org.netbeans.editor.BaseAction.actionPerformed(BaseAction.java:322)
at javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1668)
at javax.swing.JComponent.processKeyBinding(JComponent.java:2882)
at javax.swing.JComponent.processKeyBindings(JComponent.java:2929)
at javax.swing.JComponent.processKeyEvent(JComponent.java:2845)
at java.awt.Component.processEvent(Component.java:6316)
at java.awt.Container.processEvent(Container.java:2239)
at java.awt.Component.dispatchEventImpl(Component.java:4889)
at java.awt.Container.dispatchEventImpl(Container.java:2297)
at java.awt.Component.dispatchEvent(Component.java:4711)
at
java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1954)
at
java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:834)
at
java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:1102)
at
java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:973)
at
java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:799)
at java.awt.Component.dispatchEventImpl(Component.java:4760)
at java.awt.Container.dispatchEventImpl(Container.java:2297)
at java.awt.Window.dispatchEventImpl(Window.java:2746)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:760)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
at
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:84)
at java.awt.EventQueue$4.run(EventQueue.java:733)
at java.awt.EventQueue$4.run(EventQueue.java:731)
at java.security.AccessController.doPrivileged(Native Method)
at
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:730)
at
org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136)
[catch] at
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205)
at
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82){code}
!netbeans-enter-error.gif!
> Auto-indent function or pressing tab character in java editor throws
> NoSuchMethodError
> --
>
> Key: NETBEANS-6272
> URL: https://issues.apache.org/jira/browse/NETBEANS-6272
> Project: NetBeans
> Issue Type: Bug
> Components: editor -
[jira] [Created] (NETBEANS-6280) Error when trying to set breakpoint on JSP page
John created NETBEANS-6280:
--
Summary: Error when trying to set breakpoint on JSP page
Key: NETBEANS-6280
URL: https://issues.apache.org/jira/browse/NETBEANS-6280
Project: NetBeans
Issue Type: Bug
Components: debugger - Java
Affects Versions: 12.6
Environment: Linux, 5.13.0-22-generic, amd64
OpenJDK 64-Bit Server VM, 25.302-b08, OpenJDK Runtime Environment,
1.8.0_302-8u302-b08-0ubuntu2-b08
Apache NetBeans IDE 12.6
Reporter: John
Attachments: ide.log, ui.log
When trying to set a breakpoint on a JSP page, Netbeans throws an error:
{code:java}
SEVERE [org.openide.util.RequestProcessor]: Error in RequestProcessor
org.netbeans.spi.debugger.ActionsProvider$1
java.lang.InternalError: bad SourceDebugExtension syntax - position 42
at com.sun.tools.jdi.SDE.syntax(SDE.java:273)
at com.sun.tools.jdi.SDE.decode(SDE.java:615)
at com.sun.tools.jdi.SDE.(SDE.java:246)
at
com.sun.tools.jdi.ReferenceTypeImpl.sourceDebugExtensionInfo(ReferenceTypeImpl.java:799)
at com.sun.tools.jdi.ReferenceTypeImpl.stratum(ReferenceTypeImpl.java:686)
at
com.sun.tools.jdi.ReferenceTypeImpl.locationsOfLine(ReferenceTypeImpl.java:883)
at
org.netbeans.modules.debugger.jpda.jdi.ReferenceTypeWrapper.locationsOfLine0(ReferenceTypeWrapper.java:2229)
at
org.netbeans.modules.debugger.jpda.breakpoints.LineBreakpointImpl.locationsOfLineInClass(LineBreakpointImpl.java:629)
at
org.netbeans.modules.debugger.jpda.breakpoints.LineBreakpointImpl.getLocations(LineBreakpointImpl.java:570)
at
org.netbeans.modules.debugger.jpda.breakpoints.LineBreakpointImpl.classLoaded(LineBreakpointImpl.java:339)
at
org.netbeans.modules.debugger.jpda.breakpoints.ClassBasedBreakpoint.checkLoadedClasses(ClassBasedBreakpoint.java:503)
at
org.netbeans.modules.debugger.jpda.breakpoints.LineBreakpointImpl.setRequests(LineBreakpointImpl.java:293)
at
org.netbeans.modules.debugger.jpda.breakpoints.BreakpointImpl.update(BreakpointImpl.java:153)
at
org.netbeans.modules.debugger.jpda.breakpoints.BreakpointImpl.set(BreakpointImpl.java:131)
at
org.netbeans.modules.debugger.jpda.breakpoints.LineBreakpointImpl.(LineBreakpointImpl.java:134)
at
org.netbeans.modules.debugger.jpda.breakpoints.BreakpointsEngineListener.createBreakpointImpl(BreakpointsEngineListener.java:318)
at
org.netbeans.modules.debugger.jpda.breakpoints.BreakpointsEngineListener.breakpointAdded(BreakpointsEngineListener.java:156)
at
org.netbeans.api.debugger.DebuggerManager.fireBreakpointCreated(DebuggerManager.java:880)
at
org.netbeans.api.debugger.DebuggerManager.addBreakpoint(DebuggerManager.java:515)
at
org.netbeans.modules.web.debug.breakpoints.JspLineBreakpoint.(JspLineBreakpoint.java:157)
at
org.netbeans.modules.web.debug.breakpoints.JspLineBreakpoint.create(JspLineBreakpoint.java:171)
at
org.netbeans.modules.web.debug.actions.JspToggleBreakpointActionProvider.doAction(JspToggleBreakpointActionProvider.java:118)
at org.netbeans.spi.debugger.ActionsProvider$1.run(ActionsProvider.java:106)
at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
at
org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
[catch] at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033){code}
[^ide.log][^ui.log]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
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-2976) EE Deployment module not working with git-commit-id-plugin and finalName
[
https://issues.apache.org/jira/browse/NETBEANS-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306448#comment-17306448
]
John commented on NETBEANS-2976:
Any update on this issue?
> EE Deployment module not working with git-commit-id-plugin and finalName
>
>
> Key: NETBEANS-2976
> URL: https://issues.apache.org/jira/browse/NETBEANS-2976
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 11.1
> Environment: Ubuntu Linux 19.04, Netbeans 11.1, Oracle JDK 1.8.0_201
>Reporter: John
>Priority: Minor
>
> I have nested maven projects that uses plugin
> `pl.project13.maven:git-commit-id-plugin` in the parent pom, and a child
> project overriding it's artifact name in it's pom. When the `finalName`
> setting in the child project contains properties created by the plugin, the
> NB deployment module can't find the packaged ear for test deployment.
>
> Here is the parent pom.xml:
>
> {code:java}
>
> pl.project13.maven
> git-commit-id-plugin
> 2.2.6
>
>
> get-the-git-infos
>
>revision
>
> initialize
>
>
> validate-the-git-infos
>
>validateRevision
>
> package
>
>
>
> ${project.basedir}/.git
> git
> MMdd'T'HHmm
> false
> false
> false
> false
> true
> true
> false
> false false
> true
> true
>
> ^git.commit.id.abbrev$
> ^git.commit.time$
> ^git.build.version$
> ^git.branch$
>
>
> {code}
>
>
> Here is the child pom.xml:
>
> {code:java}
>
>
> ${project.artifactId}${project.version}${git.branch}${git.commit.time}${git.commit.id.abbrev}
> {code}
>
> {{And IDE.log:}}
> {code:java}
> INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment]
> org.netbeans.modules.j2ee.deployment.impl.TargetServer$NoArchiveException: No
> archive for deployment
> at
> org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:675)
> [catch] at
> org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:221)
> at
> org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:185)
> at
> org.netbeans.modules.maven.j2ee.execution.CoSAlternativeExecutorImpl.execute(CoSAlternativeExecutorImpl.java:67)
> at
> org.netbeans.modules.maven.cos.CoSAlternativeExecutor.execute(CoSAlternativeExecutor.java:64)
> at
> org.netbeans.modules.maven.cos.CosChecker.checkRunMainClass(CosChecker.java:186)
> at
> org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(CosChecker.java:140)
> at
> org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:213)
> at
> org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:128){code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Commented] (NETBEANS-3417) Control line separators
[ https://issues.apache.org/jira/browse/NETBEANS-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17306445#comment-17306445 ] John commented on NETBEANS-3417: [~Kacer]Why was this closed as `incomplete`? Can you add a comment describing the resolution? Thanks. > Control line separators > --- > > Key: NETBEANS-3417 > URL: https://issues.apache.org/jira/browse/NETBEANS-3417 > Project: NetBeans > Issue Type: Bug > Environment: Ubuntu 19.10 > Product Version: Apache NetBeans IDE 11.1 > Java: 1.8.0_181; Java HotSpot(TM) 64-Bit Server VM 25.181-b13 > Runtime: Java(TM) SE Runtime Environment 1.8.0_181-b13 > System: Linux version 5.3.0-23-generic running on amd64; UTF-8; en_US (nb) >Reporter: John Manko >Priority: Major > Attachments: Screenshot from 2019-11-20 16-16-46.png > > > When performing a git diff HEAR, I can see that netbeans is adding an "^M" > character to end of lines. The screenshot shows that where new lines are > created, the non-printable character is appended to the end of lines. > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-2976) EE Deployment module not working with git-commit-id-plugin and finalName
[
https://issues.apache.org/jira/browse/NETBEANS-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John updated NETBEANS-2976:
---
Description:
I have nested maven projects that uses plugin
`pl.project13.maven:git-commit-id-plugin` in the parent pom, and a child
project overriding it's artifact name in it's pom. When the `finalName`
setting in the child project contains properties created by the plugin, the NB
deployment module can't find the packaged ear for test deployment.
Here is the parent pom.xml:
{code:java}
pl.project13.maven
git-commit-id-plugin
2.2.6
get-the-git-infos
revision
initialize
validate-the-git-infos
validateRevision
package
${project.basedir}/.git
git
MMdd'T'HHmm
false
false
false
false
true
true
false
false false
true
true
^git.commit.id.abbrev$
^git.commit.time$
^git.build.version$
^git.branch$
{code}
Here is the child pom.xml:
{code:java}
${project.artifactId}${project.version}${git.branch}${git.commit.time}${git.commit.id.abbrev}
{code}
{{And IDE.log:}}
{code:java}
INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment]
org.netbeans.modules.j2ee.deployment.impl.TargetServer$NoArchiveException: No
archive for deployment
at
org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:675)
[catch] at
org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:221)
at
org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:185)
at
org.netbeans.modules.maven.j2ee.execution.CoSAlternativeExecutorImpl.execute(CoSAlternativeExecutorImpl.java:67)
at
org.netbeans.modules.maven.cos.CoSAlternativeExecutor.execute(CoSAlternativeExecutor.java:64)
at
org.netbeans.modules.maven.cos.CosChecker.checkRunMainClass(CosChecker.java:186)
at
org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(CosChecker.java:140)
at
org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:213)
at
org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:128){code}
was:
Have have nested maven project that uses plugin
`pl.project13.maven:git-commit-id-plugin` in the parent pom, and a child
project overriding it's artifact name in it's pom. When the `finalName`
setting in the child project container properties created by the plugin, the NB
deployment module can't find the packaged ear for deployment.
Here is the parent pom.xml:
{code:java}
pl.project13.maven
git-commit-id-plugin
2.2.6
get-the-git-infos
revision
initialize
validate-the-git-infos
validateRevision
package
${project.basedir}/.git
git
MMdd'T'HHmm
false
false
false
false
true
true
false
false false
true
true
^git.commit.id.abbrev$
^git.commit.time$
^git.build.version$
^git.branch$
{code}
Here is the child pom.xml:
{code:java}
${project.artifactId}${project.version}${git.branch}${git.commit.time}${git.commit.id.abbrev}
{code}
{{And IDE.log:}}
{code:java}
INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment]
org.netbeans.modules.j2ee.deployment.impl.TargetServer$NoArchiveException: No
archive for deployment
at
org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:675)
[catch] at
org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:221)
at
org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:185)
at
org.netbeans.modules.maven.j2ee.execution.CoSAlternativeExecutorImpl.execute(CoSAlternativeExecutorImpl.java:67)
at
org.netbeans.modules.maven.cos.CoSAlternativeExecutor.execute(CoSAlternativeExecutor.java:64)
at
org.netbeans.modules.maven.cos.CosChecker.checkRunMainClass(CosChecker.java:186)
at
org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(CosChecker.java:140)
at
org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:213)
at
org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:128){code}
> EE Deployment module not working with git-commit-id-plugin and finalName
>
>
> Key: NETBEANS-2976
> URL: https://issues.apache.org/jira/browse/NETBEANS-2976
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 11.1
> Environment: Ubuntu Linux 19.04, Netbeans 11.1, Oracle JDK 1.8.0_201
>Reporter: John
>Priority: Minor
>
> I have nested maven projects that uses plugin
>
[jira] [Updated] (NETBEANS-2976) EE Deployment module not working with git-commit-id-plugin and finalName
[
https://issues.apache.org/jira/browse/NETBEANS-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John updated NETBEANS-2976:
---
Description:
Have have nested maven project that uses plugin
`pl.project13.maven:git-commit-id-plugin` in the parent pom, and a child
project overriding it's artifact name in it's pom. When the `finalName`
setting in the child project container properties created by the plugin, the NB
deployment module can't find the packaged ear for deployment.
Here is the parent pom.xml:
{code:java}
pl.project13.maven
git-commit-id-plugin
2.2.6
get-the-git-infos
revision
initialize
validate-the-git-infos
validateRevision
package
${project.basedir}/.git
git
MMdd'T'HHmm
false
false
false
false
true
true
false
false false
true
true
^git.commit.id.abbrev$
^git.commit.time$
^git.build.version$
^git.branch$
{code}
Here is the child pom.xml:
{code:java}
${project.artifactId}${project.version}${git.branch}${git.commit.time}${git.commit.id.abbrev}
{code}
{{And IDE.log:}}
{code:java}
INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment]
org.netbeans.modules.j2ee.deployment.impl.TargetServer$NoArchiveException: No
archive for deployment
at
org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:675)
[catch] at
org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:221)
at
org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:185)
at
org.netbeans.modules.maven.j2ee.execution.CoSAlternativeExecutorImpl.execute(CoSAlternativeExecutorImpl.java:67)
at
org.netbeans.modules.maven.cos.CoSAlternativeExecutor.execute(CoSAlternativeExecutor.java:64)
at
org.netbeans.modules.maven.cos.CosChecker.checkRunMainClass(CosChecker.java:186)
at
org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(CosChecker.java:140)
at
org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:213)
at
org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:128){code}
was:
Have have nested maven project that uses plugin
`pl.project13.maven:git-commit-id-plugin` in the parent pom, and a child
project overriding it's artifact name in it's pom. When the `finalName`
setting in the child project container properties created by the plugin, the NB
deployment module can't find the packaged ear for deployment.
Here is the parent pom.xml:
pl.project13.maven
git-commit-id-plugin
2.2.6
get-the-git-infos
revision
initialize
validate-the-git-infos
validateRevision
package
${project.basedir}/.git
git
MMdd'T'HHmm
false
false
false
false
true
true
falsefalse
false
true
true
^git.commit.id.abbrev$
^git.commit.time$
^git.build.version$
^git.branch$
Here is the child pom.xml:
${project.artifactId}-${project.version}-${git.branch}-${git.commit.time}-${git.commit.id.abbrev}
{{And IDE.log:}}
{code:java}
INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment]
org.netbeans.modules.j2ee.deployment.impl.TargetServer$NoArchiveException: No
archive for deployment
at
org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:675)
[catch] at
org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:221)
at
org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:185)
at
org.netbeans.modules.maven.j2ee.execution.CoSAlternativeExecutorImpl.execute(CoSAlternativeExecutorImpl.java:67)
at
org.netbeans.modules.maven.cos.CoSAlternativeExecutor.execute(CoSAlternativeExecutor.java:64)
at
org.netbeans.modules.maven.cos.CosChecker.checkRunMainClass(CosChecker.java:186)
at
org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(CosChecker.java:140)
at
[jira] [Created] (NETBEANS-2976) EE Deployment module not working with git-commit-id-plugin and finalName
John created NETBEANS-2976:
--
Summary: EE Deployment module not working with
git-commit-id-plugin and finalName
Key: NETBEANS-2976
URL: https://issues.apache.org/jira/browse/NETBEANS-2976
Project: NetBeans
Issue Type: Bug
Affects Versions: 11.1
Environment: Ubuntu Linux 19.04, Netbeans 11.1, Oracle JDK 1.8.0_201
Reporter: John
Have have nested maven project that uses plugin
`pl.project13.maven:git-commit-id-plugin` in the parent pom, and a child
project overriding it's artifact name in it's pom. When the `finalName`
setting in the child project container properties created by the plugin, the NB
deployment module can't find the packaged ear for deployment.
Here is the parent pom.xml:
pl.project13.maven
git-commit-id-plugin
2.2.6
get-the-git-infos
revision
initialize
validate-the-git-infos
validateRevision
package
${project.basedir}/.git
git
MMdd'T'HHmm
false
false
false
false
true
true
falsefalse
false
true
true
^git.commit.id.abbrev$
^git.commit.time$
^git.build.version$
^git.branch$
Here is the child pom.xml:
${project.artifactId}-${project.version}-${git.branch}-${git.commit.time}-${git.commit.id.abbrev}
{{And IDE.log:}}
{code:java}
INFO [org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment]
org.netbeans.modules.j2ee.deployment.impl.TargetServer$NoArchiveException: No
archive for deployment
at
org.netbeans.modules.j2ee.deployment.impl.TargetServer.deploy(TargetServer.java:675)
[catch] at
org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:221)
at
org.netbeans.modules.maven.j2ee.execution.DeploymentHelper.perform(DeploymentHelper.java:185)
at
org.netbeans.modules.maven.j2ee.execution.CoSAlternativeExecutorImpl.execute(CoSAlternativeExecutorImpl.java:67)
at
org.netbeans.modules.maven.cos.CoSAlternativeExecutor.execute(CoSAlternativeExecutor.java:64)
at
org.netbeans.modules.maven.cos.CosChecker.checkRunMainClass(CosChecker.java:186)
at
org.netbeans.modules.maven.cos.CosChecker.checkRunConfig(CosChecker.java:140)
at
org.netbeans.modules.maven.execute.MavenCommandLineExecutor.run(MavenCommandLineExecutor.java:213)
at
org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:128){code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-1850) macOS: Option (⌥ / alt) key not recognised after typing brackets {, [, ], }
[
https://issues.apache.org/jira/browse/NETBEANS-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John updated NETBEANS-1850:
---
Description:
*The issue*
This issue concerns macOS only.
The option key (also known as ⌥ or the alt-key) is no longer recognised by
Netbeans after opening or closing a curly or squared bracket, i.e. after typing
*{* or *[*.
Netbeans automatically closes brackets by default. However, even with this
feature disabled, the option-key still stops working after pressing one of
these keys.
The option-key is still available to open an additional bracket. However, any
additional functionality is lost.
After re-opening Netbeans, the program does recognise the option key again.
This, however, only stays until a new bracket is opened.
*Steps to reproduce the issue*
Make sure you are using Netbeans later than 8.2 on macOS.
# Open any project. Note the option-key is working, e.g. by navigating your
code by pressing the option key and the left and right arrows at the same time.
** This can be confirmed by opening the keymap settings (Preferences, Keymap)
and clicking on "in shortcuts".
** After pressing the option key in this field, the symbol of the key is
displayed as such.
** This shows the option key is perfectly recognised by Netbeans.
# Type a *{* or *[* at any position in your project.
# Try using the option (alt)-key again in Netbeans. You will notice the key
seems broken.
** This can be confirmed by opening the keymap settings (Preferences, Keymap)
and clicking on "in shortcuts".
** When pressing the option key in this field, the field stays blank.
** This shows the option key is no longer recognised by Netbeans.
# Re-open netbeans. Then, press to use alt-key and note that it works again.
*About the issue*
The issue started appearing in Netbeans 9 and is still present in Netbeans 10.
It is not present in Netbeans 8.2.
was:
*The issue*
This issue concerns macOS only.
The option key (also known as the alt-key) is no longer recognised by Netbeans
after opening a curly or squared bracket, i.e. after typing *{* or *[*.
Netbeans automatically closes brackets by default. However, even with this
feature disabled, the alt-key still stops working after pressing one of these
keys.
After re-opening Netbeans, the program does recognise the option key again
until a bracket is opened.
*Steps to reproduce the issue*
Make sure you are using Netbeans later than 8.2 on macOS.
# Open any project. Note the option-key is working, e.g. by navigating your
code using the option key and the left and right arrows.
# Type a *{* or *[* at any position in your project.
# Try using the option (alt)-key again in Netbeans. You will notice the key
seems broken.
# Re-open netbeans, try to use alt-key again and note that it works again.
The bug can be confirmed by opening the keymap settings and searching "in
shortcuts". When pressing the option key in this field, the field stays blank.
*About the issue*
The issue started appearing in Netbeans 9 and is still present in Netbeans 10.
It is not present in Netbeans 8.2.
Summary: macOS: Option (⌥ / alt) key not recognised after typing
brackets {, [, ], } (was: macOS: Option (alt) key not recognised after typing
brackets { or [)
> macOS: Option (⌥ / alt) key not recognised after typing brackets {, [, ], }
> ---
>
> Key: NETBEANS-1850
> URL: https://issues.apache.org/jira/browse/NETBEANS-1850
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 9.0, 10.0
> Environment: macOS Mojave on a Macbook Air Early 2015, Netbeans Binary
>Reporter: John
>Priority: Major
>
> *The issue*
> This issue concerns macOS only.
> The option key (also known as ⌥ or the alt-key) is no longer recognised by
> Netbeans after opening or closing a curly or squared bracket, i.e. after
> typing *{* or *[*.
> Netbeans automatically closes brackets by default. However, even with this
> feature disabled, the option-key still stops working after pressing one of
> these keys.
> The option-key is still available to open an additional bracket. However, any
> additional functionality is lost.
> After re-opening Netbeans, the program does recognise the option key again.
> This, however, only stays until a new bracket is opened.
> *Steps to reproduce the issue*
> Make sure you are using Netbeans later than 8.2 on macOS.
> # Open any project. Note the option-key is working, e.g. by navigating your
> code by pressing the option key and the left and right arrows at the same
> time.
> ** This can be confirmed by opening the keymap settings (Preferences,
> Keymap) and clicking on "in shortcuts".
> ** After pressing the option key in this field, the symbol of the key is
> displayed as such.
> ** This shows the
[jira] [Updated] (NETBEANS-1850) macOS: Option (alt) key not recognised after typing brackets { or [
[
https://issues.apache.org/jira/browse/NETBEANS-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John updated NETBEANS-1850:
---
Environment: macOS Mojave on a Macbook Air Early 2015, Netbeans Binary
(was: macOS Mojave, Netbeans Binary)
Description:
*The issue*
This issue concerns macOS only.
The option key (also known as the alt-key) is no longer recognised by Netbeans
after opening a curly or squared bracket, i.e. after typing *{* or *[*.
Netbeans automatically closes brackets by default. However, even with this
feature disabled, the alt-key still stops working after pressing one of these
keys.
After re-opening Netbeans, the program does recognise the option key again
until a bracket is opened.
*Steps to reproduce the issue*
Make sure you are using Netbeans later than 8.2 on macOS.
# Open any project. Note the option-key is working, e.g. by navigating your
code using the option key and the left and right arrows.
# Type a *{* or *[* at any position in your project.
# Try using the option (alt)-key again in Netbeans. You will notice the key
seems broken.
# Re-open netbeans, try to use alt-key again and note that it works again.
The bug can be confirmed by opening the keymap settings and searching "in
shortcuts". When pressing the option key in this field, the field stays blank.
*About the issue*
The issue started appearing in Netbeans 9 and is still present in Netbeans 10.
It is not present in Netbeans 8.2.
was:
*The issue*
This issue concerns macOS only.
The option key (also known as the alt-key) is no longer recognised by Netbeans
after opening a curly or squared bracket, i.e. after typing *{* or *[*.
Netbeans automatically closes brackets by default. However, even with this
feature disabled, the alt-key still stops working after pressing one of these
keys.
*Steps to reproduce the issue*
The bug can be confirmed by opening the keymap settings and searching "in
shortcuts". When pressing the option key in this field, the field stays blank.
After re-opening Netbeans, the program does recognise the option key again
until a bracket is opened.
*About the issue*
The issue started appearing in Netbeans 9 and is still present in Netbeans 10.
It is not present in Netbeans 8.2.
> macOS: Option (alt) key not recognised after typing brackets { or [
> ---
>
> Key: NETBEANS-1850
> URL: https://issues.apache.org/jira/browse/NETBEANS-1850
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 9.0, 10.0
> Environment: macOS Mojave on a Macbook Air Early 2015, Netbeans Binary
>Reporter: John
>Priority: Major
>
> *The issue*
> This issue concerns macOS only.
> The option key (also known as the alt-key) is no longer recognised by
> Netbeans after opening a curly or squared bracket, i.e. after typing *{* or
> *[*.
> Netbeans automatically closes brackets by default. However, even with this
> feature disabled, the alt-key still stops working after pressing one of these
> keys.
> After re-opening Netbeans, the program does recognise the option key again
> until a bracket is opened.
> *Steps to reproduce the issue*
> Make sure you are using Netbeans later than 8.2 on macOS.
> # Open any project. Note the option-key is working, e.g. by navigating your
> code using the option key and the left and right arrows.
> # Type a *{* or *[* at any position in your project.
> # Try using the option (alt)-key again in Netbeans. You will notice the key
> seems broken.
> # Re-open netbeans, try to use alt-key again and note that it works again.
> The bug can be confirmed by opening the keymap settings and searching "in
> shortcuts". When pressing the option key in this field, the field stays blank.
> *About the issue*
> The issue started appearing in Netbeans 9 and is still present in Netbeans
> 10. It is not present in Netbeans 8.2.
--
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-1850) macOS: Option (alt) key not recognised after typing brackets { or [
[
https://issues.apache.org/jira/browse/NETBEANS-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John updated NETBEANS-1850:
---
Priority: Major (was: Minor)
> macOS: Option (alt) key not recognised after typing brackets { or [
> ---
>
> Key: NETBEANS-1850
> URL: https://issues.apache.org/jira/browse/NETBEANS-1850
> Project: NetBeans
> Issue Type: Bug
>Affects Versions: 9.0, 10.0
> Environment: macOS Mojave, Netbeans Binary
>Reporter: John
>Priority: Major
>
> *The issue*
> This issue concerns macOS only.
> The option key (also known as the alt-key) is no longer recognised by
> Netbeans after opening a curly or squared bracket, i.e. after typing *{* or
> *[*.
> Netbeans automatically closes brackets by default. However, even with this
> feature disabled, the alt-key still stops working after pressing one of these
> keys.
> *Steps to reproduce the issue*
> The bug can be confirmed by opening the keymap settings and searching "in
> shortcuts". When pressing the option key in this field, the field stays blank.
> After re-opening Netbeans, the program does recognise the option key again
> until a bracket is opened.
> *About the issue*
> The issue started appearing in Netbeans 9 and is still present in Netbeans
> 10. It is not present in Netbeans 8.2.
--
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-1850) macOS: Option (alt) key not recognised after typing brackets { or [
John created NETBEANS-1850:
--
Summary: macOS: Option (alt) key not recognised after typing
brackets { or [
Key: NETBEANS-1850
URL: https://issues.apache.org/jira/browse/NETBEANS-1850
Project: NetBeans
Issue Type: Bug
Affects Versions: 9.0, 10.0
Environment: macOS Mojave, Netbeans Binary
Reporter: John
*The issue*
This issue concerns macOS only.
The option key (also known as the alt-key) is no longer recognised by Netbeans
after opening a curly or squared bracket, i.e. after typing *{* or *[*.
Netbeans automatically closes brackets by default. However, even with this
feature disabled, the alt-key still stops working after pressing one of these
keys.
*Steps to reproduce the issue*
The bug can be confirmed by opening the keymap settings and searching "in
shortcuts". When pressing the option key in this field, the field stays blank.
After re-opening Netbeans, the program does recognise the option key again
until a bracket is opened.
*About the issue*
The issue started appearing in Netbeans 9 and is still present in Netbeans 10.
It is not present in Netbeans 8.2.
--
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
