June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22629) bzira missing mapping for linux tools 5.1.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22629?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-22629. -------------------------------- Resolution: Done Fixed. Examples, see: https://issues.jboss.org/browse/ERT-307 and https://issues.jboss.org/browse/ERT-311 Also, added new Thym mapping: https://issues.jboss.org/browse/ERT-315 > bzira missing mapping for linux tools 5.1. > ------------------------------------------ > > Key: JBIDE-22629 > URL: https://issues.jboss.org/browse/JBIDE-22629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Jeff Johnston > Fix For: 4.4.1.S116 > > > bzira/jiralint is failing on missing version mapping for linux tools 5.1.0 - what release train is 5.1.0 targetd for ? Neon.1 ? > Related log from build fail mails: > {code} > [ERROR] Unknown version for Linux Tools / 5.1.0 > [ERROR] No mapping for '5.1.0'. Please fix the mapping. Bug: #496333 ASSIGNED - jjohnstn(a)redhat.com - Run Image Launch Configuration doesn't preserve command quotes > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22629) bzira missing mapping for linux tools 5.1.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22629?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22629: ---------------------------------- Assignee: Nick Boldt (was: Jeff Johnston) > bzira missing mapping for linux tools 5.1. > ------------------------------------------ > > Key: JBIDE-22629 > URL: https://issues.jboss.org/browse/JBIDE-22629 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.4.1.S116 > > > bzira/jiralint is failing on missing version mapping for linux tools 5.1.0 - what release train is 5.1.0 targetd for ? Neon.1 ? > Related log from build fail mails: > {code} > [ERROR] Unknown version for Linux Tools / 5.1.0 > [ERROR] No mapping for '5.1.0'. Please fix the mapping. Bug: #496333 ASSIGNED - jjohnstn(a)redhat.com - Run Image Launch Configuration doesn't preserve command quotes > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21877) Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-21877: ------------------------------------ This is weird because mpc (Marketplace Client) is not part of DevStudio. So in order to reproduce, it installed Neon J2EE and installed DevStudio 10.0.0-GA on top of it but I can't reproduce, mainly because MPC got the fix. Will try with Mars J2EE + DevStudo > Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21877 > URL: https://issues.jboss.org/browse/JBIDE-21877 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: screenshot-1.png > > > When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log > {code} > There was an error retrieving children in the OpenShift explorer > java.lang.NullPointerException > at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124) > at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317) > at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92) > at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113) > at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69) > at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184) > at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43) > at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154) > at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557) > at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275) > at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195) > at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86) > at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108) > at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) > at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134) > at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99) > at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504) > at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236) > at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226) > at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376) > at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59) > at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93) > at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-318) Add privileged support to ContainerLauncher class launch method [EBZ#496515]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-318?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-318: --------------------------------- Assignee: Jeff Johnston > Add privileged support to ContainerLauncher class launch method [EBZ#496515] > ---------------------------------------------------------------------------- > > Key: ERT-318 > URL: https://issues.jboss.org/browse/ERT-318 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Nick Boldt > Assignee: Jeff Johnston > Labels: 5.1.0, Docker, bzira > Fix For: Neon.1 (4.6) > > > Support for the privileged flag is not possible with the current ContainerLauncher.launch method. A change was posted, but it was too late for the major 5.0.0 release. It will be modified for 5.1.0 to simply add API rather than remove or change API. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-317) Run Image Launch Configuration doesn't preserve command quotes [EBZ#496333]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-317?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-317: ------------------------------ Sprint: devex #116 2016/06/15 - 07/05 > Run Image Launch Configuration doesn't preserve command quotes [EBZ#496333] > --------------------------------------------------------------------------- > > Key: ERT-317 > URL: https://issues.jboss.org/browse/ERT-317 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: 5.1.0, Docker, bzira > Fix For: Neon.1 (4.6) > > > The string used for the CMD for a Run Image configuration changes each time it is opened. The first time it strips off one set of quotes, the second time it strips off the next, etc.. > The CMD string should appear the same each time the configuration is opened. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-317) Run Image Launch Configuration doesn't preserve command quotes [EBZ#496333]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-317?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-317: --------------------------------- Assignee: Jeff Johnston (was: Nick Boldt) > Run Image Launch Configuration doesn't preserve command quotes [EBZ#496333] > --------------------------------------------------------------------------- > > Key: ERT-317 > URL: https://issues.jboss.org/browse/ERT-317 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Nick Boldt > Assignee: Jeff Johnston > Labels: 5.1.0, Docker, bzira > Fix For: Neon.1 (4.6) > > > The string used for the CMD for a Run Image configuration changes each time it is opened. The first time it strips off one set of quotes, the second time it strips off the next, etc.. > The CMD string should appear the same each time the configuration is opened. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-318) Add privileged support to ContainerLauncher class launch method [EBZ#496515]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-318?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-318: ------------------------------ Sprint: devex #116 2016/06/15 - 07/05 > Add privileged support to ContainerLauncher class launch method [EBZ#496515] > ---------------------------------------------------------------------------- > > Key: ERT-318 > URL: https://issues.jboss.org/browse/ERT-318 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Nick Boldt > Labels: 5.1.0, Docker, bzira > Fix For: Neon.1 (4.6) > > > Support for the privileged flag is not possible with the current ContainerLauncher.launch method. A change was posted, but it was too late for the major 5.0.0 release. It will be modified for 5.1.0 to simply add API rather than remove or change API. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19081: ------------------------------------- [~dgolovin] as long as the tests referenced by all these tests suites are suffixed with Test, it should be alright. The suites themselves won't be run by tycho (developers can still run them in eclipse if they want) and all individual tests will be picked up. > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.4.x > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- 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: ------------------------------------ Request to get python and pip installed on the two bad slaves: https://engineering.redhat.com/rt/Ticket/Display.html?id=409178 > 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: ------------------------------------ Jobs are configured to run on the following slaves/labels: jiralint-bzira: (RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!ppc64&&!rhts jiralint-daily: (RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!ppc64&&!rhts jiralint-weekly: (RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!ppc64&&!rhts I would need to see the console log from a job which failed in order to be able to remove it from the slave pool used. Re-reading your JIRA report, I see you mention that the snippet is from an email. These appear to be the slaves which are missing pip. {code} dev218-virt4 (RHEL-any mem2G RHEL7 linux general eap-sustaining docker EAP-RHEL7 mwqa_drives_services RHEL beaker mwqa_drives_tools mem4G unix) dev148-virt2 (eap-sustaining docker EAP-RHEL7 mwqa_drives_services mem2G beaker mwqa_drives_tools mem4G) {code} > 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

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