[JBoss JIRA] (JBIDE-21877) Make error message shown in OpenShift Explorer for outdated token more user friendly
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21877:
---------------------------------------
I don't suggest to cover issue and show "user friendly message". That would not be good. I am suggesting to customize tree item under a connection representing an issue and in the same time keep stack trace in error log.
> 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
> Labels: connection, openshift_v3
>
> 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)
10 years
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Marcel Bruch commented on JBDS-3566:
------------------------------------
Can you provide me a link to the eclipse installation/installer-bundle you use? I'll try myself and see what's missing.
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: aeri-in-jbds91.png, aeri-not-firing.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21821) JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0, which installs jgit 4.0; this breaks egit 4.1.1 views when JBT 4.3.0 or JBDS 9.0.0 are installed into Mars.2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21821:
------------------------------------
Blog is live. http://tools.jboss.org/blog/ga-egit411-fix-mars.2.html
> JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0, which installs jgit 4.0; this breaks egit 4.1.1 views when JBT 4.3.0 or JBDS 9.0.0 are installed into Mars.2
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21821
> URL: https://issues.jboss.org/browse/JBIDE-21821
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, marketplace
> Reporter: Thomas Mäder
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.0.Final, 4.3.1.CR1
>
> Attachments: FrameworkEvent ERROR.txt, jbt-error, jgit40_41_JBDS.installed.txt, jgit40_41_JBT.installed.txt
>
>
> Installing Red Hat JBoss Developer Studio 9.0.0GA into a fresh Eclipse 4.5.2 (for Eclipse Committers) causes Egit to break.
> # Install Eclipse 4.5.2
> # In the Marketplace, search for "jboss developer studio"
> # You get a single result: Red Hat JBoss Developer Studio 9.0.0 GA
> # Install it
> # Restart
> # Observe: the EGit views and preferences are missing
> # Observe: you get messages in the Eclipse error log concerning a dependency version incompatibility
> -----
> JBT 4.3.0.Final / JBDS 9.0.0.GA target platforms include org.eclipse.egit.importer.ui 4.0.0.201506090130-r (Mars.1 version), which installs jgit 4.0.3.201509231615-r (Mars.1 version); this breaks egit 4.1.1 views when installed into Mars.2, because Mars.2 site does not include org.eclipse.egit.ui.importer 4.1.1.201511131810-r, and you confuse egit when you have both jgit 4.0 and 4.1 installed, disabling views and preferences.
> Solution proposed is to add org.eclipse.egit.ui.importer 4.1.1.201511131810-r to the composite site from which JBT 4.3.0.Final and JBDS 9.0.0.GA are installed, so that when org.eclipse.egit.ui.importer is installed, p2 can select the 4.1.1 version instead of the 4.0.0 version.
> I would want to pull a mirror of http://download.eclipse.org/egit/updates-4.1.1/ onto download.jboss.org if we're cool with this solution.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3566:
-----------------------------
Attachment: aeri-not-firing.png
Maybe the problem is my system (Fedora 20 in a VBox VM, using Oracle JDK 8u60), but I still can't get AERI to fire after installing the Manual Tests Feature.
I do see events in my Error Log, but nothing is alerted via AERI.
[^aeri-not-firing.png]
Re: the esc-key bug, I figured I'd mention it here and if it was an unreported snafu I could open a new issue. Just thought I'd ask the implied question, "has this already been reported?"
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: aeri-in-jbds91.png, aeri-not-firing.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21874) OpenShift master branch is not compiling any more
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21874?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21874 at 3/16/16 10:48 AM:
--------------------------------------------------------------------
Those 2 tests also fail for me in maintenance (jbosstools-4.3.x). The assertions that are wrong were changed quite some time ago (1y 8 mnth):
the following commint for JBIDE-17879 with the following [PR|https://github.com/adietish/jbosstools-openshift/commit/87310fb463ce01...]
I dont get why the tests were blue since then.
was (Author: adietish):
Those 2 tests also fail for me in maintenance (jbosstools-4.3.x). The assertions that are wrong were changed quite some time ago (1y 8 mnth):
https://github.com/adietish/jbosstools-openshift/commit/87310fb463ce01617...
I dont get why the tests were blue since then.
> OpenShift master branch is not compiling any more
> -------------------------------------------------
>
> Key: JBIDE-21874
> URL: https://issues.jboss.org/browse/JBIDE-21874
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: build, jenkins
> Fix For: 4.4.0.Alpha1
>
>
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/1199/console}
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 11:47 min
> [INFO] Finished at: 2016-03-15T22:47:06-04:00
> [INFO] Final Memory: 117M/733M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.24.0:compile (default-compile) on project org.jboss.tools.openshift.express.ui: Compilation failure: Compilation failure:
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[44]
> [ERROR] import org.eclipse.egit.core.AdaptableFileTreeIterator;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.eclipse.egit.core.AdaptableFileTreeIterator cannot be resolved
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[1253]
> [ERROR] AdaptableFileTreeIterator fileTreeIterator = new AdaptableFileTreeIterator(
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] AdaptableFileTreeIterator cannot be resolved to a type
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[1253]
> [ERROR] AdaptableFileTreeIterator fileTreeIterator = new AdaptableFileTreeIterator(
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] AdaptableFileTreeIterator cannot be resolved to a type
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[1452]
> [ERROR] return getComparator().compare(e1, e2);
> [ERROR] ^^^^^^^
> [ERROR] The method compare(capture#5-of ? super String, capture#5-of ? super String) in the type Comparator<capture#5-of ? super String> is not applicable for the arguments (Object, Object)
> [ERROR] 4 problems (4 errors)
> [ERROR] -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21874) OpenShift master branch is not compiling any more
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21874?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21874:
------------------------------------------
Those 2 tests also fail for me in maintenance (jbosstools-4.3.x). The assertions that are wrong were changed quite some time ago (1y 8 mnth):
https://github.com/adietish/jbosstools-openshift/commit/87310fb463ce01617...
I dont get why the tests were blue since then.
> OpenShift master branch is not compiling any more
> -------------------------------------------------
>
> Key: JBIDE-21874
> URL: https://issues.jboss.org/browse/JBIDE-21874
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: build, jenkins
> Fix For: 4.4.0.Alpha1
>
>
> {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/1199/console}
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 11:47 min
> [INFO] Finished at: 2016-03-15T22:47:06-04:00
> [INFO] Final Memory: 117M/733M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.24.0:compile (default-compile) on project org.jboss.tools.openshift.express.ui: Compilation failure: Compilation failure:
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[44]
> [ERROR] import org.eclipse.egit.core.AdaptableFileTreeIterator;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.eclipse.egit.core.AdaptableFileTreeIterator cannot be resolved
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[1253]
> [ERROR] AdaptableFileTreeIterator fileTreeIterator = new AdaptableFileTreeIterator(
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] AdaptableFileTreeIterator cannot be resolved to a type
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[1253]
> [ERROR] AdaptableFileTreeIterator fileTreeIterator = new AdaptableFileTreeIterator(
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] AdaptableFileTreeIterator cannot be resolved to a type
> [ERROR] /mnt/hudson_workspace/workspace/jbosstools-openshift_master/sources/plugins/org.jboss.tools.openshift.express.ui/src/org/jboss/tools/openshift/express/internal/ui/server/CommitDialog.java:[1452]
> [ERROR] return getComparator().compare(e1, e2);
> [ERROR] ^^^^^^^
> [ERROR] The method compare(capture#5-of ? super String, capture#5-of ? super String) in the type Comparator<capture#5-of ? super String> is not applicable for the arguments (Object, Object)
> [ERROR] 4 problems (4 errors)
> [ERROR] -> [Help 1]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21877) Make error message shown in OpenShift Explorer for outdated token more user friendly
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21877:
-----------------------------------------------
org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator does not check requestingURL for null.
org.apache.http.impl.client.SystemDefaultCredentialsProvider uses Authenticator.requestPasswordAuthentication() that does not set URL so that getRequestingURL() returns null.
It is not good to try to catch NPE to make user friendly conclusions. Maybe issue can be fixed by overriding SystemDefaultCredentialsProvider in openshift-restclient-java.
> 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
> Labels: connection, openshift_v3
>
> 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)
10 years
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Marcel Bruch commented on JBDS-3566:
------------------------------------
> And, I discovered that if you hit ESC on...
Yes, fixed in https://git.eclipse.org/c/epp/org.eclipse.epp.logging.git/commit/?id=2dcc...
Please consider using separate issues for different things.
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: aeri-in-jbds91.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Marcel Bruch commented on JBDS-3566:
------------------------------------
For testing purpose:
Install "EPP Logging Manual Tests Feature" from [1]. This will add a toolbar menu with several actions that trigger (synthetic) exceptions - some of them are labeled with "JBoss".
Note, the resulting error report is not complete. It certainly does not contain any bundle information. But it merely sends error reports to the JBoss server.
If you'd like to see other test cases, feel free to contribute them to the manual tests project.
[1] http://download.eclipse.org/technology/epp/logging/milestones
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: aeri-in-jbds91.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21869:
---------------------------------------
[~fbricon] moving to minor based on andy's comments. We should verify if getting logs using the binary produces the same results.
> Encoding issue in when streaming Build Logs to the console
> ----------------------------------------------------------
>
> Key: JBIDE-21869
> URL: https://issues.jboss.org/browse/JBIDE-21869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Priority: Minor
>
> Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu.
> It'll start to spew weird characters eventually :
> {noformat}
> I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ...
> I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ...
> I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble"
> I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run"
> I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
> ---> Installing application source
> ---> Building your Node application from source
> E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok
> E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13
> E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40
> ...
> E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1
> ejs(a)2.4.1 node_modules/ejs
> express(a)4.13.4 node_modules/express
> ��������� escape-html(a)1.0.3
> ��������� array-flatten(a)1.1.1
> ��������� utils-merge(a)1.0.0
> ��������� cookie-signature(a)1.0.6
> ��������� merge-descriptors(a)1.0.1
> ��������� fresh(a)0.3.0
> ��������� methods(a)1.1.2
> ��������� range-parser(a)1.0.3
> ��������� vary(a)1.0.1
> ��������� path-to-regexp(a)0.1.7
> ��������� cookie(a)0.1.5
> ��������� parseurl(a)1.3.1
> ��������� content-type(a)1.0.1
> ��������� etag(a)1.7.0
> ��������� content-disposition(a)0.5.1
> ��������� serve-static(a)1.10.2
> ��������� depd(a)1.1.0
> ��������� qs(a)4.0.0
> ��������� finalhandler(a)0.4.1 (unpipe(a)1.0.0)
> ��������� on-finished(a)2.3.0 (ee-first(a)1.1.1)
> ��������� debug(a)2.2.0 (ms(a)0.7.1)
> ��������� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
> ��������� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
> ��������� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
> ��������� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
> mongodb(a)2.1.8 node_modules/mongodb
> ��������� es6-promise(a)3.0.2
> ��������� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0)
> ��������� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
> E0315 10:39:27.684535 1 util.go:91] npm info ok
> I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image
> I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ...
> {noformat}
> I'm running on OSX
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years