June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20051) As a I user I want to be able to automatically install webhooks into my GitHub repository

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20051?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20051: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > As a I user I want to be able to automatically install webhooks into my GitHub repository > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20051 > URL: https://issues.jboss.org/browse/JBIDE-20051 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.5.x > > Original Estimate: 4 days > Remaining Estimate: 4 days > > I want to be able to automatically install webhooks into my github repository from Eclipse. > We can detect if a project has a github url. > We can probably detect the user github credentials, or ask the user his credentials before trying to install the webhook. > There must be a GitHub API that allows to then add webhooks automatically. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18983) Project cannot be built. Possible open file handle

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18983?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18983: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Project cannot be built. Possible open file handle > -------------------------------------------------- > > Key: JBIDE-18983 > URL: https://issues.jboss.org/browse/JBIDE-18983 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, maven > Affects Versions: 4.2.1.Final > Environment: luna x64 windows 8.1 x64 > java 8u25 x64 > Reporter: Cody Lerum > Assignee: Jeff MAURY > Fix For: 4.5.x > > > Frequently when working in a Java EE7 project I will get an error like. > "The project was not built due to "Could not delete '/gp-server/target/classes/META-INF`.". Fix the problem, then try refreshing this project and building since it may be inconsistent. > I've looked into a process explorer in windows and then this case is happening there is always a javaw.exe process with a file handle to "V:\workspace\gp-server\target\classes\META-INF\persistence.xml > It looks like either jboss tools or eclipse is holding on to a file handle for this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 updated JBIDE-21877: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > 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: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: connection_wizard, openshift_v3 > Fix For: 4.5.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 (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20763) Provide 'oc' binaries per platform

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20763?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20763: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Provide 'oc' binaries per platform > ---------------------------------- > > Key: JBIDE-20763 > URL: https://issues.jboss.org/browse/JBIDE-20763 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Labels: oc_binary, preferences > Fix For: 4.5.x > > > Instead of forcing the user to search, download and install the 'oc' library manually before being able to use port forwarding or log streaming, the platform-related binary could be installed automatically. > Possible implementation: > - define the oc binary URLs in stacks.yaml > - on openshift 3 plugin startup, check if oc binary is set in preferences > - if not set trigger background job to d/l oc binary matching current platform, and update preferences, else, do nothing. > [~maxandersen] does it correspond to what you had in mind? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18678) Make dependencies to org.jboss.tools.usage optional

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18678?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18678: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Make dependencies to org.jboss.tools.usage optional > --------------------------------------------------- > > Key: JBIDE-18678 > URL: https://issues.jboss.org/browse/JBIDE-18678 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim, usage > Affects Versions: 4.2.0.CR1 > Reporter: Kaloyan Raev > Assignee: Jeff MAURY > Fix For: 4.5.x > > > I am interested in adopting the CordovaSim feature in our product. However, most of the browsersim bundles have a strong dependency to org.jboss.tools.usage bundle, which force a Usage Reporting popup on startup. I want to avoid this and have the org.jboss.tools.usage excluded from my build. > Is it possible to make the dependencies to org.jboss.tools.usage optional? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22893) NoStackTrace in ChainedDiscoveryStrategy.performDiscovery

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22893?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22893: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > NoStackTrace in ChainedDiscoveryStrategy.performDiscovery > --------------------------------------------------------- > > Key: JBIDE-22893 > URL: https://issues.jboss.org/browse/JBIDE-22893 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.3.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Fred Bricon > Fix For: 4.5.x > > > The following problem was reported via the automated error reporting: > Message: HIDDEN > {noformat} > com.ctrlflow.aer.NoStackTrace: HIDDEN > at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:83) > at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114) > at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107) > at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:45) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > The reporter(s) left the following comment(s): > --- Ana Paula Lopes wrote on [196d|https://redhat.ctrlflow.com/reviewers/#!/incidents/57a23a15e4b0fe642...]: --- > incomplete installation > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.12.0.v20160518-1929 | > | org.eclipse.mylyn.discovery.core | 3.16.0.v20150526-1951 | 3.20.2.v20160630-1640 | > | org.jboss.tools.central | 2.0.0.Final-v20151001-1531-B45 | 2.1.1.v20160711-1005 | > | org.jboss.tools.discovery.core | 1.0.0.Final-v20151001-1531-B45 | 1.2.1.v20160614-2135 | > Operating Systems: > | Linux | 2.6.32.1 | 4.6.3.fc24 | > | MacOSX | 10.9.0 | 10.11.6 | > | Windows | 6.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5716931fe4b052a77c...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24174) When deploying user should be able to set the health checks (readiness and liveness)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24174?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24174: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > When deploying user should be able to set the health checks (readiness and liveness) > ------------------------------------------------------------------------------------ > > Key: JBIDE-24174 > URL: https://issues.jboss.org/browse/JBIDE-24174 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v2, wizard > Fix For: 4.5.x > > > Note: this is not yet supported with the OCP web console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24379) javaee tests failing for linux, windows and osx

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24379?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24379: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > javaee tests failing for linux, windows and osx > ----------------------------------------------- > > Key: JBIDE-24379 > URL: https://issues.jboss.org/browse/JBIDE-24379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, jsf, seam2 > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.5.x > > Attachments: javaee-test-failures.png, javaee-test-failures_last_pass_jan26.png > > > JavaEE tests have been failing for months. > Please investigate. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21448) Port Forwarding: Allow port-forwarding of ports not defined on pod metadata

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21448?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21448: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Port Forwarding: Allow port-forwarding of ports not defined on pod metadata > --------------------------------------------------------------------------- > > Key: JBIDE-21448 > URL: https://issues.jboss.org/browse/JBIDE-21448 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jiri Pechanec > Priority: Critical > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.5.x > > > Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too. > And example is EAP CLI -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24180) Command to toggle pause/resume deployment

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24180?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24180: ------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Command to toggle pause/resume deployment > ----------------------------------------- > > Key: JBIDE-24180 > URL: https://issues.jboss.org/browse/JBIDE-24180 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: openshift, openshift_v3 > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017