January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21532) OpenShift tooling is not compatible with EGit UI 4.1.1 from Mars.2.RC1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21532?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21532: ------------------------------------ egit mirror pulled: http://download.jboss.org/jbosstools/updates/requirements/egit/v4.1.1.201... > OpenShift tooling is not compatible with EGit UI 4.1.1 from Mars.2.RC1 > ---------------------------------------------------------------------- > > Key: JBIDE-21532 > URL: https://issues.jboss.org/browse/JBIDE-21532 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > > org.jboss.tools.openshift.egit.ui.util.EGitUIUtils calls Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR) to retrieve the defaut git repository defined in EGit. In Egit UI 4.1.1, used by Mars.2, UIPreferences.DEFAULT_REPO_DIR was removed, so the code no longer compile / will fail to run. > Simply replacing this call with Activator.getDefault().getPreferenceStore().getString("default_repository_dir") doesn't work either, because it'll return an null value -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21377: ---------------------------------------- Cost: low. Yaml editor isn't intrusive, doesn't add irrelevant noise, is a "light" feature. User impact: * for those using Yaml (hard to evaluate, but I estimate some 20%, and many early-adopters/influential people): high satisfaction * for those not using Yaml: no difference Keep in mind that Central Software installation is nice, but it's still something that many users may not even look at; and that users expect from a good IDE to not have to add anything. If we want Eclipse+JBT to be a good IDE, we should not expect users to have additional efforts to make in order to support an already popular (with growing popularity) format. Do I need to be more explicit about where my vote goes ? ;) > Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21377 > URL: https://issues.jboss.org/browse/JBIDE-21377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, jbtcentral-p2diff_460.txt > > > There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. > This would require adding it to the TP and adding a dependency from a JBT feature to it. > On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) > -- > Story points - 8 (fibonacci): > * update Central TP, > * update JBT/JBDS TPs, > * update JBT/JBDS category.xml files, > * update JBDS feature.xml, > * send announcement email re: TP changes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21377: ---------------------------------------- This question should be addressed to PM IMO. > Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21377 > URL: https://issues.jboss.org/browse/JBIDE-21377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, jbtcentral-p2diff_460.txt > > > There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. > This would require adding it to the TP and adding a dependency from a JBT feature to it. > On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) > -- > Story points - 8 (fibonacci): > * update Central TP, > * update JBT/JBDS TPs, > * update JBT/JBDS category.xml files, > * update JBDS feature.xml, > * send announcement email re: TP changes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21377: ------------------------------------ Sure, but do we need it default-installed via feature requirement, or optionally-installed via Central connector? THAT is the question up for debate here. > Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21377 > URL: https://issues.jboss.org/browse/JBIDE-21377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, jbtcentral-p2diff_460.txt > > > There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. > This would require adding it to the TP and adding a dependency from a JBT feature to it. > On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) > -- > Story points - 8 (fibonacci): > * update Central TP, > * update JBT/JBDS TPs, > * update JBT/JBDS category.xml files, > * update JBDS feature.xml, > * send announcement email re: TP changes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21377: ---------------------------------------- I'm back from a full-day of a web/mobile-oriented conference, and I believe I heard the work yaml and json about as many times each other. I believe that we do need both, equally. > Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21377 > URL: https://issues.jboss.org/browse/JBIDE-21377 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: updatesite > Affects Versions: 4.3.1.Beta1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, jbtcentral-p2diff_460.txt > > > There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default. > This would require adding it to the TP and adding a dependency from a JBT feature to it. > On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny]) > -- > Story points - 8 (fibonacci): > * update Central TP, > * update JBT/JBDS TPs, > * update JBT/JBDS category.xml files, > * update JBDS feature.xml, > * send announcement email re: TP changes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21532) OpenShift tooling is not compatible with EGit UI 4.1.1 from Mars.2.RC1

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21532?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21532: ----------------------------------- Assignee: Fred Bricon > OpenShift tooling is not compatible with EGit UI 4.1.1 from Mars.2.RC1 > ---------------------------------------------------------------------- > > Key: JBIDE-21532 > URL: https://issues.jboss.org/browse/JBIDE-21532 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > > org.jboss.tools.openshift.egit.ui.util.EGitUIUtils calls Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR) to retrieve the defaut git repository defined in EGit. In Egit UI 4.1.1, used by Mars.2, UIPreferences.DEFAULT_REPO_DIR was removed, so the code no longer compile / will fail to run. > Simply replacing this call with Activator.getDefault().getPreferenceStore().getString("default_repository_dir") doesn't work either, because it'll return an null value -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21406) Create and use Mars.2 RC1 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21406?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21406 at 1/21/16 1:15 PM: ------------------------------------------------------------- Reopening because egit, jgit, and mylyn/github features have been updated from 4.0.3 to 4.1.0/4.1.1. {code}p2diff http://download.jboss.org/jbosstools/updates/requirements/mars/20160120-0... http://download.eclipse.org/releases/maintenance/ | tee ~/tmp/rc1-rc1a.p2diff.txt{code} [^rc1-rc1a.p2diff.txt] [^rc1-rc1a.p2diff-filtered.txt] So, I'll leave 4.0.x in the min TP (4.50.2) and update the max TP (4.52.0) to use 4.1.1 instead of 4.0.3, per Fred's suggestion. Meanwhile, JBIDE-21532. was (Author: nickboldt): Reopening because egit, jgit, and mylyn/github features have been updated from 4.0.3 to 4.1.0/4.1.1. {code}p2diff http://download.jboss.org/jbosstools/updates/requirements/mars/20160120-0... http://download.eclipse.org/releases/maintenance/ | tee ~/tmp/rc1-rc1a.p2diff.txt{code} [^rc1-rc1a.p2diff.txt] [^rc1-rc1a.p2diff-filtered.txt] > Create and use Mars.2 RC1 target platform > ----------------------------------------- > > Key: JBIDE-21406 > URL: https://issues.jboss.org/browse/JBIDE-21406 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.Beta2 > > Attachments: jbds-tp-p2diff-450-summary.txt, jbds-tp-p2diff-450.txt, jbds-tp-p2diff-summary.txt, jbds-tp-p2diff.txt, jbt-tp-p2diff-450-summary.txt, jbt-tp-p2diff-450.txt, jbt-tp-p2diff-summary.txt, jbt-tp-p2diff.txt, jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, rc1-rc1a.p2diff-filtered.txt, rc1-rc1a.p2diff.txt > > > Prepare new 4.52.x TPs to use Mars.2 bits. > https://wiki.eclipse.org/index.php?title=Mars/Simultaneous_Release_Plan#M... > First RC1 bits should be available on Jan 20 (4.3.1.Beta2 TP freeze day), with EPP bundles needed for install tests on Jan 21 (code freeze day). > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build > * update install/matrix jobs to use new Eclipse JEE/platform binary > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21532) OpenShift tooling is not compatible with EGit UI 4.1.1 from Mars.2.RC1

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21532: ----------------------------------- Summary: OpenShift tooling is not compatible with EGit UI 4.1.1 from Mars.2.RC1 Key: JBIDE-21532 URL: https://issues.jboss.org/browse/JBIDE-21532 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Fred Bricon Priority: Blocker org.jboss.tools.openshift.egit.ui.util.EGitUIUtils calls Activator.getDefault().getPreferenceStore().getString(UIPreferences.DEFAULT_REPO_DIR) to retrieve the defaut git repository defined in EGit. In Egit UI 4.1.1, used by Mars.2, UIPreferences.DEFAULT_REPO_DIR was removed, so the code no longer compile / will fail to run. Simply replacing this call with Activator.getDefault().getPreferenceStore().getString("default_repository_dir") doesn't work either, because it'll return an null value -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21518) CoreException when validating wrong credentials (Unknown response code: 503)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21518?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21518: ----------------------------------- Fix Version/s: 4.3.1.CR1 4.4.0.Alpha1 > CoreException when validating wrong credentials (Unknown response code: 503) > ---------------------------------------------------------------------------- > > Key: JBIDE-21518 > URL: https://issues.jboss.org/browse/JBIDE-21518 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, runtime-detection > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0.Beta2-v20160121-0657-B250 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > Validating wrong credentials in DownloadRuntime wizard throws "An error occurred while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 503" > {noformat:title=ErrorLog} > org.eclipse.core.runtime.CoreException: Unknown response code: 503 > at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerWorkflowUtility.getWorkflowStatus(DownloadManagerWorkflowUtility.java:58) > at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.validateCredentials(DownloadManagerCredentialsFragment.java:205) > at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.access$1(DownloadManagerCredentialsFragment.java:203) > at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment$3.run(DownloadManagerCredentialsFragment.java:168) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > My blind guess is that it's relevant to https://issues.jboss.org/browse/JBIDE-21514, because I think, that correct message was displayed yesterday when one used wrong credentials. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21518) CoreException when validating wrong credentials (Unknown response code: 503)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21518?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21518: -------------------------------------- Assignee: Rob Stryker > CoreException when validating wrong credentials (Unknown response code: 503) > ---------------------------------------------------------------------------- > > Key: JBIDE-21518 > URL: https://issues.jboss.org/browse/JBIDE-21518 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, runtime-detection > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0.Beta2-v20160121-0657-B250 > Reporter: Radim Hopp > Assignee: Rob Stryker > > Validating wrong credentials in DownloadRuntime wizard throws "An error occurred while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 503" > {noformat:title=ErrorLog} > org.eclipse.core.runtime.CoreException: Unknown response code: 503 > at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerWorkflowUtility.getWorkflowStatus(DownloadManagerWorkflowUtility.java:58) > at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.validateCredentials(DownloadManagerCredentialsFragment.java:205) > at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment.access$1(DownloadManagerCredentialsFragment.java:203) > at org.jboss.tools.runtime.ui.internal.wizard.workflow.DownloadManagerCredentialsFragment$3.run(DownloadManagerCredentialsFragment.java:168) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > {noformat} > My blind guess is that it's relevant to https://issues.jboss.org/browse/JBIDE-21514, because I think, that correct message was displayed yesterday when one used wrong credentials. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 January 2016