April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-625) JBDS-IS 8.0.1: Create an article about upgrading from previous to current version of JBDS-IS

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-625?page=com.atlassian.jira.plug... ] Supriya Bharadwaj resolved TOOLSDOC-625. ---------------------------------------- Resolution: Done > JBDS-IS 8.0.1: Create an article about upgrading from previous to current version of JBDS-IS > -------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-625 > URL: https://issues.jboss.org/browse/TOOLSDOC-625 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > > From Petr's feedback: > c) instructions on upgrading and uninstalling the IS are missing altogether, compared to the Fuse Tooling installation guide > JBDS-IS docs team has committed to this in time for GA. > * Create and populate the upgrading article > * Send link to Gemma for B*MS splash page -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-624) JBDS-IS 8.0.1: Update Install Document

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-624?page=com.atlassian.jira.plug... ] Supriya Bharadwaj resolved TOOLSDOC-624. ---------------------------------------- Resolution: Done > JBDS-IS 8.0.1: Update Install Document > --------------------------------------- > > Key: TOOLSDOC-624 > URL: https://issues.jboss.org/browse/TOOLSDOC-624 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > > 1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But: > a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites. Update: Four installation instructions are provided in the Install Guide at the moment. The first two are for installing JBDS, the latter two are for JBDS-IS. The latter two should have a prerequisite step that tells you to install JBDS and links to the relevant topics (the first two ways to install). > b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18672) cannot run ionic tabs (the default) app with cordovasim

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18672?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18672: -------------------------------- Sprint: Sprint #2 April 2015 > cannot run ionic tabs (the default) app with cordovasim > ------------------------------------------------------- > > Key: JBIDE-18672 > URL: https://issues.jboss.org/browse/JBIDE-18672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.0.Final > Environment: Mac OS X, JavaFX > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Labels: upstream > Fix For: 4.3.0.Beta1 > > > run: > ionic start ionic-demo > import ionic-demo > run as > cordova sim > try use the app, click back. > Two issues: > 1) cordova sim complains about app.appexit not being supported > 2) when trying to click do not show again I get the following in the cordovasim error log: > Outstanding resource locks detected: > ES2 Vram Pool: 51,815,392 used (19.3%), 51,815,392 managed (19.3%), 268,435,456 total > 84 total resources being managed > average resource age is 15.1 frames > 0 resources at maximum supported age (0.0%) > 16 resources marked permanent (19.0%) > 17 resources have had mismatched locks (20.2%) > 17 resources locked (20.2%) > 30 resources contain interesting data (35.7%) > 0 resources disappeared (0.0%) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19060) Update version identifiers to 5.0.0

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19060?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-19060. -------------------------------- Verified with JBDS 9.0.0.Alpha1 > Update version identifiers to 5.0.0 > ----------------------------------- > > Key: JBIDE-19060 > URL: https://issues.jboss.org/browse/JBIDE-19060 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19055) Rename org.jboss.tools.hibernate.libs.beanshell into org.jboss.tools.hibernate.libs.bsh.v_2_0_b4

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19055?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-19055. -------------------------------- Verified with JBDS 9.0.0.Alpha1 > Rename org.jboss.tools.hibernate.libs.beanshell into org.jboss.tools.hibernate.libs.bsh.v_2_0_b4 > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-19055 > URL: https://issues.jboss.org/browse/JBIDE-19055 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19054) Rename org.jboss.tools.hibernate.spi into org.jboss.tools.hibernate.runtime.spi

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19054?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-19054. -------------------------------- > Rename org.jboss.tools.hibernate.spi into org.jboss.tools.hibernate.runtime.spi > ------------------------------------------------------------------------------- > > Key: JBIDE-19054 > URL: https://issues.jboss.org/browse/JBIDE-19054 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19117) Rename org.jboss.tools.hibernate3_5 into org.jboss.tools.hibernate.runtime.v_3_5

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19117?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-19117. -------------------------------- Verified with JBDS 9.0.0.Alpha1 > Rename org.jboss.tools.hibernate3_5 into org.jboss.tools.hibernate.runtime.v_3_5 > -------------------------------------------------------------------------------- > > Key: JBIDE-19117 > URL: https://issues.jboss.org/browse/JBIDE-19117 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19083) Rename org.jboss.tools.hibenate.spi.test into org.jboss.tools.hibernate.runtime.spi.test

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19083?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-19083. -------------------------------- > Rename org.jboss.tools.hibenate.spi.test into org.jboss.tools.hibernate.runtime.spi.test > ---------------------------------------------------------------------------------------- > > Key: JBIDE-19083 > URL: https://issues.jboss.org/browse/JBIDE-19083 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19080) Rename org.jboss.tools.hibernate.spi into org.jboss.tools.hibernate.runtime.spi

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19080?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-19080. -------------------------------- Plugin renamed, verified with JBDS 9.0.0.Alpha2 nightly. > Rename org.jboss.tools.hibernate.spi into org.jboss.tools.hibernate.runtime.spi > ------------------------------------------------------------------------------- > > Key: JBIDE-19080 > URL: https://issues.jboss.org/browse/JBIDE-19080 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19594) SSL callback: provide meaningful hostname verifier, stop always accepting hostnames

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19594?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19594: ------------------------------------- Summary: SSL callback: provide meaningful hostname verifier, stop always accepting hostnames (was: SSL callback: provide meaningful hostname verifier, drop always accepting hostnames) > SSL callback: provide meaningful hostname verifier, stop always accepting hostnames > ----------------------------------------------------------------------------------- > > Key: JBIDE-19594 > URL: https://issues.jboss.org/browse/JBIDE-19594 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > > We're currently using an SSL callback that will allow users to get informed and act upon "faulty" certificates (ex. self-signed ones) and mismatches btw. the host we're talking to and the one that is referenced in the ssl certificate: > {code:title=com.openshift.client.IHttpClient.ISSLCertificateCallback} > public interface ISSLCertificateCallback { > public boolean allowCertificate(X509Certificate[] chain); > public boolean allowHostname(String hostname, SSLSession session); > } > {code} > The callback that we are using in JBT is presenting a dialog in case the jdk cannot verify the certificate (ex. self signed certificates) and allows the user to accept/deny it. > In case the jdk cannot verify the hostname (the host we're talking to is not matching the host that's referenced in the certificate) we're currently always accepting the hostname: > {code:title=org.jboss.tools.openshift.express.internal.ui.wizard.connection.SSLCertificateCallback} > @Override > public boolean allowHostname(String hostname, SSLSession sslSession) { > return true; > } > {code} > We should find a meaningfull implementation of such a verification that does not simply always accept it. A first idea would be to present the mismatch to the user and allow it to accept/refute it. > This issue came up JBIDE-19581 when there was no callback installed which made the hostname verification fail as in jdk. When fetching the quickstarts OSJC is reaching out to https://hub.openshift.com (https://hub.openshift.com/api/v1/quickstarts/promoted.json) while the ssl certificate presented only covers openshift.redhat.com: > {code} > * Server certificate: > * subject: CN=openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US > * start date: Jul 23 00:00:00 2014 GMT > * expire date: Jul 27 12:00:00 2017 GMT > * common name: openshift.redhat.com > * issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 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 April 2015