[JBoss JIRA] (JBIDE-25665) It is not possible to update from 4.5.1. to 4.5.2.Final using Check for Update
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25665?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25665:
-------------------------------
Fix Version/s: 4.5.3.AM1
(was: 4.5.2.Final)
> It is not possible to update from 4.5.1. to 4.5.2.Final using Check for Update
> ------------------------------------------------------------------------------
>
> Key: JBIDE-25665
> URL: https://issues.jboss.org/browse/JBIDE-25665
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.2.Final
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM1
>
> Attachments: CheckForUpdates.png
>
>
> It is not possible to update to 4.5.2.Final using "Check for Update". Check for Update is not able to find any remedy for this conflict:
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss JAX-RS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.0.v20180105-1426)
> Software currently installed: JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.feature.feature.group 1.9.101.v20170822-1704)
> Only one of the following can be installed at once:
> JBoss WebServices Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.ui 2.0.0.v20180105-1426)
> JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.ui 1.9.101.v20170822-1704)
> Cannot satisfy dependency:
> From: JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.feature.feature.group 1.9.101.v20170822-1704)
> To: org.jboss.tools.ws.ui [1.9.101.v20170822-1704]
> Cannot satisfy dependency:
> From: JBoss JAX-RS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.0.v20180105-1426)
> To: org.jboss.tools.ws.ui [2.0.0.v20180105-1426]
> {code}
> !CheckForUpdates.png|thumbnail!
> It is maybe caused by separation of SOAP from jbosstools-webservices (JBIDE-24880).
> This process is routinely tested and the test passed on Friday/Monday, but unfortunately I made a mistake. I installed JBT 4.5.1 from Eclipse Marketplace, then I added staging update site and executed Check for Update which passed without any problems. But I didn't realize that JBT 4.5.1 added stable update site for 4.5.1, which was used together with 4.5.2 update site, so it was able to resolve that conflict. So I apologize for this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25666) Pod Log: wont work if I have an invalid oc in prefs and a valid connection ovveride
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25666?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25666:
-------------------------------------
Attachment: build-logs-using-oc-location-in-prefs.png
> Pod Log: wont work if I have an invalid oc in prefs and a valid connection ovveride
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-25666
> URL: https://issues.jboss.org/browse/JBIDE-25666
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: build_log, oc_binary, preferences
> Fix For: 4.5.x
>
> Attachments: build-logs-using-oc-location-in-prefs.png
>
>
> # ASSERT: have the "oc" location set in Eclipse preferences
> # EXEC: start some build in OpenShift (ex. by creating an app via nodejs-mongo-persistent template)
> # EXEC: kill the oc that preferences is pointing to
> # EXEC: set the "Override oc location" for your OpenShift connection to some valid oc binary
> # EXEC: in Properties > Builds: select your build and pick "Build Log"
> Result:
> The "Console" view is opened but instead of the log you'll see the following error (<invalid path> is the path that you have set in preferences:
> {code}
> Does your OpenShift binary location exist? Error starting process: Cannot run program <invalid path to oc from Eclipse preferences>: error=2, No such file or directory
> {code}
> "Build Logs" obviously doesnt honour the oc location override for the connection, it is using the value in the Eclipse preferences.
> Expected result:
> The "Build Log" should use the override in the Connection and show the build log
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25666) Pod Log: wont work if I have an invalid oc in prefs and a valid connection ovveride
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25666?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25666:
-------------------------------------
Description:
# ASSERT: have the "oc" location set in Eclipse preferences
# EXEC: start some build in OpenShift (ex. by creating an app via nodejs-mongo-persistent template)
# EXEC: kill the oc that preferences is pointing to
# EXEC: set the "Override oc location" for your OpenShift connection to some valid oc binary
# EXEC: in Properties > Builds: select your build and pick "Build Log"
Result:
The "Console" view is opened but instead of the log you'll see the following error (<invalid path> is the path that you have set in preferences:
{code}
Does your OpenShift binary location exist? Error starting process: Cannot run program <invalid path to oc from Eclipse preferences>: error=2, No such file or directory
{code}
!build-logs-using-oc-location-in-prefs.png!
"Build Logs" obviously doesnt honour the oc location override for the connection, it is using the value in the Eclipse preferences.
Expected result:
The "Build Log" should use the override in the Connection and show the build log
was:
# ASSERT: have the "oc" location set in Eclipse preferences
# EXEC: start some build in OpenShift (ex. by creating an app via nodejs-mongo-persistent template)
# EXEC: kill the oc that preferences is pointing to
# EXEC: set the "Override oc location" for your OpenShift connection to some valid oc binary
# EXEC: in Properties > Builds: select your build and pick "Build Log"
Result:
The "Console" view is opened but instead of the log you'll see the following error (<invalid path> is the path that you have set in preferences:
{code}
Does your OpenShift binary location exist? Error starting process: Cannot run program <invalid path to oc from Eclipse preferences>: error=2, No such file or directory
{code}
"Build Logs" obviously doesnt honour the oc location override for the connection, it is using the value in the Eclipse preferences.
Expected result:
The "Build Log" should use the override in the Connection and show the build log
> Pod Log: wont work if I have an invalid oc in prefs and a valid connection ovveride
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-25666
> URL: https://issues.jboss.org/browse/JBIDE-25666
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: build_log, oc_binary, preferences
> Fix For: 4.5.x
>
> Attachments: build-logs-using-oc-location-in-prefs.png
>
>
> # ASSERT: have the "oc" location set in Eclipse preferences
> # EXEC: start some build in OpenShift (ex. by creating an app via nodejs-mongo-persistent template)
> # EXEC: kill the oc that preferences is pointing to
> # EXEC: set the "Override oc location" for your OpenShift connection to some valid oc binary
> # EXEC: in Properties > Builds: select your build and pick "Build Log"
> Result:
> The "Console" view is opened but instead of the log you'll see the following error (<invalid path> is the path that you have set in preferences:
> {code}
> Does your OpenShift binary location exist? Error starting process: Cannot run program <invalid path to oc from Eclipse preferences>: error=2, No such file or directory
> {code}
> !build-logs-using-oc-location-in-prefs.png!
> "Build Logs" obviously doesnt honour the oc location override for the connection, it is using the value in the Eclipse preferences.
> Expected result:
> The "Build Log" should use the override in the Connection and show the build log
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25666) Pod Log: wont work if I have an invalid oc in prefs and a valid connection ovveride
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25666?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25666:
-------------------------------------
Labels: build_log oc_binary preferences (was: )
> Pod Log: wont work if I have an invalid oc in prefs and a valid connection ovveride
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-25666
> URL: https://issues.jboss.org/browse/JBIDE-25666
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: build_log, oc_binary, preferences
> Fix For: 4.5.x
>
> Attachments: build-logs-using-oc-location-in-prefs.png
>
>
> # ASSERT: have the "oc" location set in Eclipse preferences
> # EXEC: start some build in OpenShift (ex. by creating an app via nodejs-mongo-persistent template)
> # EXEC: kill the oc that preferences is pointing to
> # EXEC: set the "Override oc location" for your OpenShift connection to some valid oc binary
> # EXEC: in Properties > Builds: select your build and pick "Build Log"
> Result:
> The "Console" view is opened but instead of the log you'll see the following error (<invalid path> is the path that you have set in preferences:
> {code}
> Does your OpenShift binary location exist? Error starting process: Cannot run program <invalid path to oc from Eclipse preferences>: error=2, No such file or directory
> {code}
> !build-logs-using-oc-location-in-prefs.png!
> "Build Logs" obviously doesnt honour the oc location override for the connection, it is using the value in the Eclipse preferences.
> Expected result:
> The "Build Log" should use the override in the Connection and show the build log
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-25666) Pod Log: wont work if I have an invalid oc in prefs and a valid connection ovveride
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-25666:
----------------------------------------
Summary: Pod Log: wont work if I have an invalid oc in prefs and a valid connection ovveride
Key: JBIDE-25666
URL: https://issues.jboss.org/browse/JBIDE-25666
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.5.2.Final
Reporter: Andre Dietisheim
Assignee: Rob Stryker
Fix For: 4.5.x
# ASSERT: have the "oc" location set in Eclipse preferences
# EXEC: start some build in OpenShift (ex. by creating an app via nodejs-mongo-persistent template)
# EXEC: kill the oc that preferences is pointing to
# EXEC: set the "Override oc location" for your OpenShift connection to some valid oc binary
# EXEC: in Properties > Builds: select your build and pick "Build Log"
Result:
The "Console" view is opened but instead of the log you'll see the following error (<invalid path> is the path that you have set in preferences:
{code}
Does your OpenShift binary location exist? Error starting process: Cannot run program <invalid path to oc from Eclipse preferences>: error=2, No such file or directory
{code}
"Build Logs" obviously doesnt honour the oc location override for the connection, it is using the value in the Eclipse preferences.
Expected result:
The "Build Log" should use the override in the Connection and show the build log
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-23288) Users somehow have server configured for as6 shutdown behavior (jmx) and as7+ deployment scanner behavior (mgmt)
by Raphael Ackermann (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23288?page=com.atlassian.jira.plugi... ]
Raphael Ackermann commented on JBIDE-23288:
-------------------------------------------
happens to me frequently. Usually in relation to switching branches and then starting deployment again
> Users somehow have server configured for as6 shutdown behavior (jmx) and as7+ deployment scanner behavior (mgmt)
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23288
> URL: https://issues.jboss.org/browse/JBIDE-23288
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Automated Error Reporting Bot
> Fix For: LATER
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: HIDDEN
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:352)
> at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:291)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:1)
> at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerUtil.executeWithService(JBoss7ManagerUtil.java:136)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.executeWithResult(AS7DeploymentScannerUtility.java:289)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScanners(AS7DeploymentScannerUtility.java:161)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScannersFromServer(AS7DeploymentScannerUtility.java:249)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadScannersFromServer(LocalJBoss7DeploymentScannerAdditions.java:173)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.loadScannersFromServerSafely(LocalJBoss7DeploymentScannerAdditions.java:135)
> at org.jboss.ide.eclipse.as.core.server.internal.v7.LocalJBoss7DeploymentScannerAdditions.ensureScannersRemoved(LocalJBoss7DeploymentScannerAdditions.java:150)
> at org.jboss.ide.eclipse.as.core.server.internal.AbstractDeploymentScannerAdditions.removeAddedDeploymentScanners(AbstractDeploymentScannerAdditions.java:83)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.removeScanners(LocalLegacyShutdownController.java:75)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:58)
> at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:53)
> at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:252)
> at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3688)
> at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3645)
> at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:403)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.expressions | 3.5.0.v20150421-2214 | 3.5.100.v20160418-1621 |
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.5.0.v20150421-2214 |
> | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.12.0.v20160518-1929 |
> | org.eclipse.jst.j2ee | 1.1.850.v201506041749 | 1.1.850.v201506041749 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> | org.eclipse.ui.forms | 3.6.200.v20150506-2029 | 3.6.200.v20150506-2029 |
> | org.eclipse.ui.navigator | 3.6.0.v20150422-0725 | 3.6.100.v20160518-1929 |
> | org.eclipse.wst.common.frameworks | 1.2.200.v201304241450 | 1.2.200.v201304241450 |
> | org.eclipse.wst.server.core | 1.8.0.v201601132216 | 1.8.100.v201605201456 |
> | org.eclipse.wst.server.ui | 1.5.202.v201602111638 | 1.5.304.v201605121430 |
> | org.jboss.ide.eclipse.as.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.3.1.Final-v20151021-0032-B49 |
> | org.jboss.ide.eclipse.as.management.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.3.1.Final-v20151021-0032-B49 |
> | org.jboss.ide.eclipse.as.management.wildfly9 | 3.1.0.Beta2-v20150723-0026-B29 | 3.3.1.Final-v20151021-0032-B49 |
> | org.jboss.ide.eclipse.as.ui | 3.1.0.Beta2-v20150723-0026-B29 | 3.1.1.Final-v20160409-0826-B118 |
> | org.jboss.ide.eclipse.as.wtp.core | 3.1.0.Beta2-v20150723-0026-B29 | 3.3.1.Final-v20151021-0032-B49 |
> | org.jboss.tools.jmx.ui | 1.7.1.Final-v20160409-0826-B118 | 1.8.0.Final-v20160614-2020-B9 |
> Operating Systems:
> | Linux | 2.6.32.3 | 4.7.4.fc24 |
> | MacOSX | 10.11.4 | 10.11.6 |
> | 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/570ce1e8e4b07391bf...] 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)
6 years, 5 months
[JBoss JIRA] (JBIDE-25665) It is not possible to update from 4.5.1. to 4.5.2.Final using Check for Update
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25665?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-25665:
------------------------------------
[~nickboldt] this is not an approach we have followed in the past. We always wanted that our users get notification and upgrade via Check for Updates easily. Doing a fresh install maybe be a burden for them since they can have multiple other plugins installed (not shipped by default with JBT) and will need to reinstall them as well. Does it mean that we don't care in the future? I think we should.
> It is not possible to update from 4.5.1. to 4.5.2.Final using Check for Update
> ------------------------------------------------------------------------------
>
> Key: JBIDE-25665
> URL: https://issues.jboss.org/browse/JBIDE-25665
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.2.Final
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 4.5.2.Final
>
> Attachments: CheckForUpdates.png
>
>
> It is not possible to update to 4.5.2.Final using "Check for Update". Check for Update is not able to find any remedy for this conflict:
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss JAX-RS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.0.v20180105-1426)
> Software currently installed: JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.feature.feature.group 1.9.101.v20170822-1704)
> Only one of the following can be installed at once:
> JBoss WebServices Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.ui 2.0.0.v20180105-1426)
> JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.ui 1.9.101.v20170822-1704)
> Cannot satisfy dependency:
> From: JBoss WebServices Tools 1.9.101.v20170822-1704 (org.jboss.tools.ws.feature.feature.group 1.9.101.v20170822-1704)
> To: org.jboss.tools.ws.ui [1.9.101.v20170822-1704]
> Cannot satisfy dependency:
> From: JBoss JAX-RS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.0.v20180105-1426)
> To: org.jboss.tools.ws.ui [2.0.0.v20180105-1426]
> {code}
> !CheckForUpdates.png|thumbnail!
> It is maybe caused by separation of SOAP from jbosstools-webservices (JBIDE-24880).
> This process is routinely tested and the test passed on Friday/Monday, but unfortunately I made a mistake. I installed JBT 4.5.1 from Eclipse Marketplace, then I added staging update site and executed Check for Update which passed without any problems. But I didn't realize that JBT 4.5.1 added stable update site for 4.5.1, which was used together with 4.5.2 update site, so it was able to resolve that conflict. So I apologize for this issue.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBDS-4671) Errors updating from 11.1.0.GA to latest one
by Roman Martin Gil (JIRA)
Roman Martin Gil created JBDS-4671:
--------------------------------------
Summary: Errors updating from 11.1.0.GA to latest one
Key: JBDS-4671
URL: https://issues.jboss.org/browse/JBDS-4671
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Affects Versions: 11.1.0.GA
Environment: Red Hat JBoss Developer Studio 11.1.0.GA with early access activate.
openjdk version "1.8.0_151" .OpenJDK Runtime Environment (build 1.8.0_151-b12)
Operating System: Fedora 27
Reporter: Roman Martin Gil
Attachments: 01-rhjbds-available-updates.png, 02-rhjbds-about-installation.png, 03-rhjbds-updating-error.png
Since some days I am getting alerts to update my RHJBDS 11.1.0.GA to latest versions however I could not complete anyway.
Everyday I get a update alert with latest versions but it seems that they are not ready to be applied.
After some moments updating the environment I got the following error and stack trace:
{code:java}
An error occurred while collecting items to be installed
session context was:(profile=devstudio, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,com.jboss.devstudio.core,11.3.0.AM1-v20180125-1048-B1900
No repository found containing: osgi.bundle,com.jboss.devstudio.core.capabilities,11.3.0.v20180124-1725
No repository found containing: osgi.bundle,com.jboss.devstudio.core.central,11.3.0.AM1-v20180125-1048-B1900
No repository found containing: osgi.bundle,com.jboss.devstudio.core.project.examples,11.3.0.v20180124-1725
No repository found containing: osgi.bundle,com.jboss.devstudio.core.usage.branding,11.3.0.v20180124-1725
No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.capabilities.feature,11.3.0.v20180124-1725
No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.feature,11.3.0.v20180125-1048
No repository found containing: binary,com.jboss.devstudio.core.package.executable.gtk.linux.x86_64,11.3.0.AM1-v20180125-1048-B1900
No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.rpm.feature,11.3.0.v20180125-1048
No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.core.rpmdeps.feature,11.3.0.v20180124-1725
No repository found containing: org.eclipse.update.feature,com.jboss.devstudio.fuse.feature,11.3.0.v20180124-1725
{code}
I attached some screenshots with the process.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months