April 2016 - jbosstools-issues - Jboss List Archives

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3718?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3718: -------------------------------- Priority: Blocker (was: Major) > 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 > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > > 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-3747) Build failures with newest JSPM

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3747?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3747: -------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.1.0.GA) > Build failures with newest JSPM > ------------------------------- > > Key: JBDS-3747 > URL: https://issues.jboss.org/browse/JBDS-3747 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Jan Richter > Priority: Minor > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > The newest JSPM release (0.16.32 atm.) has broken the build. We have reverted to 0.16.31 until a more permanent solution is discovered. Investigate the failures with newer versions. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3732) Installer - A summary of what was installed should be displayed after a successful install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3732?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3732: -------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.1.0.GA) > Installer - A summary of what was installed should be displayed after a successful install > ------------------------------------------------------------------------------------------ > > Key: JBDS-3732 > URL: https://issues.jboss.org/browse/JBDS-3732 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Minor > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: Add_an_inventory.png > > > See the attached screenshot - it would be helpful/informative to the user to see a summary/inventory of the components that were installed or updated during a successful install. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3731) Installer - Failure to install a component does not halt the installer's progress bar

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3731?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3731: -------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.1.0.GA) > Installer - Failure to install a component does not halt the installer's progress bar > ------------------------------------------------------------------------------------- > > Key: JBDS-3731 > URL: https://issues.jboss.org/browse/JBDS-3731 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Environment: Windows10 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > Attachments: Screenshot (20).png, Screenshot (24).png > > > See the attached screenshots - when the bug described in JBDS-3722 was encountered, the virtualbox installation status bar continued to proceed, even though the installation of the affected component had stopped. This will be confusing to the user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3754) Installer: redirect links for Vagrant and VirtualBox should use https

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3754?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3754: ----------------------------------- Assignee: Denis Golovin > Installer: redirect links for Vagrant and VirtualBox should use https > --------------------------------------------------------------------- > > Key: JBDS-3754 > URL: https://issues.jboss.org/browse/JBDS-3754 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.GA > > > Installer's requirements.json file \[1] declares location of Vagrant and VirtualBox installers like these: > {code} > http://developers.redhat.com/redirect/to/vagrant-1.7.4.download > http://developers.redhat.com/redirect/to/virtualbox-5.0.8.download > {code} > They should use *https* scheme. > \[1] https://github.com/redhat-developer-tooling/developer-platform-install/bl... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-639) Update kie navigator tests after bugfixes

by Tomas David (JIRA)

Tomas David created JBTIS-639: --------------------------------- Summary: Update kie navigator tests after bugfixes Key: JBTIS-639 URL: https://issues.jboss.org/browse/JBTIS-639 Project: JBoss Tools Integration Stack Issue Type: Enhancement Components: drools/ jBPM, QE Reporter: Tomas David Assignee: Tomas David -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22079) Error when import a project already existing in workspace

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22079: --------------------------------------- Ok I agree, it's not critical and it can be done in 4.4.0.Alpha1. I wanted to make this as an enhancement, but enhancements do not support steps to reproduce. Feel free, if you like, move steps to reproduce to description and change type of issue to enhancement if required. > Error when import a project already existing in workspace > --------------------------------------------------------- > > Key: JBIDE-22079 > URL: https://issues.jboss.org/browse/JBIDE-22079 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: import_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: import-error.png > > > When I am creating a new OpenShift application using an existing repo, or at least project in workspace, it throws an error upon application creation completion. This is a bit of pain, because even I have an existing git repo and checked the checkbox in Import Wizard to reuse it, it tries to import project then, but it fails. But the existing project is still usable to use it for a new OpenShift 3 server adapter and upon start of the adapter, local changes are published to OpenShift. This issue is just about error. Maybe we could display a dialog that such a project already exists in workspace and let user to choose to replace it by the one being imported or keep it as it is (if user know that the project in workspace is the correct one and he/she does not want to overwrite it and let local changes disappear). > Error: > {code}Could not import project from org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException: There was a maven related error that prevented us from importing the project. We encourage you to look into the pom in the cloned repository at /home/mlabuda/git/jboss-eap-quickstarts. > One of the possible reasons is that there is already a project in your workspace that matches the maven name of the OpenShift application. You can then rename your workspace project and start over again. > An exception stack trace is not available. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22047) Label Openshift CDK feature as "Tech Preview"

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22047?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-22047: ---------------------------------- Attachment: cdk-feature-1.png cdk-feature-2.png I can see this displayed correctly under Installed Software: !cdk-feature-1.png! I would expect the Features tab to say the same, but it doesn't. For some reason it displays the plugin's name and description instead of the feature (and it's a bit outdated - I created JBIDE-22120 for that): !cdk-feature-2.png! > Label Openshift CDK feature as "Tech Preview" > --------------------------------------------- > > Key: JBIDE-22047 > URL: https://issues.jboss.org/browse/JBIDE-22047 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: cdk-feature-1.png, cdk-feature-2.png > > > Per call today, openshift.cdk.feature should be clearly marked as Tech Preview -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22047) Label Openshift CDK feature as "Tech Preview"

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22047?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22047. --------------------------------- The feature is properly marked as tech preview, closing. > Label Openshift CDK feature as "Tech Preview" > --------------------------------------------- > > Key: JBIDE-22047 > URL: https://issues.jboss.org/browse/JBIDE-22047 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: cdk-feature-1.png, cdk-feature-2.png > > > Per call today, openshift.cdk.feature should be clearly marked as Tech Preview -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22120) CDK plugin description is outdated

by Martin Malina (JIRA)

Martin Malina created JBIDE-22120: ------------------------------------- Summary: CDK plugin description is outdated Key: JBIDE-22120 URL: https://issues.jboss.org/browse/JBIDE-22120 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Affects Versions: 4.3.1.CR1 Reporter: Martin Malina Assignee: Rob Stryker Priority: Trivial JBIDE-22047 changed the cdk feature to tech preview. While verifying that, I noticed that the cdk plugin has a very much different name and description - see that JIRA for screenshots. -- 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 April 2016