March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3682) Online installer reports missing package.js file

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3682?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3682. ----------------------------- Both app and tests seem to work properly now, closing. > Online installer reports missing package.js file > ------------------------------------------------ > > Key: JBDS-3682 > URL: https://issues.jboss.org/browse/JBDS-3682 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > Installer now files to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up. > Right way to reference package json would be different for development and runtime (see attached PR); -- 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 Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3691?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3691. ----------------------------- Vagrant 1.7.4 msi is now in master, closing as verified. > 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-3625) Vagrant delivered by installer has no vagrant.exe

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3625?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3625. ----------------------------- The Vagrant installer has been swapped to the original msi, closing. > Vagrant delivered by installer has no vagrant.exe > ------------------------------------------------- > > Key: JBDS-3625 > URL: https://issues.jboss.org/browse/JBDS-3625 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Environment: Windows x86_64 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1 > > > As [~hardy.ferentschik] pointed out in DEVEX-90 vagrant from installer (see https://github.com/redhat-developer-tooling/vagrant-distribution) has no vagrant.exe, but original vagrant installer does have it. > That should be fixed in vagrant distributed by installer, because current tools implementation expects vagrant.exe to be available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21690) Include updated wildfly10 schema in catalog

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21690?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21690. --------------------------------- I verified that the commit is applied both in master and 4.3.x. Also, I checked that all the schema files from wildfly 10 are present in the catalog plugin: {code} $ for i in `ls`; do find ~/tmp/jar/ -name $i >/dev/null || echo $i not found; done {code} But then I found that two dtd files that are in the catalog are not in the plugin.xml, I created a JIRA for that: JBIDE-21939 Closing. > Include updated wildfly10 schema in catalog > ------------------------------------------- > > Key: JBIDE-21690 > URL: https://issues.jboss.org/browse/JBIDE-21690 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > Wildfly 10 final has many updated schema which should be added. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3647) Investigate why we are including both cygwin and mingw

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3647?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3647. ----------------------------- Investigation is over, closing. > Investigate why we are including both cygwin and mingw > ------------------------------------------------------ > > Key: JBDS-3647 > URL: https://issues.jboss.org/browse/JBDS-3647 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Pete Muir > Assignee: Denis Golovin > Priority: Critical > Labels: havoc > Fix For: 9.1.0.CR1 > > > We shouldn't need to include cygwin to make vagrant work. Let's check why we include this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21939) datatypes.dtd and properties.dtd not present in xml catalog

by Martin Malina (JIRA)

Martin Malina created JBIDE-21939: ------------------------------------- Summary: datatypes.dtd and properties.dtd not present in xml catalog Key: JBIDE-21939 URL: https://issues.jboss.org/browse/JBIDE-21939 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.3.1.CR1 Reporter: Martin Malina Assignee: Rob Stryker Maybe this is not an issue at all but need to check. While verifying JBIDE-21690, I noticed that there are two dtd files that are not referenced in plugin.xml of org.jboss.tools.as.catalog_3.1.1.CR1-v20160316-0026-B106.jar . {code} $ for i in `find schema -name '*.dtd'`; do grep $i plugin.xml >/dev/null || echo $i not found; done schema/dtd/datatypes.dtd not found schema/dtd/properties.dtd not found {code} Is this ok or not? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3607) Update Suite installer UI/names

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3607?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3607: ------------------------------------------- the overall rebranding/renaming have been pushed out past 9.1, but this issue seem to cater more about actually getting the UI consistent and have proper names; thus I've decoupled this issue from the rebranding epic and updated the title. > Update Suite installer UI/names > ------------------------------- > > 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. > https://patternfly.atlassian.net/browse/RHUAP-26 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3611) update tools.jboss.org for developers.redhat.com branding

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3611?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3611: -------------------------------------- Fix Version/s: 10.0.0.Alpha1 (was: 9.1.0.CR1) > update tools.jboss.org for developers.redhat.com branding > ---------------------------------------------------------- > > Key: JBDS-3611 > URL: https://issues.jboss.org/browse/JBDS-3611 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 10.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3607) Update Suite installer UI/names

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3607?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3607: -------------------------------------- Summary: Update Suite installer UI/names (was: Rebrand Suite installer) > Update Suite installer UI/names > ------------------------------- > > 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. > https://patternfly.atlassian.net/browse/RHUAP-26 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3608) update devstudio.redhat.com branding

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3608?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3608: ------------------------------------------- [~nickboldt] please do not commit artifacts to our master repos before branding is actually finalized. (PR's are fine) moved this issue out past 9.1 > update devstudio.redhat.com branding > ------------------------------------ > > Key: JBDS-3608 > URL: https://issues.jboss.org/browse/JBDS-3608 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > update branding for developers.redhat.com -- 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