[JBoss JIRA] (JBIDE-24411) Explorer: Automatically refresh the connection after correcting credentials in "edit connection" wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24411?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24411:
------------------------------------------
This is duplicate to JBIDE-25590. JBIDE-25590 was fixed and verified.
> Explorer: Automatically refresh the connection after correcting credentials in "edit connection" wizard
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24411
> URL: https://issues.jboss.org/browse/JBIDE-24411
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: explorer, openshift_v3
> Fix For: 4.5.3.Final
>
>
> Currently if I have an OpenSHift connection in OpenSHift Explorer which have bad credentials, if I expand it i have a little error message in the tree (which is nice)
> So I right-click -> Edit connection... I update my connection parameters and when I click finish, in the tree I still have the error. I need to manually right-click -> refresh.
> it would be nice to refresh automatically the tree when the connection has been edited
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBDS-3987) CoreException below RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call (thrown in RepositoryStatusHelper.wrap)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3987?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-3987:
--------------------------------
Assignee: Jeff MAURY (was: Nick Boldt)
> CoreException below RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call (thrown in RepositoryStatusHelper.wrap)
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3987
> URL: https://issues.jboss.org/browse/JBDS-3987
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 9.1.0.GA
> Reporter: Automated Error Reporting Bot
> Assignee: Jeff MAURY
> Fix For: LATER
>
> Attachments: Screen Shot 2016-08-08 at 9.51.05 AM.png
>
>
> The following problem was reported via the automated error reporting:
> Message: Cannot download bundle at https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.1...: null
> {noformat}
> org.eclipse.core.runtime.CoreException:
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryStatusHelper.wrap(RepositoryStatusHelper.java:177)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.checkException(FileReader.java:504)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:435)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:358)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(null:-2)
> at sun.reflect.NativeMethodAccessorImpl.invoke(null:-1)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1)
> at java.lang.reflect.Method.invoke(null:-1)
> at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
> at java.util.concurrent.FutureTask.run(null:-1)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(null:-1)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(null:-1)
> at java.lang.Thread.run(null:-1)
> {noformat}
> Bundles:
> | org.eclipse.equinox.p2.transport.ecf | 1.1.100.v20150521-1342 | 1.1.200.v20160606-1311 |
> | org.eclipse.mylyn.discovery.core | 3.7.1.v20120425-0100 | 3.20.2.v20160630-1640 |
> | org.eclipse.oomph.p2.core | 1.1.0.v20150610-1534 | 1.4.0.v20160606-0856 |
> | org.jboss.tools.discovery.core | 1.0.1.Final-v20160401-1059-B103 | 1.1.0.Final-v20160613-2000-B8 |
> Operating Systems:
> | Linux | 3.0.101 | 4.6.3.fc24 |
> | MacOSX | 10.11.4 | 10.11.4 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5718e82fe4b0cd449c...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-24411) Explorer: Automatically refresh the connection after correcting credentials in "edit connection" wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24411?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-24411:
----------------------------------------
Assignee: Andre Dietisheim
> Explorer: Automatically refresh the connection after correcting credentials in "edit connection" wizard
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24411
> URL: https://issues.jboss.org/browse/JBIDE-24411
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: explorer, openshift_v3
> Fix For: 4.5.3.Final
>
>
> Currently if I have an OpenSHift connection in OpenSHift Explorer which have bad credentials, if I expand it i have a little error message in the tree (which is nice)
> So I right-click -> Edit connection... I update my connection parameters and when I click finish, in the tree I still have the error. I need to manually right-click -> refresh.
> it would be nice to refresh automatically the tree when the connection has been edited
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBDS-3987) [AERI] CoreException below RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call (thrown in RepositoryStatusHelper.wrap)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3987?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3987:
-----------------------------
Summary: [AERI] CoreException below RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call (thrown in RepositoryStatusHelper.wrap) (was: CoreException below RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call (thrown in RepositoryStatusHelper.wrap))
> [AERI] CoreException below RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call (thrown in RepositoryStatusHelper.wrap)
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3987
> URL: https://issues.jboss.org/browse/JBDS-3987
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 9.1.0.GA
> Reporter: Automated Error Reporting Bot
> Assignee: Jeff MAURY
> Fix For: LATER
>
> Attachments: Screen Shot 2016-08-08 at 9.51.05 AM.png
>
>
> The following problem was reported via the automated error reporting:
> Message: Cannot download bundle at https://devstudio.redhat.com/9.0/stable/updates/discovery.earlyaccess/9.1...: null
> {noformat}
> org.eclipse.core.runtime.CoreException:
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryStatusHelper.wrap(RepositoryStatusHelper.java:177)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.checkException(FileReader.java:504)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:435)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:358)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(null:-2)
> at sun.reflect.NativeMethodAccessorImpl.invoke(null:-1)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1)
> at java.lang.reflect.Method.invoke(null:-1)
> at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
> at java.util.concurrent.FutureTask.run(null:-1)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(null:-1)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(null:-1)
> at java.lang.Thread.run(null:-1)
> {noformat}
> Bundles:
> | org.eclipse.equinox.p2.transport.ecf | 1.1.100.v20150521-1342 | 1.1.200.v20160606-1311 |
> | org.eclipse.mylyn.discovery.core | 3.7.1.v20120425-0100 | 3.20.2.v20160630-1640 |
> | org.eclipse.oomph.p2.core | 1.1.0.v20150610-1534 | 1.4.0.v20160606-0856 |
> | org.jboss.tools.discovery.core | 1.0.1.Final-v20160401-1059-B103 | 1.1.0.Final-v20160613-2000-B8 |
> Operating Systems:
> | Linux | 3.0.101 | 4.6.3.fc24 |
> | MacOSX | 10.11.4 | 10.11.4 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5718e82fe4b0cd449c...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-24411) Explorer: Automatically refresh the connection after correcting credentials in "edit connection" wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24411?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24411:
-------------------------------------
Fix Version/s: 4.5.3.Final
(was: 4.5.x)
> Explorer: Automatically refresh the connection after correcting credentials in "edit connection" wizard
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24411
> URL: https://issues.jboss.org/browse/JBIDE-24411
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: explorer, openshift_v3
> Fix For: 4.5.3.Final
>
>
> Currently if I have an OpenSHift connection in OpenSHift Explorer which have bad credentials, if I expand it i have a little error message in the tree (which is nice)
> So I right-click -> Edit connection... I update my connection parameters and when I click finish, in the tree I still have the error. I need to manually right-click -> refresh.
> it would be nice to refresh automatically the tree when the connection has been edited
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-25301) [release] externalize common properties to parameterize jobs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25301?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25301:
-------------------------------
Sprint: devex #147 April 2018
> [release] externalize common properties to parameterize jobs
> ------------------------------------------------------------
>
> Key: JBIDE-25301
> URL: https://issues.jboss.org/browse/JBIDE-25301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.5.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.Final
>
>
> As in JBIDE-25137, we can externalize properties used in Jenkins to run jobs so the jobs are more parameterized.
> for example we could set these params in the jbosstools-jenkins.properties files:
> {code}TARGET_PLATFORM_VERSION_MIN=
> TARGET_PLATFORM_VERSION_MAX=
> TARGET_PLATFORM_CENTRAL_MAX=
> {code}
> Or we could simply remove them and source them from the parent pom.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-24311) Application wizard: is loading templates even if I go back
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24311?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24311:
-------------------------------------
Description:
# ASSERT: have a openshift server (using the internal instance works better since it's remote, requests take more time)
# EXEC: launch application wizard
# EXEC: select a template and hit "Next >" and end up in the "Template Parameters" page
# EXEC: hit "< Back"
Result:
page "Select Template" is displayed, mouse turns "hoursglass" and the page shows a progress bar indicating that the page is loading it's resources.
Expected result:
the page "Select Template" should only load upon initial display. Every subsequent display of the very same page should used cached resources, not load them again and again.
> Application wizard: is loading templates even if I go back
> ----------------------------------------------------------
>
> Key: JBIDE-24311
> URL: https://issues.jboss.org/browse/JBIDE-24311
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Andre Dietisheim
> Priority: Minor
> Fix For: 4.5.x
>
>
> # ASSERT: have a openshift server (using the internal instance works better since it's remote, requests take more time)
> # EXEC: launch application wizard
> # EXEC: select a template and hit "Next >" and end up in the "Template Parameters" page
> # EXEC: hit "< Back"
> Result:
> page "Select Template" is displayed, mouse turns "hoursglass" and the page shows a progress bar indicating that the page is loading it's resources.
> Expected result:
> the page "Select Template" should only load upon initial display. Every subsequent display of the very same page should used cached resources, not load them again and again.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months