July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4426) Devstudio 11 includes link to devstudio 10 to install features, which it should not

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4426?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4426. ---------------------------- Resolution: Cannot Reproduce Bug Using devstudio-11.0.0.AM2-v20170713-2124-B489-installer-standalone.jar, I can't reproduce this. !jbds1100am2-ootb.png|thumbnail! !jbds1100am2-after-using-central.png|thumbnail! Closing. > Devstudio 11 includes link to devstudio 10 to install features, which it should not > ----------------------------------------------------------------------------------- > > Key: JBDS-4426 > URL: https://issues.jboss.org/browse/JBDS-4426 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, central-update, updatesite > Affects Versions: 11.0.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 11.0.0.GA > > Attachments: devstudio-10-in-11.png, jbds1100am2-after-using-central.png, jbds1100am2-ootb.png > > > OOTB the BYOE installation of Devstudio 11.0.0.AM1 contains a link to devstudio 10's stable update site. It should NOT have this link. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4426) Devstudio 11 includes link to devstudio 10 to install features, which it should not

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4426?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4426: ----------------------------- Attachment: jbds1100am2-after-using-central.png jbds1100am2-ootb.png > Devstudio 11 includes link to devstudio 10 to install features, which it should not > ----------------------------------------------------------------------------------- > > Key: JBDS-4426 > URL: https://issues.jboss.org/browse/JBDS-4426 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, central-update, updatesite > Affects Versions: 11.0.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 11.0.0.GA > > Attachments: devstudio-10-in-11.png, jbds1100am2-after-using-central.png, jbds1100am2-ootb.png > > > OOTB the BYOE installation of Devstudio 11.0.0.AM1 contains a link to devstudio 10's stable update site. It should NOT have this link. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24518) change github check frequency for CI builds from 8hrs to 20 mins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24518?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24518. ------------------------------ Resolution: Done Done: https://github.com/jbdevstudio/jbdevstudio-ci/commit/c76d6f472332b387ada5... > change github check frequency for CI builds from 8hrs to 20 mins > ---------------------------------------------------------------- > > Key: JBIDE-24518 > URL: https://issues.jboss.org/browse/JBIDE-24518 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Currently the jbosstools-* component project builds run every 8hrs, with a nightly buildflow also triggering a rebuild. But since breaking changes are frequently NOT fixed quickly enough as devs cannot or will not kick their own builds, we need to implement a better strategy to check github for changes more often. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4422) Rename RPM package to rh-eclipse47-devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4422?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4422. ---------------------------- Resolution: Done Yes, I just wanted to be sure installation worked too. {code} #➔ yum install rh-eclipse47-devstudio Installed: rh-eclipse47-base.x86_64 4.7-2.el7 rh-eclipse47-devstudio.x86_64 11.0-0.20170719.1340.el7 rh-eclipse47-eclipse-abrt.noarch 0.0.3-2.2.el7 rh-eclipse47-eclipse-usage.noarch 4.4.4-1.1.el7 rh-eclipse47-eclipse-webtools-jsf.noarch 3.9.0-1.2.el7 Upgraded: rh-eclipse47-runtime.x86_64 4.7-2.el7 {code} Closing. > Rename RPM package to rh-eclipse47-devstudio > -------------------------------------------- > > Key: JBDS-4422 > URL: https://issues.jboss.org/browse/JBDS-4422 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: rpm > Affects Versions: 11.0.0.AM1 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 11.0.0.GA > > Attachments: build.log.txt, core.runtime.note.resolved.started-config.ini.log.txt, root.log.txt > > > Devstudio RPM should be renamed to "rh-eclipse47-devstudio". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4461) Document list of features, versions, and quality status of devstudio 11 contents

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4461?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4461: ---------------------------------- {quote} Is there a way to make the output a little less computer and a little more human readable? {quote} Yes, someone could write a parsing script to strip out dupe/undesired info. {quote}If we could massage the data to strip some of the information and present it in easier to read/sort, it might work.{quote} We could parse the data into CSV so it could then be imported to a Google Doc spreadsheet. Then you can sort/format to your heart's content. :D {quote}It also doesn't state quality of the version{quote} True, but everything is GA at this point unless it's explicitly called out as pre-GA tech preview (in the RTD) or it's available from RH Central after enabling Early Access. {quote}higher level of stating only components{quote} True, you get 4 features for Openshift rather than just one line item; for Fuse there are 5 features. So it's a bit more granular than just a "here are the 17 projects in jbosstools" list, like if you look at https://github.com/jbosstools or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... {quote}who is going to scan that 1k line document{quote} Well that's the $1k question. Who actually WANTS this document, and what level of detail do they need? This feels like an exercise in "hot potato" crossed with "if we build it, *maybe* they will come?" :D > Document list of features, versions, and quality status of devstudio 11 contents > -------------------------------------------------------------------------------- > > Key: JBDS-4461 > URL: https://issues.jboss.org/browse/JBDS-4461 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 11.0.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.GA > > Attachments: whats-in-devstudio-features-plugins-only.txt, whats-in-devstudio.png, whats-in-devstudio.txt > > > We need an updated document that details the list of all the stuff that's in devstudio 11. > This can be based on https://docs.google.com/spreadsheets/d/1xOgXaeXSZOc0AFIhwzaKQIzCJpMQS8d-r... but needs to be a fresh document as much of the content has changed, upversioned or been removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4461) Document list of features, versions, and quality status of devstudio 11 contents

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4461?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4461 at 7/19/17 2:57 PM: ----------------------------------------------------------- {quote}Is there a way to make the output a little less computer and a little more human readable? {quote} Yes, someone could write a parsing script to strip out dupe/undesired info. {quote}If we could massage the data to strip some of the information and present it in easier to read/sort, it might work.{quote} We could parse the data into CSV so it could then be imported to a Google Doc spreadsheet. Then you can sort/format to your heart's content. :D {quote}It also doesn't state quality of the version{quote} True, but everything is GA at this point unless it's explicitly called out as pre-GA tech preview (in the RTD) or it's available from RH Central after enabling Early Access. {quote}higher level of stating only components{quote} True, you get 4 features for Openshift rather than just one line item; for Fuse there are 5 features. So it's a bit more granular than just a "here are the 17 projects in jbosstools" list, like if you look at https://github.com/jbosstools or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... {quote}who is going to scan that 1k line document{quote} Well that's the $1k question. Who actually WANTS this document, and what level of detail do they need? This feels like an exercise in "hot potato" crossed with "if we build it, *maybe* they will come?" :D was (Author: nickboldt): {quote} Is there a way to make the output a little less computer and a little more human readable? {quote} Yes, someone could write a parsing script to strip out dupe/undesired info. {quote}If we could massage the data to strip some of the information and present it in easier to read/sort, it might work.{quote} We could parse the data into CSV so it could then be imported to a Google Doc spreadsheet. Then you can sort/format to your heart's content. :D {quote}It also doesn't state quality of the version{quote} True, but everything is GA at this point unless it's explicitly called out as pre-GA tech preview (in the RTD) or it's available from RH Central after enabling Early Access. {quote}higher level of stating only components{quote} True, you get 4 features for Openshift rather than just one line item; for Fuse there are 5 features. So it's a bit more granular than just a "here are the 17 projects in jbosstools" list, like if you look at https://github.com/jbosstools or https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... {quote}who is going to scan that 1k line document{quote} Well that's the $1k question. Who actually WANTS this document, and what level of detail do they need? This feels like an exercise in "hot potato" crossed with "if we build it, *maybe* they will come?" :D > Document list of features, versions, and quality status of devstudio 11 contents > -------------------------------------------------------------------------------- > > Key: JBDS-4461 > URL: https://issues.jboss.org/browse/JBDS-4461 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 11.0.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.GA > > Attachments: whats-in-devstudio-features-plugins-only.txt, whats-in-devstudio.png, whats-in-devstudio.txt > > > We need an updated document that details the list of all the stuff that's in devstudio 11. > This can be based on https://docs.google.com/spreadsheets/d/1xOgXaeXSZOc0AFIhwzaKQIzCJpMQS8d-r... but needs to be a fresh document as much of the content has changed, upversioned or been removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4471) Update Virtualbox to latest 5.1.24 release

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4471?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4471: ----------------------------------- Assignee: Sudhir Verma (was: Denis Golovin) > Update Virtualbox to latest 5.1.24 release > ------------------------------------------ > > Key: JBDS-4471 > URL: https://issues.jboss.org/browse/JBDS-4471 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 11.0.0.AM2 > Reporter: Denis Golovin > Assignee: Sudhir Verma > Fix For: 11.0.0.GA > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4461) Document list of features, versions, and quality status of devstudio 11 contents

by Tim Moran (JIRA)

[ https://issues.jboss.org/browse/JBDS-4461?page=com.atlassian.jira.plugin.... ] Tim Moran commented on JBDS-4461: --------------------------------- Is there a way to make the output a little less computer and a little more human readable? If we could massage the data to strip some of the information and present it in easier to read/sort, it might work. It also doesn't state quality of the version and it dives a lot deeper into "features or parts" rather than at a higher level of stating only components; if we could up-level the output to look similar to the categories in the spreadsheet I think it would be easier to read. Perhaps a script? Otherwise, who is going to scan that 1k line document to try and make sense of what's what. > Document list of features, versions, and quality status of devstudio 11 contents > -------------------------------------------------------------------------------- > > Key: JBDS-4461 > URL: https://issues.jboss.org/browse/JBDS-4461 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 11.0.0.AM2 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 11.0.0.GA > > Attachments: whats-in-devstudio-features-plugins-only.txt, whats-in-devstudio.png, whats-in-devstudio.txt > > > We need an updated document that details the list of all the stuff that's in devstudio 11. > This can be based on https://docs.google.com/spreadsheets/d/1xOgXaeXSZOc0AFIhwzaKQIzCJpMQS8d-r... but needs to be a fresh document as much of the content has changed, upversioned or been removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3727) Installer fails with not normalized paths

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3727?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3727: -------------------------------- Fix Version/s: (was: 10.x) > Installer fails with not normalized paths > ----------------------------------------- > > Key: JBDS-3727 > URL: https://issues.jboss.org/browse/JBDS-3727 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > > The installer accepts installation paths with the following format: > {noformat}/home/jrichter/Downloads/xyz/../abdc/../temp/../temp{noformat} > With such a path it fails immediately after the installation starts with the following exception: > {noformat}java.io.FileNotFoundException: /home/jrichter/Downloads/xyz/../abdc/../temp/../temp/JBoss-EULA.html (No such file or directory) > at java.io.FileOutputStream.open0(Native Method) > at java.io.FileOutputStream.open(FileOutputStream.java:270) > at java.io.FileOutputStream.<init>(FileOutputStream.java:213) > at java.io.FileOutputStream.<init>(FileOutputStream.java:162) > at com.izforge.izpack.installer.Unpacker.run(Unpacker.java:448) > at java.lang.Thread.run(Thread.java:745){noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24742) [wtp] Fix / adjust parent pom for optimal efficiency

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-24742: ----------------------------------- Summary: [wtp] Fix / adjust parent pom for optimal efficiency Key: JBIDE-24742 URL: https://issues.jboss.org/browse/JBIDE-24742 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: upstream Reporter: Rob Stryker WTP's parent pom will need changes to adjust to our desired new architecture. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 July 2017