[JBoss JIRA] (ERT-136) ArrayIndexOutOfBoundsException in JavaScriptValidator.findSourceFile(JavaScriptValidator.java:89) [EBZ#490830]
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/ERT-136?page=com.atlassian.jira.plugin.sy... ]
Victor Rubezhny resolved ERT-136.
---------------------------------
Resolution: Done
> ArrayIndexOutOfBoundsException in JavaScriptValidator.findSourceFile(JavaScriptValidator.java:89) [EBZ#490830]
> --------------------------------------------------------------------------------------------------------------
>
> Key: ERT-136
> URL: https://issues.jboss.org/browse/ERT-136
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Labels: General, bzira
> Fix For: Neon (4.6) M7
>
>
> An exception occurs when a JavaScript project has no Source Folder defined:
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.eclipse.wst.jsdt.internal.core.validation.JavaScriptValidator.findSourceFile(JavaScriptValidator.java:89)
> at org.eclipse.wst.jsdt.internal.core.validation.JavaScriptValidator.validate(JavaScriptValidator.java:55)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299)
> at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:120)
> at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:84)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:129)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:94)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:117)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:105)
> at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219)
> at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178)
> at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ERT-136) ArrayIndexOutOfBoundsException in JavaScriptValidator.findSourceFile(JavaScriptValidator.java:89) [EBZ#490830]
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/ERT-136?page=com.atlassian.jira.plugin.sy... ]
Victor Rubezhny updated ERT-136:
--------------------------------
Fix Version/s: Neon (4.6) M7
> ArrayIndexOutOfBoundsException in JavaScriptValidator.findSourceFile(JavaScriptValidator.java:89) [EBZ#490830]
> --------------------------------------------------------------------------------------------------------------
>
> Key: ERT-136
> URL: https://issues.jboss.org/browse/ERT-136
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Nick Boldt
> Labels: General, bzira
> Fix For: Neon (4.6) M7
>
>
> An exception occurs when a JavaScript project has no Source Folder defined:
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.eclipse.wst.jsdt.internal.core.validation.JavaScriptValidator.findSourceFile(JavaScriptValidator.java:89)
> at org.eclipse.wst.jsdt.internal.core.validation.JavaScriptValidator.validate(JavaScriptValidator.java:55)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299)
> at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:120)
> at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:84)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:129)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:94)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:117)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:105)
> at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219)
> at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178)
> at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ERT-136) ArrayIndexOutOfBoundsException in JavaScriptValidator.findSourceFile(JavaScriptValidator.java:89) [EBZ#490830]
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/ERT-136?page=com.atlassian.jira.plugin.sy... ]
Victor Rubezhny reassigned ERT-136:
-----------------------------------
Assignee: Victor Rubezhny
> ArrayIndexOutOfBoundsException in JavaScriptValidator.findSourceFile(JavaScriptValidator.java:89) [EBZ#490830]
> --------------------------------------------------------------------------------------------------------------
>
> Key: ERT-136
> URL: https://issues.jboss.org/browse/ERT-136
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Labels: General, bzira
> Fix For: Neon (4.6) M7
>
>
> An exception occurs when a JavaScript project has no Source Folder defined:
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.eclipse.wst.jsdt.internal.core.validation.JavaScriptValidator.findSourceFile(JavaScriptValidator.java:89)
> at org.eclipse.wst.jsdt.internal.core.validation.JavaScriptValidator.validate(JavaScriptValidator.java:55)
> at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
> at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
> at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
> at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
> at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299)
> at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:120)
> at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:84)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:129)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:94)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:52)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:117)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:105)
> at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219)
> at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178)
> at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3799) Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3799?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3799:
---------------------------------
Component/s: cdk
> Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-3799
> URL: https://issues.jboss.org/browse/JBDS-3799
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Hardy Ferentschik
> Priority: Critical
> Labels: havoc
>
> This unresolved issue: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/272
> Is causing rsync issues such as:
> default: Rsyncing folder: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant
> There was an error when attempting to rsync a synced folder.
> Please inspect the error message below for more info.
> Host path: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/
> Guest path: /vagrant
> Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ vagrant@127.0.0.1:/vagrant
> Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts.
> dup() in/out/err failed
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3799) Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3799?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3799:
---------------------------------
Component/s: upstream
(was: installer)
> Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-3799
> URL: https://issues.jboss.org/browse/JBDS-3799
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Priority: Critical
> Labels: havoc
>
> This unresolved issue: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/272
> Is causing rsync issues such as:
> default: Rsyncing folder: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant
> There was an error when attempting to rsync a synced folder.
> Please inspect the error message below for more info.
> Host path: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/
> Guest path: /vagrant
> Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ vagrant@127.0.0.1:/vagrant
> Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts.
> dup() in/out/err failed
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3799) Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3799?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3799:
------------------------------------
Assignee: Hardy Ferentschik (was: Fred Bricon)
> Installer - rsync failures seen during post-install JBDS startup of CDK as server runtime
> -----------------------------------------------------------------------------------------
>
> Key: JBDS-3799
> URL: https://issues.jboss.org/browse/JBDS-3799
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Hardy Ferentschik
> Priority: Critical
> Labels: havoc
>
> This unresolved issue: https://github.com/projectatomic/adb-atomic-developer-bundle/issues/272
> Is causing rsync issues such as:
> default: Rsyncing folder: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant
> There was an error when attempting to rsync a synced folder.
> Please inspect the error message below for more info.
> Host path: /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/
> Guest path: /vagrant
> Command: rsync --verbose --archive --delete -z --copy-links --chmod=ugo=rwX --no-perms --no-owner --no-group --rsync-path sudo rsync -e ssh -p 2222 -o StrictHostKeyChecking=no -o IdentitiesOnly=true -o UserKnownHostsFile=/dev/null -i 'C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/private_key' --exclude .vagrant/ /c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ vagrant@127.0.0.1:/vagrant
> Error: Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts.
> dup() in/out/err failed
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.2]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21857:
-------------------------------------
The patched jdk was for windows. I was testing in linux.
As for the java code, I was testing jbosstools, with the patch you provided. In the end I moved some code around to make the heirarchy of plugins more appropriate (as.wst.core shouldnt depend on jmx), but the code was essentially the same.
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3798) Repeated component detection keeps stale values
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3798?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3798:
--------------------------------------
Ah, you mean:
1. Go to the confirmation page
2. Then back to the login page
3. Then go forward to the confirmation page again -> Broken
?
> Repeated component detection keeps stale values
> -----------------------------------------------
>
> Key: JBDS-3798
> URL: https://issues.jboss.org/browse/JBDS-3798
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Setup-bundled-0.0.2-20160413-107
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Attachments: screenshot-1.png
>
>
> Installer detects existing tools on confirmation page. If after that a change happens (like the user uninstalls VirtualBox) and then the user goes to the previous page and to confirm page again - the change is correctly detected, but instead of replacing the old option, there are now both options for 'install' and 'use existing'. Plus the count of detected components stays the same.
> Using the existing (no longer existing in fact) installation fails, naturally.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3798) Repeated component detection keeps stale values
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3798?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3798:
--------------------------------------
{quote}and then the user goes to the previous page and to confirm page again{quote}
Goes to the previous page from what? We should not allow to go to the confirmation page back from the "download and install" page.
> Repeated component detection keeps stale values
> -----------------------------------------------
>
> Key: JBDS-3798
> URL: https://issues.jboss.org/browse/JBDS-3798
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Setup-bundled-0.0.2-20160413-107
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Attachments: screenshot-1.png
>
>
> Installer detects existing tools on confirmation page. If after that a change happens (like the user uninstalls VirtualBox) and then the user goes to the previous page and to confirm page again - the change is correctly detected, but instead of replacing the old option, there are now both options for 'install' and 'use existing'. Plus the count of detected components stays the same.
> Using the existing (no longer existing in fact) installation fails, naturally.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years