June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3653) User's home folder with spaces cannot be used by vagrant during install

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3653. --------------------------------- Resolution: Done VirtualBox installation runs now without major problems, resolving this issue. > User's home folder with spaces cannot be used by vagrant during install > ----------------------------------------------------------------------- > > Key: JBDS-3653 > URL: https://issues.jboss.org/browse/JBDS-3653 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.0.0.Alpha3 > > Attachments: install(1).log > > > Vagrant complains about > {quote}Wed, 02 Mar 2016 18:04:21 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.0.0.gem" > The directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again > {quote} > When user home directory have spaces in it, because .vagrant.d file path in turn has spaces as well. For instance: > {code}C:\Users\User Name\.vagrant.d{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22443) Add to TP build a check that produced TP can be installed in target Eclipse version

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22443?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22443: ---------------------------------------- No, they're not duplicates. Read the description of this jira and the one of JBDS-3917 and you'll see they're speaking about different problems/ideas/solutions. > Add to TP build a check that produced TP can be installed in target Eclipse version > ----------------------------------------------------------------------------------- > > Key: JBIDE-22443 > URL: https://issues.jboss.org/browse/JBIDE-22443 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, target-platform > Reporter: Mickael Istria > > Recently, a change in TP (jetty 9.3.6) was introduced and everything built fine with it; until the very end of the build process: during install-tests. > This issue would *probably* have occured if trying to install all content of the TP into the target Eclipse IDE (using install-grinder or p2director or whatever installation). So it would be good to have inside the TP build (as a "verify" plugin in pom.xml) something that would try to find whether target Eclipse version and our TP are already compatible. > Technical notes: > * Trying to install all IUs from the release train site + our TP seems easier to implement > * We do not need to actually install the artifacts, just making the p2 request and getting whether the request managed to find a working plan without remediation seems enough. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-725) Fix Model Wizard Test

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/JBTIS-725?page=com.atlassian.jira.plugin.... ] Matus Makovy commented on JBTIS-725: ------------------------------------ Update site added. Verification job passed. > Fix Model Wizard Test > --------------------- > > Key: JBTIS-725 > URL: https://issues.jboss.org/browse/JBTIS-725 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: Matus Makovy > Assignee: Matus Makovy > Fix For: 4.3.1.Final > > > Fix model names in new Model Wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3917) Verify target-platform PR by running compile/package (no tests) build for all modules

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3917?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3917: ------------------------------------------- why not put it on central ci server if that one is running already ? and does it not need to be triggered by the TP PR job with a parameter to use the temporary generated TP from the TP PR build ? > Verify target-platform PR by running compile/package (no tests) build for all modules > ------------------------------------------------------------------------------------- > > Key: JBDS-3917 > URL: https://issues.jboss.org/browse/JBDS-3917 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Enhancement > Components: build, target-platform > Affects Versions: 10.0.0.Alpha2 > Reporter: Denis Golovin > > Would be good to have this as part of TP PR Verification build. > Example of repository with git submodules https://github.com/dgolovin/devstudio-releng. > Example for possible full build https://github.com/dgolovin/jbosstools-dev. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22443) Add to TP build a check that produced TP can be installed in target Eclipse version

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22443?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22443: --------------------------------------------- Thanks [~dgolovin] but is this issue and JBDS-3917 not now a duplicate of each other ? > Add to TP build a check that produced TP can be installed in target Eclipse version > ----------------------------------------------------------------------------------- > > Key: JBIDE-22443 > URL: https://issues.jboss.org/browse/JBIDE-22443 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, target-platform > Reporter: Mickael Istria > > Recently, a change in TP (jetty 9.3.6) was introduced and everything built fine with it; until the very end of the build process: during install-tests. > This issue would *probably* have occured if trying to install all content of the TP into the target Eclipse IDE (using install-grinder or p2director or whatever installation). So it would be good to have inside the TP build (as a "verify" plugin in pom.xml) something that would try to find whether target Eclipse version and our TP are already compatible. > Technical notes: > * Trying to install all IUs from the release train site + our TP seems easier to implement > * We do not need to actually install the artifacts, just making the p2 request and getting whether the request managed to find a working plan without remediation seems enough. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3612) Define new names for studio

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3612?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3612. ----------------------------- Looks all done to me, closing. > Define new names for studio > --------------------------- > > Key: JBDS-3612 > URL: https://issues.jboss.org/browse/JBDS-3612 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.Alpha3 > > > Issue to outline names for final products - blocks completion of any branding work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3899) Include latest wst.jsdt and chromium.debug features in TPs, jboss tools, and devstudio

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3899?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3899. ----------------------------- Both features successfully located in JBT 4.4.0.Alpha3 and DS 10.0.0.Alpha3 nightly builds. > Include latest wst.jsdt and chromium.debug features in TPs, jboss tools, and devstudio > -------------------------------------------------------------------------------------- > > Key: JBDS-3899 > URL: https://issues.jboss.org/browse/JBDS-3899 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: target-platform > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.Alpha3 > > > New JSDT included new Debugger plugins. They are not included in JSDT feature afaik. > We should make sure we have all needed plugins/features included in devstudio and JBT TPs/market place/installation. > [~vrubezhny], [~ibuziuk] please provide all needed info for [~nickboldt]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22410) server New and Noteworthy for 4.4.0.Alpha2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22410?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22410. --------------------------------- Both JIRAs from the query are properly documented, but I had to reopen JBIDE-20577 for now. > server New and Noteworthy for 4.4.0.Alpha2 > ------------------------------------------ > > Key: JBIDE-22410 > URL: https://issues.jboss.org/browse/JBIDE-22410 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If server is not listed here check if there are issues that should be added and add them. > Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3898) Make sure eclipse JSON editor is included in devstudio

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3898?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3898. ----------------------------- Verified in 10.0.0.Alpha3 B5485. > Make sure eclipse JSON editor is included in devstudio > ------------------------------------------------------ > > Key: JBDS-3898 > URL: https://issues.jboss.org/browse/JBDS-3898 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: target-platform > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Priority: Critical > Fix For: 10.0.0.Alpha3 > > > We should make sure JSON Editor is included in devstudio and JBT target platforms/Market place/installation. > [~vrubezhny] please provide all needed information for [~nickboldt] regarding this plugin. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3897) Use "Red Hat JBoss Developer Studio" instead of "Red Hat Developer Studio" in graphics

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3897?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3897. ----------------------------- Verified with devstudio-10.0.0.Alpha3-v20160601-0425-B5485-installer > Use "Red Hat JBoss Developer Studio" instead of "Red Hat Developer Studio" in graphics > -------------------------------------------------------------------------------------- > > Key: JBDS-3897 > URL: https://issues.jboss.org/browse/JBDS-3897 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: installer > Affects Versions: 10.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha3 > > Attachments: about_devstudio.jpg, devstudio_banner.png, heading.png, RHJBoss_DevStudio_Assets.zip, splash.bmp > > > Due to changes in https://trello.com/c/Cbo0q8TT/99-rebrand-jbds-as-rhds-using-rhd-logo the correct name of the product is "Red Hat JBoss Developer Studio", not "Red Hat Developer Studio", so we need to add the "JBoss" part back into the new RHD-branded headers & splash. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016