[JBoss JIRA] (JBDS-4321) Unable to start Devstudio without -clean after install of any stuff from RH Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4321?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4321:
-----------------------------
Fix Version/s: 10.4.0.GA
(was: 10.4.0.AM3)
> Unable to start Devstudio without -clean after install of any stuff from RH Central
> -----------------------------------------------------------------------------------
>
> Key: JBDS-4321
> URL: https://issues.jboss.org/browse/JBDS-4321
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM2
> Environment: RHEL7, RHSCL 2.4 Beta 1.1, Devstudio 10.4-0.20170320.0955.el7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.4.0.GA
>
> Attachments: Start_without_clean.png, rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt, rpm-installed-everything-from-central.png, rpm-installed-everything-from-central.update.rpm.deps.txt
>
>
> When I install something from Red Hat Central and then start Devstudio without -clean then I get this error:
> {code}
> !ENTRY org.eclipse.e4.ui.workbench 4 0 2017-03-23 07:51:22.689
> !MESSAGE Unable to load resource platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi
> !STACK 0
> java.lang.NullPointerException
> {code}
> There are multiple errors but this one seems to be common for multiple items.
> And this window appear:
> !Start_without_clean.png|thumbnail!
> There is easy workaround but user won't start Devstudio with -clean and many of them could be upset.
> Please see the log: [^rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt] There is what I got when I installed FindBugs. I put some comments there so you can find sections installation/start without clean/start with clean.
> CC: [~psrna] [~vkadlcik]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23422:
------------------------------------
Slip to 4.5.0.AM1 based on Jeff's comments.
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.5.0.AM1
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23422:
-------------------------------
Sprint: devex #130 April 2017, devex #131 April 2017 (was: devex #130 April 2017)
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.5.0.AM1
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23422:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.4.Final)
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.5.0.AM1
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24377) Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24377?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24377:
------------------------------------
Jobs only check github every 6-8hrs. You need to trigger your job manually if you want it to spin up more often.
But because I'm awesome, I've kicked it for you.
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=8
> Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-24377
> URL: https://issues.jboss.org/browse/JBIDE-24377
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> {code}
> 14:38:32 [INFO] org.jboss.ide.eclipse.as.management.wf11 ........... FAILURE [ 14.669 s]
> 14:38:32 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.7:copy (get-libs) on project org.jboss.ide.eclipse.as.management.wf11: Unable to find artifact. Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT in jboss-releases (https://repository.jboss.org/nexus/content/repositories/releases)
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] Try downloading the file manually from the project website.
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] Then, install it using the command:
> 14:38:32 [ERROR] mvn install:install-file -DgroupId=org.wildfly.core -DartifactId=wildfly-controller-client -Dversion=3.0.0.Beta16-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] Alternatively, if you host your own repository you can deploy the file there:
> 14:38:32 [ERROR] mvn deploy:deploy-file -DgroupId=org.wildfly.core -DartifactId=wildfly-controller-client -Dversion=3.0.0.Beta16-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> 14:38:32 [ERROR]
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] from the specified remote repositories:
> 14:38:32 [ERROR] redhat-ea-repository (https://maven.repository.redhat.com/earlyaccess/all/, releases=true, snapshots=false),
> 14:38:32 [ERROR] redhat-ga-repository (http://maven.repository.redhat.com/ga/, releases=true, snapshots=false),
> 14:38:32 [ERROR] jboss-releases (https://repository.jboss.org/nexus/content/repositories/releases, releases=true, snapshots=true),
> 14:38:32 [ERROR] jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/, releases=true, snapshots=true),
> 14:38:32 [ERROR] jbosstools-experiments (https://repository.jboss.org/nexus/content/repositories/jbosstools-experi..., releases=true, snapshots=true),
> 14:38:32 [ERROR] jbosstools-base (http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b..., releases=false, snapshots=false),
> 14:38:32 [ERROR] jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=true),
> 14:38:32 [ERROR] jboss-ga-repository (http://maven.repository.redhat.com/ga/, releases=true, snapshots=true),
> 14:38:32 [ERROR] central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false)
> 14:38:32 [ERROR] -> [Help 1]
> {code}
> -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months
[JBoss JIRA] (JBIDE-24377) Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24377?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24377:
-------------------------------------
Seems the snapshot disappeared and beta16 is available now. So I've fixed that. Waiting for a build to verify
> Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-24377
> URL: https://issues.jboss.org/browse/JBIDE-24377
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> {code}
> 14:38:32 [INFO] org.jboss.ide.eclipse.as.management.wf11 ........... FAILURE [ 14.669 s]
> 14:38:32 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.7:copy (get-libs) on project org.jboss.ide.eclipse.as.management.wf11: Unable to find artifact. Could not find artifact org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT in jboss-releases (https://repository.jboss.org/nexus/content/repositories/releases)
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] Try downloading the file manually from the project website.
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] Then, install it using the command:
> 14:38:32 [ERROR] mvn install:install-file -DgroupId=org.wildfly.core -DartifactId=wildfly-controller-client -Dversion=3.0.0.Beta16-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] Alternatively, if you host your own repository you can deploy the file there:
> 14:38:32 [ERROR] mvn deploy:deploy-file -DgroupId=org.wildfly.core -DartifactId=wildfly-controller-client -Dversion=3.0.0.Beta16-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> 14:38:32 [ERROR]
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] org.wildfly.core:wildfly-controller-client:jar:3.0.0.Beta16-SNAPSHOT
> 14:38:32 [ERROR]
> 14:38:32 [ERROR] from the specified remote repositories:
> 14:38:32 [ERROR] redhat-ea-repository (https://maven.repository.redhat.com/earlyaccess/all/, releases=true, snapshots=false),
> 14:38:32 [ERROR] redhat-ga-repository (http://maven.repository.redhat.com/ga/, releases=true, snapshots=false),
> 14:38:32 [ERROR] jboss-releases (https://repository.jboss.org/nexus/content/repositories/releases, releases=true, snapshots=true),
> 14:38:32 [ERROR] jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/, releases=true, snapshots=true),
> 14:38:32 [ERROR] jbosstools-experiments (https://repository.jboss.org/nexus/content/repositories/jbosstools-experi..., releases=true, snapshots=true),
> 14:38:32 [ERROR] jbosstools-base (http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-b..., releases=false, snapshots=false),
> 14:38:32 [ERROR] jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/, releases=true, snapshots=true),
> 14:38:32 [ERROR] jboss-ga-repository (http://maven.repository.redhat.com/ga/, releases=true, snapshots=true),
> 14:38:32 [ERROR] central (https://repo.maven.apache.org/maven2, releases=true, snapshots=false)
> 14:38:32 [ERROR] -> [Help 1]
> {code}
> -- https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 8 months