March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3656) The installer should use Vagrantfile provided by CDK

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBDS-3656?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik commented on JBDS-3656: ----------------------------------------- {quote} Beta 5 is out. Can we get rid of our https://github.com/redhat-developer-tooling/openshift-vagrant/ in the installer and switch to cdk Beta5? {quote} Yes {quote} Or we still have some remaining issues which we need to push upstream? {quote} I still would like to make some minor changes to the default _Vagrantfile_, but that does not effect the basic use cases. > The installer should use Vagrantfile provided by CDK > ---------------------------------------------------- > > Key: JBDS-3656 > URL: https://issues.jboss.org/browse/JBDS-3656 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > The installer should be using the {{Vagrantfile}} provided by the CDK (provided it reaches feature parity) instead of the {{Vagrantfile}} provided by the [openshift-vagrant|https://github.com/redhat-developer-tooling/openshift-v...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3607) Rebrand Suite installer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3607?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3607: ------------------------------------------- could we please have any updates to UX linked to this issue ? > Rebrand Suite installer > ----------------------- > > Key: JBDS-3607 > URL: https://issues.jboss.org/browse/JBDS-3607 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Joshua Wilson > Priority: Blocker > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > > Suite Installer should use Red Hat Developer style. more details to follow. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3607) Rebrand Suite installer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3607?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3607: ------------------------------------------- I mean, if UX team created some new designs it would make sense to add them to this jira. > Rebrand Suite installer > ----------------------- > > Key: JBDS-3607 > URL: https://issues.jboss.org/browse/JBDS-3607 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Joshua Wilson > Priority: Blocker > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > > Suite Installer should use Red Hat Developer style. more details to follow. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-602) Fix creating a SY project with intpkg

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-602?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-602: ------------------------------------ Summary: Fix creating a SY project with intpkg (was: Fix creating a SY project with intplg) > Fix creating a SY project with intpkg > ------------------------------------- > > Key: JBTIS-602 > URL: https://issues.jboss.org/browse/JBTIS-602 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: QE, switchyard > Affects Versions: 4.2.6.CR1 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > > The problem is that the behaviour depends eclipse base (luna or mars) > - detect correct runtime label > - get rid of switchyard vs integration version -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-602) Fix creating a SY project with intplg

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-602: --------------------------------------- Summary: Fix creating a SY project with intplg Key: JBTIS-602 URL: https://issues.jboss.org/browse/JBTIS-602 Project: JBoss Tools Integration Stack Issue Type: Task Components: QE, switchyard Affects Versions: 4.2.6.CR1 Reporter: Andrej Podhradsky Assignee: Andrej Podhradsky The problem is that the behaviour depends eclipse base (luna or mars) - detect correct runtime label - get rid of switchyard vs integration version -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3689) ask user for JDK location when old location is gone

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3689?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3689: -------------------------------------- This is one risk when setting the -vm flag. Eclipse IDE itself (at least on Linux) doesn't set this -vm flag and relies on the JAVA_HOME or PATH, which gets correctly updated when Java is updated. A solution for JBDS would be to simply not set this flag and rely on the default behaviour to find out the best JVM. > ask user for JDK location when old location is gone > --------------------------------------------------- > > Key: JBDS-3689 > URL: https://issues.jboss.org/browse/JBDS-3689 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: upstream > Affects Versions: 9.1.0.Beta2 > Environment: Fedora 23 > Reporter: Aleksandar Kostadinov > Assignee: Mickael Istria > Fix For: 4.4 > > > Hello, installed 9.1.0.Beta2 and starting it after some fedora update, yielded an error that JDK is not found. With no help how to fix. > Searching over the internet I found > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > But it makes much more sense to let the user select a different location. Or at least point user at the ini file to be updated. Currently user is left wondering why JBDS fails to start when system has a perfectly working JDK installed on standard location. My first thought was that for some reason JBDS installation broke. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-585) Adapt 'JMXNavigatorTest' to 8.0.0

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-585?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-585. ----------------------------------- Resolution: Done pushed to master > Adapt 'JMXNavigatorTest' to 8.0.0 > --------------------------------- > > Key: JBTIS-585 > URL: https://issues.jboss.org/browse/JBTIS-585 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Alpha2 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.0.Final > > Time Spent: 30 minutes > Remaining Estimate: 0 minutes > > SSIA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3607) Rebrand Suite installer

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3607?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-3607: ------------------------------------- [~ppitonak] The UX team re-designed the UI and so I moved it. I will keep moving and cleaning up the UI until it matches new design. > Rebrand Suite installer > ----------------------- > > Key: JBDS-3607 > URL: https://issues.jboss.org/browse/JBDS-3607 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Joshua Wilson > Priority: Blocker > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > > Suite Installer should use Red Hat Developer style. more details to follow. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3691) Use original installer for vagrant 1.7.4

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3691?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3691: --------------------------------- Fix Version/s: 9.1.0.CR1 > Use original installer for vagrant 1.7.4 > ----------------------------------------- > > Key: JBDS-3691 > URL: https://issues.jboss.org/browse/JBDS-3691 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > We can use original vagrant installer as soon as it is downloaded during installation from original web site https://releases.hashicorp.com/vagrant/1.7.4/vagrant_1.7.4.msi. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3694) CDK plugins instalation should not be hardcoded with list of gem file names

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3694?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3694: ----------------------------- > CDK plugins instalation should not be hardcoded with list of gem file names > --------------------------------------------------------------------------- > > Key: JBDS-3694 > URL: https://issues.jboss.org/browse/JBDS-3694 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > > Installer should iterated over .gem files in cdk/plugins to install plugins instead of hardcoding file names to install. File names have version in it and with new cdk those version change sometimes. -- 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