July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24748) Enable Show In Console for cdk 3

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24748?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24748: ------------------------------------- My experience is that (for cdk3) the console is shown automatically as well, it's just slower to show, and has much less output until the end, when it suddenly dumps a lot. I haven't experienced the bug of console not showing automatically with output for cdk3 though. If you experience that, please open a bug and I'll investigate. > Enable Show In Console for cdk 3 > -------------------------------- > > Key: JBIDE-24748 > URL: https://issues.jboss.org/browse/JBIDE-24748 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.Final > > > CDK 2 used the Terminal view, CDK 3 switched back to usiong Console view. So Show In Console on the server adapter should be enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24749) Rename cdk runtime detector to cdk 2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24749?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-24749. --------------------------------- Resolution: Done Pushed to master. Also found a small issue in runtime detection schema (should be unbounded, but isn't) > Rename cdk runtime detector to cdk 2 > ------------------------------------ > > Key: JBIDE-24749 > URL: https://issues.jboss.org/browse/JBIDE-24749 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.Final > > Attachments: runtime-detectors.png > > > In JBIDE-24584 I requested that cdk server adapter be renamed to cdk 2 which is now done. But today I noticed that we missed the runtime detector: > Go to Preferences -> JBoss Tools -> JBoss Runtime Detection > On that page, there is a table called Available runtime detectors which, among others, includes: > Container Development Environment 3 > Container Development Environment > !runtime-detectors.png! > So the latter should be renamed to include "2" or "2.x" - probably the latter to be consistent with the server adapter name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24379) javaee tests failing for linux, windows and osx

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24379?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24379 at 7/31/17 10:33 AM: -------------------------------------------------------------- After some discussion on MM w/ Jeff and Dmitri, we've decided to: * disable the broken seam tests * mark the seam features in jbosstools/devstudio/central deprecated as of this forthcoming 4.5 / 11.0 release was (Author: nickboldt): After some discussion on MM w/ Jeff and Dmitri, we've decided to: * disable the broken seam tests * mark the seam features in jbosstools/devstudio/central deprecated as of this forthcoming 4.5 / 11.0 release. > javaee tests failing for linux, windows and osx > ----------------------------------------------- > > Key: JBIDE-24379 > URL: https://issues.jboss.org/browse/JBIDE-24379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, jsf, seam2 > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Dmitrii Bocharov > Priority: Blocker > Fix For: 4.5.0.Final > > Attachments: javaee-test-failures.png, javaee-test-failures_last_pass_jan26.png, javaee-tests-failing.png, javaee-tests-failing_latest_status_jul5_842am_build269.png, jst.ui.test.log > > > JavaEE tests have been failing for months. > Please investigate. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24749) Rename cdk runtime detector to cdk 2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24749?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24749: -------------------------------- Fix Version/s: 4.5.0.Final > Rename cdk runtime detector to cdk 2 > ------------------------------------ > > Key: JBIDE-24749 > URL: https://issues.jboss.org/browse/JBIDE-24749 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.Final > > Attachments: runtime-detectors.png > > > In JBIDE-24584 I requested that cdk server adapter be renamed to cdk 2 which is now done. But today I noticed that we missed the runtime detector: > Go to Preferences -> JBoss Tools -> JBoss Runtime Detection > On that page, there is a table called Available runtime detectors which, among others, includes: > Container Development Environment 3 > Container Development Environment > !runtime-detectors.png! > So the latter should be renamed to include "2" or "2.x" - probably the latter to be consistent with the server adapter name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24379) javaee tests failing for linux, windows and osx

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24379?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24379: ------------------------------------ After some discussion on MM w/ Jeff and Dmitri, we've decided to: * disable the broken seam tests * mark the seam features in jbosstools/devstudio/central deprecated as of this forthcoming 4.5 / 11.0 release. > javaee tests failing for linux, windows and osx > ----------------------------------------------- > > Key: JBIDE-24379 > URL: https://issues.jboss.org/browse/JBIDE-24379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, jsf, seam2 > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Dmitrii Bocharov > Priority: Blocker > Fix For: 4.5.0.Final > > Attachments: javaee-test-failures.png, javaee-test-failures_last_pass_jan26.png, javaee-tests-failing.png, javaee-tests-failing_latest_status_jul5_842am_build269.png, jst.ui.test.log > > > JavaEE tests have been failing for months. > Please investigate. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-667) Fix VersionChecker Test

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-667?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík closed JBTIS-667. ------------------------------ Fix Version/s: (was: 4.3.0.Final) Resolution: Out of Date We do not use _VersionCheckerTest_ anymore. Closing as out of date > Fix VersionChecker Test > ----------------------- > > Key: JBTIS-667 > URL: https://issues.jboss.org/browse/JBTIS-667 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE > Affects Versions: 4.0.0 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > > Fix com.redhat.jbossqe.jbdsis.installer.test.VersionCheckerTest > need to handle compositeArtifacts.xml - https://devstudio.redhat.com/9.0/development/updates/integration-stack/ea... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24778) Creating application from Eclipse project which already defines a Git repo should reuse the URL

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24778?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24778: ------------------------------- Affects Version/s: 4.5.0.AM2 > Creating application from Eclipse project which already defines a Git repo should reuse the URL > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24778 > URL: https://issues.jboss.org/browse/JBIDE-24778 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Mickael Istria > Fix For: 4.5.x > > > I'm trying to connect an existing Eclipse project to OpenShift. > The project is connected to GitHub ( https://github.com/mickaelistria/demo-dotnet.git ) > The OpenShift application I'm using uses a dotnet-core:2.0 image. > Once I've selected the openshift project, the Eclipse project and the application image; I'm driven to a wizard page asking me for some details about the application, including the Git repo URL. > I would expect the repo URL to be prepopulated with the Git repo URL of my Eclipse project > Instead, the URL was the one of the image example: https://github.com/redhat-developer/s2i-dotnetcore-ex.git > If this is an issue in the .NET Core 2.0 image, please tell me and I'll open a bug for it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24778) Creating application from Eclipse project which already defines a Git repo should reuse the URL

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24778?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24778: ------------------------------- Fix Version/s: 4.5.x > Creating application from Eclipse project which already defines a Git repo should reuse the URL > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24778 > URL: https://issues.jboss.org/browse/JBIDE-24778 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.0.AM2 > Reporter: Mickael Istria > Fix For: 4.5.x > > > I'm trying to connect an existing Eclipse project to OpenShift. > The project is connected to GitHub ( https://github.com/mickaelistria/demo-dotnet.git ) > The OpenShift application I'm using uses a dotnet-core:2.0 image. > Once I've selected the openshift project, the Eclipse project and the application image; I'm driven to a wizard page asking me for some details about the application, including the Git repo URL. > I would expect the repo URL to be prepopulated with the Git repo URL of my Eclipse project > Instead, the URL was the one of the image example: https://github.com/redhat-developer/s2i-dotnetcore-ex.git > If this is an issue in the .NET Core 2.0 image, please tell me and I'll open a bug for it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24778) Creating application from Eclipse project which already defines a Git repo should reuse the URL

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-24778: -------------------------------------- Summary: Creating application from Eclipse project which already defines a Git repo should reuse the URL Key: JBIDE-24778 URL: https://issues.jboss.org/browse/JBIDE-24778 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Mickael Istria I'm trying to connect an existing Eclipse project to OpenShift. The project is connected to GitHub ( https://github.com/mickaelistria/demo-dotnet.git ) The OpenShift application I'm using uses a dotnet-core:2.0 image. Once I've selected the openshift project, the Eclipse project and the application image; I'm driven to a wizard page asking me for some details about the application, including the Git repo URL. I would expect the repo URL to be prepopulated with the Git repo URL of my Eclipse project Instead, the URL was the one of the image example: https://github.com/redhat-developer/s2i-dotnetcore-ex.git If this is an issue in the .NET Core 2.0 image, please tell me and I'll open a bug for it. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24777) Creating an application from project should allow to connect project to Git if nissing

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-24777: -------------------------------------- Summary: Creating an application from project should allow to connect project to Git if nissing Key: JBIDE-24777 URL: https://issues.jboss.org/browse/JBIDE-24777 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Mickael Istria Using Red Hat Developer Studio 11.0.AM2. I'm trying to deploy a new project to OpenShift (Online). As this project is new, it's not connected to any Git repo. When going through the wizards to create an application, the wizard shows an error message because project isn't connected to Git. The only way to connect to Git is to quit the current OpenShift wizard, use the Git wizards to connect project and then re-open the OpenShift wizard. I believe a better workflow would be to show in the error message or in the wizard a link to connect the selected repo to Git if it's missing. Then the workflow is more linear and progressive so it's easier for user to move forward. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2017