April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3860) JBDS 9.1 not connecting to internet

by Nichola Moore (JIRA)

[ https://issues.jboss.org/browse/JBDS-3860?page=com.atlassian.jira.plugin.... ] Nichola Moore commented on JBDS-3860: ------------------------------------- Hi [~nickboldt] and [~apodhrad], In an interesting turn of events, it seems that the issue was a bug in Fedora 23. See https://forums.aws.amazon.com/message.jspa?messageID=716342#716342 for more details. I had to get help from [~hghasemb] because the P2-browser wouldn't build. I upgraded to Fedora 23 on the 26th March. This bug was discovered on 26th March. After much googling and trying to work out why there were access errors on the secure Maven repositories, Hooman discovered the forum entry and we updated Fedora. JBDS 9.1 now works and I have installed JBDSIS. That's one for the release notes. An excerpt from the Amazon forum: For any other fedora users: it has a patch applied, so the base version has not updated. The buggy one is 1.8.0.91-1 and the correctly patched one is 1.8.0.91-2 Thanks for all your efforts. To answer your questions above - Yes I added https://devstudio.redhat.com/9.0/staging/ because I was following a set of instructions provided before the 9.1 GA. I tried the JBDSIS staging to see if I could get to it. I uninstalled and reinstalled JBDS 9.1 and created a new workspace. I did originally reuse the old JBDS 8 workspace so that would have been a problem > JBDS 9.1 not connecting to internet > ----------------------------------- > > Key: JBDS-3860 > URL: https://issues.jboss.org/browse/JBDS-3860 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.1.0.GA > Reporter: Nichola Moore > Assignee: Nick Boldt > Attachments: JBDS9.1_bug.png, JBDS9.1_error_log.png, JBDS9.1_whole_screen.png, jbds_error_log.txt > > > I have downloaded and installed JBDS 9.1.0 GA on to Fedora 23. > When I try to get to JBDS-IS on Red Hat Central > Software/Update I get the error shown in the attached screenshot [1] in a pop-up window. > The rest of the screen looks like the screenshot at [2] when I click OK on the pop-up window. > [1] JBDS9.1_bug.png > [2] JBDS9.1_whole_screen.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-165) Refactor the Connection Wizard [EBZ#492420]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-165?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-165: ------------------------------ Sprint: devex #113 April 2016 > Refactor the Connection Wizard [EBZ#492420] > ------------------------------------------- > > Key: ERT-165 > URL: https://issues.jboss.org/browse/ERT-165 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > Refactor the connection wizard to provide: > - a table with all existing Docker instances (native, Docker for Mac/Windows and Docker Machine) > - a simplified form to specify custom settings, more directly based on the env variables that are used by the Docker CLI client (DOCKER_HOST, DOCKER_TLS_VERIFY and DOCKER_CERT_PATH) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22215) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Webservices]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22215?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-22215. --------------------------------- Resolution: Done Done: no missing commit in {{master}} branch, all reported commits are false positives or unrelated commits (prepare for 4.3.1.CR1, etc.). > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Webservices] > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22215 > URL: https://issues.jboss.org/browse/JBIDE-22215 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Rob Stryker > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Webservices]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-webservices at https://github.com/jbosstools/jbosstools-webservices/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "6aa98d" is the last common ancestor of jbosstools-4.3.x and master > 6aa98d is 6 commits ago in branch master > 6aa98d is 8 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-webservices//commit/22de6f979a60... > - https://github.com/jbosstools/jbosstools-webservices//commit/0e9928f3f5ca... > - https://github.com/jbosstools/jbosstools-webservices//commit/6a071b8e9bb6... > - https://github.com/jbosstools/jbosstools-webservices//commit/ff6841f2dac9... > - https://github.com/jbosstools/jbosstools-webservices//commit/ce92ff639574... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Webservices task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22195) Docker-machine look-up does not work

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22195?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-22195: --------------------------------------- Will be outdated once ERT-165 is done. > Docker-machine look-up does not work > ------------------------------------ > > Key: JBIDE-22195 > URL: https://issues.jboss.org/browse/JBIDE-22195 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha1 > > > The {{Search...}} dialog for Docker Machines in the New Connection wizard in the Docker tooling does not work: a warning message appears in the Error Log view, saying : > {quote} > The 'docker-machine' command could not be located in /usr/bin:/bin:/usr/sbin:/sbin > {quote} > even though the preferences show that the {{docker-machine}} command is located in {{/usr/local/bin}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22219) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [LiveReload]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22219?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-22219. --------------------------------- Resolution: Done Done: no missing commit in {{master}} branch, all reported commits are false positives or unrelated commits (prepare for 4.3.1.CR1, etc.). > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [LiveReload] > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22219 > URL: https://issues.jboss.org/browse/JBIDE-22219 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Rob Stryker > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [LiveReload]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-livereload at https://github.com/jbosstools/jbosstools-livereload/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "b49e9d" is the last common ancestor of jbosstools-4.3.x and master > b49e9d is 16 commits ago in branch master > b49e9d is 15 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-livereload//commit/bf3ca4c56fe7a... > - https://github.com/jbosstools/jbosstools-livereload//commit/eeaa6e4f032ce... > - https://github.com/jbosstools/jbosstools-livereload//commit/c3748dc829f05... > - https://github.com/jbosstools/jbosstools-livereload//commit/5db3bdee91271... > - https://github.com/jbosstools/jbosstools-livereload//commit/a1dd89ea861e9... > - https://github.com/jbosstools/jbosstools-livereload//commit/bc88160f5bf7d... > - https://github.com/jbosstools/jbosstools-livereload//commit/43ff18a8b49d0... > - https://github.com/jbosstools/jbosstools-livereload//commit/cda733cfa345b... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for LiveReload task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3794) Installer - We should document the uninstall steps

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBDS-3794?page=com.atlassian.jira.plugin.... ] Misha Ali commented on JBDS-3794: --------------------------------- Hi, [~jrichter1], I've fixed the first two issue, but am unsure what we want to say about the VAGRANT_DETECTED_OS env variable. Can you tell me about what it is used for in this context, or whether users need to set it, etc.? > Installer - We should document the uninstall steps > -------------------------------------------------- > > Key: JBDS-3794 > URL: https://issues.jboss.org/browse/JBDS-3794 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: documentation, platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: havoc > Fix For: 10.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-175) Add xml validator option to ignore "Referenced file contains errors" error [EBZ#491313]

by Friendly Jira Robot (JIRA)

[ https://issues.jboss.org/browse/ERT-175?page=com.atlassian.jira.plugin.sy... ] Friendly Jira Robot resolved ERT-175. ------------------------------------- Resolution: Done > Add xml validator option to ignore "Referenced file contains errors" error [EBZ#491313] > --------------------------------------------------------------------------------------- > > Key: ERT-175 > URL: https://issues.jboss.org/browse/ERT-175 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Priority: Trivial > Labels: 3.8_M7, bzira, wst.xml > Fix For: Neon (4.6) M7 > > > The biggest problems we have for our customers is when the customer's xml file is fine, but validating against an imperfect schema upstream ends up with an error like this: > "Referenced file contains errors (file:/home/rob/apps/eclipse/builds/tp/4.60.x_20160308/../../../../../code/jbtools/github/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema/xsd/ourBundledSchema.xsd). For > more information, right click on the message in the Problems View and select "Show Details..." > It'd be great if we had an xml validator option to allow this to be an error, a warning, or even ignored. > Since this is our most common error for users, we consider it a pretty high priority request. We'd be willing to do some of the work if you could point us to where such a thing could be implemented easily (or even not easily... at least a starting-off point). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-175) Add xml validator option to ignore "Referenced file contains errors" error [EBZ#491313]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-175: --------------------------------------- Summary: Add xml validator option to ignore "Referenced file contains errors" error [EBZ#491313] Key: ERT-175 URL: https://issues.jboss.org/browse/ERT-175 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Friendly Jira Robot Priority: Trivial Fix For: Neon (4.6) M7 The biggest problems we have for our customers is when the customer's xml file is fine, but validating against an imperfect schema upstream ends up with an error like this: "Referenced file contains errors (file:/home/rob/apps/eclipse/builds/tp/4.60.x_20160308/../../../../../code/jbtools/github/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema/xsd/ourBundledSchema.xsd). For more information, right click on the message in the Problems View and select "Show Details..." It'd be great if we had an xml validator option to allow this to be an error, a warning, or even ignored. Since this is our most common error for users, we consider it a pretty high priority request. We'd be willing to do some of the work if you could point us to where such a thing could be implemented easily (or even not easily... at least a starting-off point). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-732) JBDS-IS 9.0.0 GA Release Notes

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-732?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-732: ------------------------------------ Thanks, [~apodhrad]. Fixes: - Section 2 * s/9.0.0 Beta/ 9.0.0 GA * s/Integration Stack 8.0.5/Integration Stack 8.0.6 * Added .Final to BPMB2 modeller - Section 3.1: Added .Final to BPMN2 modeller title - Section 3.2: Updated Drools issues Please have a look and let me know if there are any further fixes required. > JBDS-IS 9.0.0 GA Release Notes > ------------------------------ > > Key: TOOLSDOC-732 > URL: https://issues.jboss.org/browse/TOOLSDOC-732 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create Release Notes for GA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-701) JBDS 9.1 GA: Additional OpenShift v3 functionality and change support info

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-701?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-701: ------------------------------- Sprint: 18-Jan >> 31-Jan 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 25-Apr >> 08-May 2016-JBDS/JBT (was: 18-Jan >> 31-Jan 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT) > JBDS 9.1 GA: Additional OpenShift v3 functionality and change support info > -------------------------------------------------------------------------- > > Key: TOOLSDOC-701 > URL: https://issues.jboss.org/browse/TOOLSDOC-701 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 Beta2 > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: OpenShiftv3 > > Document the additional OpenShift v3 functionality in JBDS 9.1 and update support information in existing OSv3 articles to remove the tech preview warnings. > Summary: > - [Server Adapter to start/stop/restart/auto-configure the CDK's Vagrant VM|https://issues.jboss.org/browse/JBIDE-20990?jql=project%20%3D%20%22Too...] > - [oc new-app|https://issues.jboss.org/browse/JBIDE-21372] > - oc edit > - oc sync (via server adapter) > - [logical view|https://issues.jboss.org/browse/JBIDE-3229?jql=project%20%3D%20%22To...] > - [import existing project (pom.xml, dockerfile)|https://issues.jboss.org/browse/JBIDE-3229?jql=project%20%3D%...] > - [run/build as launch configurations so users can rerun|https://issues.jboss.org/browse/JBIDE-9442?jql=project%20%3D%20%22T...] > I'm creating a subtask for each of these issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016