[JBoss JIRA] (JBIDE-24081) runtime detection for cdk 3 via minishift
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24081?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24081:
------------------------------------
When pushing changes to master and 4.4.x branch, please make sure you've properly upversioned plugins and their containing features if that's not already been done in the branches.
By building locally, you can avoid causing builds to break in Jenkins like this:
{code}
02:29:04 [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.foundation.ui: Only qualifier changed for (org.jboss.tools.foundation.ui/1.3.3.v20170315-2203). Expected to have bigger x.y.z than what is available in baseline (1.3.3.v20161213-1258) -> [Help 1]
{code} -- http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/D...
> runtime detection for cdk 3 via minishift
> -----------------------------------------
>
> Key: JBIDE-24081
> URL: https://issues.jboss.org/browse/JBIDE-24081
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, runtime-detection
> Affects Versions: 4.4.4.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM2, 4.5.0.AM1
>
>
> CDK3 has no runtime detection support
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24074) Download runtimes eap-6.2 has bad layout on credential page
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24074?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24074:
------------------------------------
When pushing changes to master and 4.4.x branch, please make sure you've properly upversioned plugins and their containing features if that's not already been done in the branches.
By building locally, you can avoid causing builds to break in Jenkins like this:
{code}
02:29:04 [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.foundation.ui: Only qualifier changed for (org.jboss.tools.foundation.ui/1.3.3.v20170315-2203). Expected to have bigger x.y.z than what is available in baseline (1.3.3.v20161213-1258) -> [Help 1]
{code} -- http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/D...
> Download runtimes eap-6.2 has bad layout on credential page
> -----------------------------------------------------------
>
> Key: JBIDE-24074
> URL: https://issues.jboss.org/browse/JBIDE-24074
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.4.4.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM2, 4.5.0.AM1
>
>
> Very ugly layout. The edit button exists when it should not exist, and it breaks the entire layout.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-22969:
-------------------------------------
Sprint: devex #123 November 2016, devex #129 March 2017 (was: devex #123 November 2016)
> Make sure OpenShift Tools support proxies
> -----------------------------------------
>
> Key: JBIDE-22969
> URL: https://issues.jboss.org/browse/JBIDE-22969
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Reporter: Alexey Kazakov
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.4.AM2
>
> Attachments: proxy_settings.png, proxy_settings_2.png
>
>
> CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too.
> If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side.
> This issue covers:
> - testing
> - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests)
> - fixing any problems we have in OpenShift tooling regarding proxy support.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4181) No valid JDK found
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-4181?page=com.atlassian.jira.plugin.... ]
Marián Labuda edited comment on JBDS-4181 at 3/16/17 5:12 AM:
--------------------------------------------------------------
As I said, it is edge case, when user upgrade OS. If you want to reproduce, install Fedora 23 (maybe the later one would work too), install the specified java version, then upgrade to Fedora 24 and then the issue happened. It's not easily reproducible.
was (Author: mlabuda):
As I said, it is edge case, when user upgrade OS. If you want to reproduce, install Fedora 24, install the specified java version, then upgrade to Fedora 25 and then the issue happened. It's not easily reproducible.
> No valid JDK found
> ------------------
>
> Key: JBDS-4181
> URL: https://issues.jboss.org/browse/JBDS-4181
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: common, upstream
> Affects Versions: 10.2.0.GA
> Environment: Fedora 24,
> openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> OpenJDK 64-Bit Server VM (build 25.102-b14, mixed mode)
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Fix For: 10.x
>
>
> When I start latest DevStudio 10.2.0.GA build ID GA-v20161116-0039-B6472, I get following error in error log
> {code}
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:275)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:432)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:417)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:146)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:121)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:114)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4181) No valid JDK found
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-4181?page=com.atlassian.jira.plugin.... ]
Marián Labuda commented on JBDS-4181:
-------------------------------------
As I said, it is edge case, when user upgrade OS. If you want to reproduce, install Fedora 24, install the specified java version, then upgrade to Fedora 25 and then the issue happened. It's not easily reproducible.
> No valid JDK found
> ------------------
>
> Key: JBDS-4181
> URL: https://issues.jboss.org/browse/JBDS-4181
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: common, upstream
> Affects Versions: 10.2.0.GA
> Environment: Fedora 24,
> openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> OpenJDK 64-Bit Server VM (build 25.102-b14, mixed mode)
> Reporter: Marián Labuda
> Assignee: Rob Stryker
> Fix For: 10.x
>
>
> When I start latest DevStudio 10.2.0.GA build ID GA-v20161116-0039-B6472, I get following error in error log
> {code}
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:275)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:432)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:417)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:146)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:121)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:114)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82)
> at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73)
> at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23896) Allow user to choose hypervisor in editor and new server wizard
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23896?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-23896:
---------------------------------------
Hi [~rob.stryker] - Sorry for not giving info about the build, it is devstudio 10.4.0.AM1 Build id: AM1-v20170309-1919-B213. I will definitely report the result to the other jira in case if it would not be working in upcoming build (should be AM2, right?). Thanks!
> Allow user to choose hypervisor in editor and new server wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-23896
> URL: https://issues.jboss.org/browse/JBIDE-23896
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, server
> Affects Versions: 4.4.3.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM2
>
> Attachments: cdk3tp.png
>
>
> Users do not like going to customize cmd args unless absolutely necessary. The most common usecases should be doable from the server editor or the creation wizard.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years