June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22630) bzira/jiralint fails often because of missing pip install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22630?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22630 at 6/23/16 8:47 AM: ------------------------------------------------------------- >From eng-ops: {quote}those particular slaves are owned/managed by EAP QE team. Those are provisioned by the automation ([1]) which was taken over by EAP QE couple of months ago. You can ask them for incorporation of your request to it or you can fix it by yourself in [1], prepare PR and ask them for merge/rep-provision those slaves after. I suppose all slaves under [2] are affected by this issue. [1] https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-beaker-slav... [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/EAP-RHEL7{quote} was (Author: nickboldt): >From eng-ops: {quote}those particular slaves are owned/managed by EAP QE team. Those are provisioned by the automation ([1]) which was taken over by EAP QE couple of months ago. You can ask them for incorporation of your request to it or you can fix it by yourself in [1], prepare PR and ask them for merge/rep-provision those slaves after. I suppose all slaves under [2] are affected by this issue. {code} [1] https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-beaker-slav... [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/EAP-RHEL7 > bzira/jiralint fails often because of missing pip install > --------------------------------------------------------- > > Key: JBIDE-22630 > URL: https://issues.jboss.org/browse/JBIDE-22630 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > > bzia/jiralint oftenn fails because pip are missing from the servers it runs on. > shuold limit the nodes it runs on or get pip installed more generally. > error from build mails > {code} > + pip install --upgrade --user bugzilla bugzillatools python-bugzilla jira pytz > Traceback (most recent call last): > File "/qa/services/hudson/.local/bin/pip", line 7, in <module> > from pip import main > ImportError: No module named pip > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22630) bzira/jiralint fails often because of missing pip install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22630?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22630: ------------------------------------ >From eng-ops: {quote}those particular slaves are owned/managed by EAP QE team. Those are provisioned by the automation ([1]) which was taken over by EAP QE couple of months ago. You can ask them for incorporation of your request to it or you can fix it by yourself in [1], prepare PR and ask them for merge/rep-provision those slaves after. I suppose all slaves under [2] are affected by this issue. {code} [1] https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-beaker-slav... [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/EAP-RHEL7 > bzira/jiralint fails often because of missing pip install > --------------------------------------------------------- > > Key: JBIDE-22630 > URL: https://issues.jboss.org/browse/JBIDE-22630 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > > bzia/jiralint oftenn fails because pip are missing from the servers it runs on. > shuold limit the nodes it runs on or get pip installed more generally. > error from build mails > {code} > + pip install --upgrade --user bugzilla bugzillatools python-bugzilla jira pytz > Traceback (most recent call last): > File "/qa/services/hudson/.local/bin/pip", line 7, in <module> > from pip import main > ImportError: No module named pip > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3847) Need new screenshot for DevStudio 10 update site page

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3847?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3847. ----------------------------- Closing as done. > Need new screenshot for DevStudio 10 update site page > ----------------------------------------------------- > > Key: JBDS-3847 > URL: https://issues.jboss.org/browse/JBDS-3847 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: documentation, updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.GA > > Attachments: devstudio.png, devstudio10-screenshot-full.png, devstudio10-screenshot-thumb.png > > > https://devstudio.redhat.com/10.0/staging/updates/ contains two screenshots, both showing "JBoss Central". > Since we're now calling that Red Hat Central, we need new screenshots for that page. > We could also backport this to the /9.0/ pages if anyone cares. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-322) Docker Search Images dialog is broken on second call [EBZ#496633]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-322: --------------------------------------- Summary: Docker Search Images dialog is broken on second call [EBZ#496633] Key: ERT-322 URL: https://issues.jboss.org/browse/ERT-322 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon.1 (4.6) Created attachment 262626 Resulting UI When searching for a Docker Image to pull, the second time the dialog is opened, the UI is broken and the whole Eclipse hangs when closing the dialog with the cancel button. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-792) Remove deprecated VDB, WAR framework and update tests

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-792?page=com.atlassian.jira.plugin.... ] stanislav kaleta resolved JBTIS-792. ------------------------------------ Resolution: Done > Remove deprecated VDB, WAR framework and update tests > ----------------------------------------------------- > > Key: JBTIS-792 > URL: https://issues.jboss.org/browse/JBTIS-792 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22642) ProcessInformationStore.loadprocessStore doesn't work on Windows

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22642?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-22642: ------------------------------------ Description: - l.90 it searches for a jps file although the file is jps.exe on Windows jps = jHomePath.removeLastSegments(1).append("bin").append("jps").toFile(); error log: {noformat} java.io.IOException: Cannot run program "C:\Program Files\Java\jdk1.8.0_65\jre\bin\jps": CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at java.lang.Runtime.exec(Runtime.java:620) at java.lang.Runtime.exec(Runtime.java:485) at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:102) at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64) at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:140) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.<init>(ProcessImpl.java:386) at java.lang.ProcessImpl.start(ProcessImpl.java:137) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) {noformat} was: - it searches for a jps file although the file is jps.exe on Windows jps = jHomePath.removeLastSegments(1).append("bin").append("jps").toFile(); error log: {noformat} java.io.IOException: Cannot run program "C:\Program Files\Java\jdk1.8.0_65\jre\bin\jps": CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at java.lang.Runtime.exec(Runtime.java:620) at java.lang.Runtime.exec(Runtime.java:485) at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:102) at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64) at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:140) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.<init>(ProcessImpl.java:386) at java.lang.ProcessImpl.start(ProcessImpl.java:137) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) {noformat} > ProcessInformationStore.loadprocessStore doesn't work on Windows > ---------------------------------------------------------------- > > Key: JBIDE-22642 > URL: https://issues.jboss.org/browse/JBIDE-22642 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.1.Final > Environment: Windows > Reporter: Aurélien Pupier > > - l.90 it searches for a jps file although the file is jps.exe on Windows > jps = jHomePath.removeLastSegments(1).append("bin").append("jps").toFile(); > error log: > {noformat} > java.io.IOException: Cannot run program "C:\Program Files\Java\jdk1.8.0_65\jre\bin\jps": CreateProcess error=2, The system cannot find the file specified > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) > at java.lang.Runtime.exec(Runtime.java:620) > at java.lang.Runtime.exec(Runtime.java:485) > at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:102) > at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64) > at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:140) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified > at java.lang.ProcessImpl.create(Native Method) > at java.lang.ProcessImpl.<init>(ProcessImpl.java:386) > at java.lang.ProcessImpl.start(ProcessImpl.java:137) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22642) ProcessInformationStore.loadprocessStore doesn't work on Windows

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22642?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-22642: ------------------------------------ Description: - it searches for a jps file although the file is jps.exe on Windows jps = jHomePath.removeLastSegments(1).append("bin").append("jps").toFile(); error log: {noformat} java.io.IOException: Cannot run program "C:\Program Files\Java\jdk1.8.0_65\jre\bin\jps": CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at java.lang.Runtime.exec(Runtime.java:620) at java.lang.Runtime.exec(Runtime.java:485) at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:102) at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64) at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:140) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.<init>(ProcessImpl.java:386) at java.lang.ProcessImpl.start(ProcessImpl.java:137) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) {noformat} was: - it searches for a jps file although the file is jps.exe error log: {noformat} java.io.IOException: Cannot run program "C:\Program Files\Java\jdk1.8.0_65\jre\bin\jps": CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at java.lang.Runtime.exec(Runtime.java:620) at java.lang.Runtime.exec(Runtime.java:485) at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:102) at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64) at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:140) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.<init>(ProcessImpl.java:386) at java.lang.ProcessImpl.start(ProcessImpl.java:137) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) {noformat} > ProcessInformationStore.loadprocessStore doesn't work on Windows > ---------------------------------------------------------------- > > Key: JBIDE-22642 > URL: https://issues.jboss.org/browse/JBIDE-22642 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.3.1.Final > Environment: Windows > Reporter: Aurélien Pupier > > - it searches for a jps file although the file is jps.exe on Windows > jps = jHomePath.removeLastSegments(1).append("bin").append("jps").toFile(); > error log: > {noformat} > java.io.IOException: Cannot run program "C:\Program Files\Java\jdk1.8.0_65\jre\bin\jps": CreateProcess error=2, The system cannot find the file specified > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) > at java.lang.Runtime.exec(Runtime.java:620) > at java.lang.Runtime.exec(Runtime.java:485) > at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:102) > at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64) > at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:140) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified > at java.lang.ProcessImpl.create(Native Method) > at java.lang.ProcessImpl.<init>(ProcessImpl.java:386) > at java.lang.ProcessImpl.start(ProcessImpl.java:137) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22642) ProcessInformationStore.loadprocessStore doesn't work on Windows

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-22642: --------------------------------------- Summary: ProcessInformationStore.loadprocessStore doesn't work on Windows Key: JBIDE-22642 URL: https://issues.jboss.org/browse/JBIDE-22642 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 4.3.1.Final Environment: Windows Reporter: Aurélien Pupier - it searches for a jps file although the file is jps.exe error log: {noformat} java.io.IOException: Cannot run program "C:\Program Files\Java\jdk1.8.0_65\jre\bin\jps": CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at java.lang.Runtime.exec(Runtime.java:620) at java.lang.Runtime.exec(Runtime.java:485) at org.jboss.tools.jmx.local.ProcessInformationStore.loadProcessStore(ProcessInformationStore.java:102) at org.jboss.tools.jmx.local.ProcessInformationStore.refreshProcessInformationStore(ProcessInformationStore.java:64) at org.jboss.tools.jmx.local.ProcessInformationStore$1.run(ProcessInformationStore.java:140) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.<init>(ProcessImpl.java:386) at java.lang.ProcessImpl.start(ProcessImpl.java:137) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22635) Deprecate / Remove the Server Log View

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22635?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22635: --------------------------------------- +1 I only saw it several times and wasn't sure what added value it provides. > Deprecate / Remove the Server Log View > -------------------------------------- > > Key: JBIDE-22635 > URL: https://issues.jboss.org/browse/JBIDE-22635 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.S116 > Reporter: Rob Stryker > > Deprecate and remove the Server Log View. > The Server Log View was originally designed to allow a custom "Error Log" to be filled with information that wasn't just "errors" but more like tracing what the server adapter was doing. > In it's original form, it held all status warnings and errors, and users never saw them. Eventually, we started also sending the status objects to the official Error Log, so users may see them. Once that happened, the Server Log view became completely redundant. It's only benefits were that it occasionally over-logged stuff that wasn't appropriate to send to the main error log... but it's API / extension points were kinda ugly, and it overall isn't very useful any longer. > Also, other server adapters have requested we remove the action at least, for their server types, since they never use the Server Log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22641) When an Openshift connection is deleted, the secure entries are not removed

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-22641: ---------------------------------- Summary: When an Openshift connection is deleted, the secure entries are not removed Key: JBIDE-22641 URL: https://issues.jboss.org/browse/JBIDE-22641 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Final Reporter: Jeff MAURY When a token or password is saved in secure storage for an Openshift connection, then deleting this connection will not remove this data from secure storage. Then creating a new connection with the same address will reuse this infos. This is a security breach -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2016