March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-502) Include Drools tooling 6.3 to JBDS-IS 9.x

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-502?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-502: ------------------------------------ Fix Version/s: 9.0.0.Beta1 4.3.0.Beta1 (was: 9.0.0.Alpha2) (was: 4.3.0.Alpha2) > Include Drools tooling 6.3 to JBDS-IS 9.x > ----------------------------------------- > > Key: JBTIS-502 > URL: https://issues.jboss.org/browse/JBTIS-502 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 4.3.0.Beta1, 9.0.0.Beta1 > > > There is a new version of Drools tooling which is available at http://drools.org/download/download.html > Please include the new Drools tooling to the next build of JBDS-IS 9.x -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3718) Detected/selected JDK always reported as invalid

by Jan Richter (JIRA)

Jan Richter created JBDS-3718: --------------------------------- Summary: Detected/selected JDK always reported as invalid Key: JBDS-3718 URL: https://issues.jboss.org/browse/JBDS-3718 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.1.0.CR1 Reporter: Jan Richter The installer correctly detects a JDK but still reports it as invalid. Same goes for selecting an installation of JDK - all checks pass but still the message says the installation is invalid. It does not seem to be a problem with the detection logic - it returns correct values for me. My guess would be that something is incorrectly propagated to the UI, but I haven't been able to find the source yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3718) Detected/selected JDK always reported as invalid

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3718?page=com.atlassian.jira.plugin.... ] Jan Richter reassigned JBDS-3718: --------------------------------- Assignee: Denis Golovin > Detected/selected JDK always reported as invalid > ------------------------------------------------ > > Key: JBDS-3718 > URL: https://issues.jboss.org/browse/JBDS-3718 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > > The installer correctly detects a JDK but still reports it as invalid. Same goes for selecting an installation of JDK - all checks pass but still the message says the installation is invalid. > It does not seem to be a problem with the detection logic - it returns correct values for me. My guess would be that something is incorrectly propagated to the UI, but I haven't been able to find the source yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-614) Adpat ProjectCapabilitiesTest to follow API changes in SwitchyardRequirement

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-614?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-614: ------------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/670, https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/671 (was: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/670) > Adpat ProjectCapabilitiesTest to follow API changes in SwitchyardRequirement > ---------------------------------------------------------------------------- > > Key: JBTIS-614 > URL: https://issues.jboss.org/browse/JBTIS-614 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, switchyard > Affects Versions: 4.3.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.3.0.Final > > > See the changes in JBTIS-602 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3704) The installer gets stuck on Download page and never goes to Getting Started

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3704?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3704: ----------------------------------- By this principle, one could resolve an issue by skipping an arbitrary task because it is faulty. But I digress, onwards to JBDS-3711 then. > The installer gets stuck on Download page and never goes to Getting Started > --------------------------------------------------------------------------- > > Key: JBDS-3704 > URL: https://issues.jboss.org/browse/JBDS-3704 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > It happens if the installer installs JBDS and works fine if it just sets up some already existing one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21967) Cannot create server adapter if there is a running build on a project although there are more projects

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21967: ------------------------------------- Summary: Cannot create server adapter if there is a running build on a project although there are more projects Key: JBIDE-21967 URL: https://issues.jboss.org/browse/JBIDE-21967 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Priority: Critical When I am having several projects and some of them has already running application, I am not able to create a new server adapter for OpenShift 3 application if there is a project with running build. Once build finish, it is possible to create a project but while there is any project with not completed build (and therefore application image is not there yet) user is blocked from creating a new server adapter. This is related to JBIDE-21731 - once this issue will be fixed, it should keep in mind to allow users proceed with creation of server adapters on other projects. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21967) Cannot create server adapter if there is a running build on a project although there are more projects

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21967?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21967: ---------------------------------- Labels: openshift_v3 server_adapter (was: ) > Cannot create server adapter if there is a running build on a project although there are more projects > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21967 > URL: https://issues.jboss.org/browse/JBIDE-21967 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > > When I am having several projects and some of them has already running application, I am not able to create a new server adapter for OpenShift 3 application if there is a project with running build. Once build finish, it is possible to create a project but while there is any project with not completed build (and therefore application image is not there yet) user is blocked from creating a new server adapter. This is related to JBIDE-21731 - once this issue will be fixed, it should keep in mind to allow users proceed with creation of server adapters on other projects. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-614) Adpat ProjectCapabilitiesTest to follow API changes in SwitchyardRequirement

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-614?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-614: ------------------------------------ Description: See the changes in JBTIS-602 > Adpat ProjectCapabilitiesTest to follow API changes in SwitchyardRequirement > ---------------------------------------------------------------------------- > > Key: JBTIS-614 > URL: https://issues.jboss.org/browse/JBTIS-614 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, switchyard > Affects Versions: 4.3.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.3.0.Final > > > See the changes in JBTIS-602 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-614) Adpat ProjectCapabilitiesTest to follow API changes in SwitchyardRequirement

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-614: --------------------------------------- Summary: Adpat ProjectCapabilitiesTest to follow API changes in SwitchyardRequirement Key: JBTIS-614 URL: https://issues.jboss.org/browse/JBTIS-614 Project: JBoss Tools Integration Stack Issue Type: Bug Components: QE, switchyard Affects Versions: 4.3.0.Beta1 Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky Fix For: 4.3.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3717) Installer says "Terms and Conditions for CDK have not been signed" with no hint for the user on how to do it

by Pavol Srna (JIRA)

Pavol Srna created JBDS-3717: -------------------------------- Summary: Installer says "Terms and Conditions for CDK have not been signed" with no hint for the user on how to do it Key: JBDS-3717 URL: https://issues.jboss.org/browse/JBDS-3717 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 9.1.0.CR1 Reporter: Pavol Srna This is a new user scenario. I've registered on developers.redhat.com with a new 'personal' email address - following the create account link in the installer. Then I attempted to log in from within the installer. Installer does not log me in and says "Terms and Conditions for CDK have not been signed". But as a new user I have no idea on where to sign them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016