[JBoss JIRA] (JBIDE-25609) Properties: certain tabs are missing icons
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25609?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-25609:
----------------------------------
Assignee: Jeff MAURY
> Properties: certain tabs are missing icons
> ------------------------------------------
>
> Key: JBIDE-25609
> URL: https://issues.jboss.org/browse/JBIDE-25609
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: properties
> Fix For: 4.5.x
>
> Attachments: image-2018-01-23-10-16-06-140.png, image-2018-01-23-10-17-20-304.png, screenshot-2.png
>
>
> The tabs in the properties view for OpenShift feature an icon and an explanatory label.
> !screenshot-2.png!
> Some of the tabs are missing their icon:
> * Build Configs
> !image-2018-01-23-10-16-06-140.png!
> (icon exists in org.jboss.tools.openshift.ui/icons: !image-2018-01-23-10-17-20-304.png!)
> * Deployments (icon missing?)
> * Deployment Configs (icon missing?)
> * Events (icon missing?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25609) Properties: certain tabs are missing icons
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25609?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25609:
-------------------------------
Sprint: devex #147 April 2018
> Properties: certain tabs are missing icons
> ------------------------------------------
>
> Key: JBIDE-25609
> URL: https://issues.jboss.org/browse/JBIDE-25609
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: properties
> Fix For: 4.5.x
>
> Attachments: image-2018-01-23-10-16-06-140.png, image-2018-01-23-10-17-20-304.png, screenshot-2.png
>
>
> The tabs in the properties view for OpenShift feature an icon and an explanatory label.
> !screenshot-2.png!
> Some of the tabs are missing their icon:
> * Build Configs
> !image-2018-01-23-10-16-06-140.png!
> (icon exists in org.jboss.tools.openshift.ui/icons: !image-2018-01-23-10-17-20-304.png!)
> * Deployments (icon missing?)
> * Deployment Configs (icon missing?)
> * Events (icon missing?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25857) Add support for images import/export in CDK/minishift adapter
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-25857:
----------------------------------
Summary: Add support for images import/export in CDK/minishift adapter
Key: JBIDE-25857
URL: https://issues.jboss.org/browse/JBIDE-25857
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: cdk
Affects Versions: 4.5.3.Final
Reporter: Jeff MAURY
Assignee: Rob Stryker
Fix For: 4.5.x
Would be fine if we could manage images export/import for the CDK/Minishift server adapter. This is how it could be implemented:
* in the UI we could display the list of available images (using the Docker connection)
* in the UI we could also display the list of cached images (from the minishift images list command)
Then using context menu we could import/export images when one of them is selected
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBDS-4690) Import Spring Starter Project shows error
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBDS-4690?page=com.atlassian.jira.plugin.... ]
Josef Kopriva commented on JBDS-4690:
-------------------------------------
[~nickboldt] I have installed spring from http://dist.springsource.com/release/TOOLS/update/e4.7 and afterwards Spring Starter Project has been imported without errors.
> Import Spring Starter Project shows error
> -----------------------------------------
>
> Key: JBDS-4690
> URL: https://issues.jboss.org/browse/JBDS-4690
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: 3rd-party-certification
> Affects Versions: 11.3.0.AM3
> Environment: F28
> +
> Red Hat JBoss Developer Studio
> Version: 11.3.0.AM3
> Build id: AM3-v20180322-1027-B2194
> Build date: 20180322-1027
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
>
> {code:java}
> null
> org.springframework.ide.eclipse.beans.core
> Error
> Fri Mar 23 15:35:53 CET 2018
> Problems occurred when invoking code from plug-in: "org.springframework.ide.eclipse.beans.core".
> java.lang.NoSuchMethodError: org.springframework.util.Assert.state(ZLjava/util/function/Supplier;)V
> at org.springframework.boot.autoconfigure.cache.CacheConfigurations.getConfigurationClass(CacheConfigurations.java:55)
> at org.springframework.boot.autoconfigure.cache.CacheAutoConfiguration$CacheConfigurationImportSelector.selectImports(CacheAutoConfiguration.java:169)
> at org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:517)
> at org.springframework.context.annotation.ConfigurationClassParser.doProcessConfigurationClass(ConfigurationClassParser.java:286)
> at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:237)
> at org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:536)
> at org.springframework.context.annotation.ConfigurationClassParser.processDeferredImportSelectors(ConfigurationClassParser.java:481)
> at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:191)
> at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:321)
> at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:88)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$3.run(BeansJavaConfig.java:332)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.executePostProcessor(BeansJavaConfig.java:321)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.access$5(BeansJavaConfig.java:319)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:233)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (ERT-614) Add error message for wrong pom [EBZ#532696]
by Friendly Jira Robot (JIRA)
[ https://issues.jboss.org/browse/ERT-614?page=com.atlassian.jira.plugin.sy... ]
Friendly Jira Robot updated ERT-614:
------------------------------------
Component/s: WTP Source Editing
(was: m2e)
> Add error message for wrong pom [EBZ#532696]
> --------------------------------------------
>
> Key: ERT-614
> URL: https://issues.jboss.org/browse/ERT-614
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Source Editing
> Reporter: Friendly Jira Robot
> Labels: bzira, ui
>
> Created attachment 273233
> Screenshot
> Accidently I create a wrong pom without the <project> tag.
> Example pom.xml:
> ------
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.vogella.maven</groupId>
> <artifactId>com.vogella.maven.executablejar</artifactId>
> <version>0.1.0-SNAPSHOT</version>
> <packaging>jar</packaging>
> ------
> m2e showed me an error marker in the editor but no problem marker in the Problems view. Also the marker had no error message. I would expect at least a hover text with "Invalid format of the pom" for something similar.
> See screenshot.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBDS-4690) Import Spring Starter Project shows error
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4690?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4690:
----------------------------------
Can you try installing a newer version of Spring 3.9.3 from here?
http://dist.springsource.com/release/TOOLS/update/e4.7
or if that doesn't fix the problem, maybe it's fixed in a newer CI version (3.9.4) ?
http://dist.springframework.org/snapshot/IDE/nightly/
> Import Spring Starter Project shows error
> -----------------------------------------
>
> Key: JBDS-4690
> URL: https://issues.jboss.org/browse/JBDS-4690
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: 3rd-party-certification
> Affects Versions: 11.3.0.AM3
> Environment: F28
> +
> Red Hat JBoss Developer Studio
> Version: 11.3.0.AM3
> Build id: AM3-v20180322-1027-B2194
> Build date: 20180322-1027
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
>
> {code:java}
> null
> org.springframework.ide.eclipse.beans.core
> Error
> Fri Mar 23 15:35:53 CET 2018
> Problems occurred when invoking code from plug-in: "org.springframework.ide.eclipse.beans.core".
> java.lang.NoSuchMethodError: org.springframework.util.Assert.state(ZLjava/util/function/Supplier;)V
> at org.springframework.boot.autoconfigure.cache.CacheConfigurations.getConfigurationClass(CacheConfigurations.java:55)
> at org.springframework.boot.autoconfigure.cache.CacheAutoConfiguration$CacheConfigurationImportSelector.selectImports(CacheAutoConfiguration.java:169)
> at org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:517)
> at org.springframework.context.annotation.ConfigurationClassParser.doProcessConfigurationClass(ConfigurationClassParser.java:286)
> at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:237)
> at org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:536)
> at org.springframework.context.annotation.ConfigurationClassParser.processDeferredImportSelectors(ConfigurationClassParser.java:481)
> at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:191)
> at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:321)
> at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:88)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$3.run(BeansJavaConfig.java:332)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.executePostProcessor(BeansJavaConfig.java:321)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.access$5(BeansJavaConfig.java:319)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:233)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25856) Can't update from JBT 4.5.2.Final to 4.5.3.AM3 using Check for Updates
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25856?page=com.atlassian.jira.plugi... ]
Lukáš Valach updated JBIDE-25856:
---------------------------------
Attachment: InstallNewSoftware_ShowOriginalErrors.png
InstallNewSoftware_Update.png
InstallNewSoftware_Keep.png
> Can't update from JBT 4.5.2.Final to 4.5.3.AM3 using Check for Updates
> ----------------------------------------------------------------------
>
> Key: JBIDE-25856
> URL: https://issues.jboss.org/browse/JBIDE-25856
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.2.AM3
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 4.5.3.Final
>
> Attachments: CheckForUpdates.png, InstallNewSoftware_Keep.png, InstallNewSoftware_ShowOriginalErrors.png, InstallNewSoftware_Update.png
>
>
> I tested an update form Oxygen2+JBT 4.5.2.Final to JBT 4.5.3.AM3. When I went through Check For Updates I got this error:
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss JAX-RS Tools 2.0.1.v20180311-2201 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.1.v20180311-2201)
> Software currently installed: JBoss JAX-WS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxws.feature.feature.group 2.0.0.v20180105-1426)
> 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 2.0.1.v20180311-2201 (org.jboss.tools.ws.ui 2.0.1.v20180311-2201)
> Cannot satisfy dependency:
> From: JBoss JAX-RS Tools 2.0.1.v20180311-2201 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.1.v20180311-2201)
> To: org.jboss.tools.ws.ui [2.0.1.v20180311-2201]
> Cannot satisfy dependency:
> From: JBoss JAX-WS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxws.feature.feature.group 2.0.0.v20180105-1426)
> To: org.jboss.tools.ws.ui [2.0.0.v20180105-1426]
> {code}
> If my understanding is correct, the eclipse plans to update JAX-RS but doesn't plan to update JAX-WS.
> I know that we fixed similar issue recently in JBIDE-25665.
> The "Check for Updates" doesn't offer any remediation action but Install new Software offers nice solution.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25856) Can't update from JBT 4.5.2.Final to 4.5.3.AM3 using Check for Updates
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25856?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25856:
-------------------------------
Description:
I tested an update form Oxygen2+JBT 4.5.2.Final to JBT 4.5.3.AM3. When I went through Check For Updates I got this error:
{code}
Cannot complete the install because of a conflicting dependency.
Software being installed: JBoss JAX-RS Tools 2.0.1.v20180311-2201 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.1.v20180311-2201)
Software currently installed: JBoss JAX-WS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxws.feature.feature.group 2.0.0.v20180105-1426)
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 2.0.1.v20180311-2201 (org.jboss.tools.ws.ui 2.0.1.v20180311-2201)
Cannot satisfy dependency:
From: JBoss JAX-RS Tools 2.0.1.v20180311-2201 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.1.v20180311-2201)
To: org.jboss.tools.ws.ui [2.0.1.v20180311-2201]
Cannot satisfy dependency:
From: JBoss JAX-WS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxws.feature.feature.group 2.0.0.v20180105-1426)
To: org.jboss.tools.ws.ui [2.0.0.v20180105-1426]
{code}
If my understanding is correct, the eclipse plans to update JAX-RS but doesn't plan to update JAX-WS.
I know that we fixed similar issue recently in JBIDE-25665.
The "Check for Updates" doesn't offer any remediation action but Install new Software offers nice solution.
was:
I tested an update form Oxygen2+JBT 4.5.2.Final to JBT 4.5.3.AM3. When I went through Check For Updates I got this error:
{code}
Cannot complete the install because of a conflicting dependency.
Software being installed: JBoss JAX-RS Tools 2.0.1.v20180311-2201 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.1.v20180311-2201)
Software currently installed: JBoss JAX-WS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxws.feature.feature.group 2.0.0.v20180105-1426)
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 2.0.1.v20180311-2201 (org.jboss.tools.ws.ui 2.0.1.v20180311-2201)
Cannot satisfy dependency:
From: JBoss JAX-RS Tools 2.0.1.v20180311-2201 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.1.v20180311-2201)
To: org.jboss.tools.ws.ui [2.0.1.v20180311-2201]
Cannot satisfy dependency:
From: JBoss JAX-WS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxws.feature.feature.group 2.0.0.v20180105-1426)
To: org.jboss.tools.ws.ui [2.0.0.v20180105-1426]
{code}
If my understanding is correct, the eclipse plans to update JAX-RS but doesn't plan to update JAX-WS.
I know that we fixed similar issue recently (https://issues.jboss.org/browse/JBIDE-25665).
The "Check for Updates" doesn't offer any remediation action but Install new Software offers nice solution.
> Can't update from JBT 4.5.2.Final to 4.5.3.AM3 using Check for Updates
> ----------------------------------------------------------------------
>
> Key: JBIDE-25856
> URL: https://issues.jboss.org/browse/JBIDE-25856
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.5.2.AM3
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 4.5.3.Final
>
> Attachments: CheckForUpdates.png
>
>
> I tested an update form Oxygen2+JBT 4.5.2.Final to JBT 4.5.3.AM3. When I went through Check For Updates I got this error:
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss JAX-RS Tools 2.0.1.v20180311-2201 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.1.v20180311-2201)
> Software currently installed: JBoss JAX-WS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxws.feature.feature.group 2.0.0.v20180105-1426)
> 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 2.0.1.v20180311-2201 (org.jboss.tools.ws.ui 2.0.1.v20180311-2201)
> Cannot satisfy dependency:
> From: JBoss JAX-RS Tools 2.0.1.v20180311-2201 (org.jboss.tools.ws.jaxrs.feature.feature.group 2.0.1.v20180311-2201)
> To: org.jboss.tools.ws.ui [2.0.1.v20180311-2201]
> Cannot satisfy dependency:
> From: JBoss JAX-WS Tools 2.0.0.v20180105-1426 (org.jboss.tools.ws.jaxws.feature.feature.group 2.0.0.v20180105-1426)
> To: org.jboss.tools.ws.ui [2.0.0.v20180105-1426]
> {code}
> If my understanding is correct, the eclipse plans to update JAX-RS but doesn't plan to update JAX-WS.
> I know that we fixed similar issue recently in JBIDE-25665.
> The "Check for Updates" doesn't offer any remediation action but Install new Software offers nice solution.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months