[JBoss JIRA] (JBIDE-14856) OpenShift Explorer: should be able to remove several connections at once
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14856?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14856:
-------------------------------------
Fix Version/s: 4.2.0.Alpha1
(was: 4.2.x)
> OpenShift Explorer: should be able to remove several connections at once
> ------------------------------------------------------------------------
>
> Key: JBIDE-14856
> URL: https://issues.jboss.org/browse/JBIDE-14856
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.0.Alpha1
>
>
> steps to reproduce:
> # ASSER: make sure you have several connections available in *OpenShift Explorer*
> # EXEC: select them all and open up the context menu
> Result:
> You cannot choose *Remove from view* for all the selected connections. You have select them one by one and remove them.
> Expected result:
> You can select all your connections and remove them all at once.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-14768) Inform users about invalid SSL certificates and allow them to accept/refuse them
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14768?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14768:
-------------------------------------
Fix Version/s: 4.2.0.Alpha1
(was: 4.2.x)
> Inform users about invalid SSL certificates and allow them to accept/refuse them
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-14768
> URL: https://issues.jboss.org/browse/JBIDE-14768
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
>
> In JBIDE-10447 the openshift-java-client disabled the checks for SSL certificates since those prevented users from connecting to internal/private OpenShift instances:
> {code:title=UrlConnectionHttpClient}
> private HttpURLConnection createConnection(String userAgent, URL url) throws IOException {
> HttpURLConnection connection = (HttpURLConnection) url.openConnection();
> if (isHttps(url)
> && !doSSLChecks) {
> HttpsURLConnection httpsConnection = (HttpsURLConnection) connection;
> httpsConnection.setHostnameVerifier(new NoopHostnameVerifier());
> setPermissiveSSLSocketFactory(httpsConnection);
> }
> private boolean isHttps(URL url) {
> return "https".equals(url.getProtocol());
> }
> /**
> * Sets a trust manager that will always trust.
> * <p>
> * TODO: dont swallog exceptions and setup things so that they dont disturb other components.
> */
> private void setPermissiveSSLSocketFactory(HttpsURLConnection connection) {
> try {
> SSLContext sslContext = SSLContext.getInstance("SSL");
> sslContext.init(new KeyManager[0], new TrustManager[] { new PermissiveTrustManager() }, new SecureRandom());
> SSLSocketFactory socketFactory = sslContext.getSocketFactory();
> ((HttpsURLConnection) connection).setSSLSocketFactory(socketFactory);
> } catch (KeyManagementException e) {
> // ignore
> } catch (NoSuchAlgorithmException e) {
> // ignore
> }
> }
> private static class PermissiveTrustManager implements X509TrustManager {
> public X509Certificate[] getAcceptedIssuers() {
> return null;
> }
> public void checkServerTrusted(X509Certificate[] chain,
> String authType) throws CertificateException {
> }
> public void checkClientTrusted(X509Certificate[] chain,
> String authType) throws CertificateException {
> }
> }
> private static class NoopHostnameVerifier implements HostnameVerifier {
> public boolean verify(String hostname, SSLSession sslSession) {
> return true;
> }
> }
> {code}
> We should not simply disable these SSL checks but allow users to accept/refuse them via a dialog
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-14768) Inform users about invalid SSL certificates and allow them to accept/refuse them
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14768?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14768:
-------------------------------------
Fix Version/s: 4.2.x
(was: 4.2.0.Alpha1)
> Inform users about invalid SSL certificates and allow them to accept/refuse them
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-14768
> URL: https://issues.jboss.org/browse/JBIDE-14768
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
>
> In JBIDE-10447 the openshift-java-client disabled the checks for SSL certificates since those prevented users from connecting to internal/private OpenShift instances:
> {code:title=UrlConnectionHttpClient}
> private HttpURLConnection createConnection(String userAgent, URL url) throws IOException {
> HttpURLConnection connection = (HttpURLConnection) url.openConnection();
> if (isHttps(url)
> && !doSSLChecks) {
> HttpsURLConnection httpsConnection = (HttpsURLConnection) connection;
> httpsConnection.setHostnameVerifier(new NoopHostnameVerifier());
> setPermissiveSSLSocketFactory(httpsConnection);
> }
> private boolean isHttps(URL url) {
> return "https".equals(url.getProtocol());
> }
> /**
> * Sets a trust manager that will always trust.
> * <p>
> * TODO: dont swallog exceptions and setup things so that they dont disturb other components.
> */
> private void setPermissiveSSLSocketFactory(HttpsURLConnection connection) {
> try {
> SSLContext sslContext = SSLContext.getInstance("SSL");
> sslContext.init(new KeyManager[0], new TrustManager[] { new PermissiveTrustManager() }, new SecureRandom());
> SSLSocketFactory socketFactory = sslContext.getSocketFactory();
> ((HttpsURLConnection) connection).setSSLSocketFactory(socketFactory);
> } catch (KeyManagementException e) {
> // ignore
> } catch (NoSuchAlgorithmException e) {
> // ignore
> }
> }
> private static class PermissiveTrustManager implements X509TrustManager {
> public X509Certificate[] getAcceptedIssuers() {
> return null;
> }
> public void checkServerTrusted(X509Certificate[] chain,
> String authType) throws CertificateException {
> }
> public void checkClientTrusted(X509Certificate[] chain,
> String authType) throws CertificateException {
> }
> }
> private static class NoopHostnameVerifier implements HostnameVerifier {
> public boolean verify(String hostname, SSLSession sslSession) {
> return true;
> }
> }
> {code}
> We should not simply disable these SSL checks but allow users to accept/refuse them via a dialog
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15467) should JBT have a category for "stuff not in Abridged" ?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15467?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-15467 at 9/9/13 9:55 AM:
------------------------------------------------------------
"Abriged" means "core subset".
"Non-abridged" means "superset, including everything".
Therefore non-abridged cannot also be "Additional" because it would include EVERYTHING, not just the complimentary features.
Either we have an "All the features in a single category" or we have "Additional features not in the 'Abridged' category".
--
Here's what I'm suggesting: a new category right next to the existing "*Abridged JBoss Tools" category, which would include everything else on the site which is NOT in the Abridged category, but which is therefore additional.
Of course those features would also appear in other categories, like the Aerogear and Cordova stuff in Mobile:
!15467.png!
WDYT?
was (Author: nickboldt):
Here's what I'm suggesting: a new category right next to the existing "*Abridged JBoss Tools" category, which would include everything else on the site which is NOT in the Abridged category, but which is additional.
Of course those features would also appear in other categories, like the Aerogear and Cordova stuff in Mobile:
!15467.png!
WDYT?
> should JBT have a category for "stuff not in Abridged" ?
> --------------------------------------------------------
>
> Key: JBIDE-15467
> URL: https://issues.jboss.org/browse/JBIDE-15467
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.1.1.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.1.Alpha2
>
> Attachments: 15467.png
>
>
> The Marketplace entry for JBT includes all the features in the "Abridged JBoss Tools" category, but there are a number of features not included therein.
> So for those users installing from the update site itself, not the Marketplace, should these be grouped into a single category, perhaps called "Additional JBoss Tools"?
> {code}
> org.jboss.tools.arquillian.feature
> org.jboss.tools.common.mylyn.feature
> org.jboss.tools.gwt.feature
> org.jboss.tools.maven.gwt.feature
> org.jboss.tools.aerogear.hybrid.feature
> org.jboss.tools.vpe.cordovasim.feature
> org.jboss.tools.central.themes.feature
> org.jboss.tools.birt.feature
> org.jboss.tools.forge.ext.feature
> {code}
> Added bonus (from a releng P.O.V., not an end user one) is that having such a category would make it easier to maintain the full list of features to be included in these job configs, to ensure we're properly doing full JBT co-installation testing:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite...
> [~burrsutter] [~maxandersen] [~koen.aers] [~gercan] WDYT?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15467) should JBT have a category for "stuff not in Abridged" ?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15467?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-15467:
-------------------------------
Attachment: 15467.png
Here's what I'm suggesting: a new category right next to the existing "*Abridged JBoss Tools" category, which would include everything else on the site which is NOT in the Abridged category, but which is additional.
Of course those features would also appear in other categories, like the Aerogear and Cordova stuff in Mobile:
!15467.png!
WDYT?
> should JBT have a category for "stuff not in Abridged" ?
> --------------------------------------------------------
>
> Key: JBIDE-15467
> URL: https://issues.jboss.org/browse/JBIDE-15467
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.1.1.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.1.Alpha2
>
> Attachments: 15467.png
>
>
> The Marketplace entry for JBT includes all the features in the "Abridged JBoss Tools" category, but there are a number of features not included therein.
> So for those users installing from the update site itself, not the Marketplace, should these be grouped into a single category, perhaps called "Additional JBoss Tools"?
> {code}
> org.jboss.tools.arquillian.feature
> org.jboss.tools.common.mylyn.feature
> org.jboss.tools.gwt.feature
> org.jboss.tools.maven.gwt.feature
> org.jboss.tools.aerogear.hybrid.feature
> org.jboss.tools.vpe.cordovasim.feature
> org.jboss.tools.central.themes.feature
> org.jboss.tools.birt.feature
> org.jboss.tools.forge.ext.feature
> {code}
> Added bonus (from a releng P.O.V., not an end user one) is that having such a category would make it easier to maintain the full list of features to be included in these job configs, to ensure we're properly doing full JBT co-installation testing:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite...
> [~burrsutter] [~maxandersen] [~koen.aers] [~gercan] WDYT?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15285) Increment minor version of jbosstools-base/foundation submodule
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15285?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-15285:
-----------------------------------
Assignee: Denis Golovin (was: Daniel Azarov)
I would like to note here that the package "Trace" is added in is NOT a public package. It is a private package marked with xfriends for easy testing.
There is a bug tracking this issue upstream in eclipse: https://bugs.eclipse.org/bugs/show_bug.cgi?id=230279
In the future, please do not bump versions so quickly, but rather assign the bug to the proper owner, who can either make an API Filter for the added class, or, bump the version.
In this specific case, bumping the version was incorrect. But, we won't need to change the version back, as new real API has just been added.
But in the future, do not bump so quickly.
You may close this issue again as you see fit. No changes are needed on your end. It was re-opened merely so you would look at it.
> Increment minor version of jbosstools-base/foundation submodule
> ---------------------------------------------------------------
>
> Key: JBIDE-15285
> URL: https://issues.jboss.org/browse/JBIDE-15285
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core
> Affects Versions: 4.2.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: versioning
> Fix For: 4.2.0.Alpha1
>
>
> New class [Trace|https://github.com/jbosstools/jbosstools-base/commit/0e97d80209db88...] was introduced in Public API of foundation submodule, thus minor version should be incremented.
> 1.0.0-SNAPSHOT -> 1.1.0-SNAPSHOT
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-15469) {MASTER] CLONE - Increment version's service part for jbosstools-base/foundation submodule
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15469?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-15469.
---------------------------------
Resolution: Out of Date
Seems thsi was already bumped (incorrectly) previously: see JBIDE-15285
> {MASTER] CLONE - Increment version's service part for jbosstools-base/foundation submodule
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-15469
> URL: https://issues.jboss.org/browse/JBIDE-15469
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core
> Affects Versions: 4.1.1.Alpha1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.1.1.Alpha1
>
>
> jbosstools-base/foundation submodule had changes since 4.1.0.Final is released:
> {code}$ git diff --name-only jbosstools-4.1.0.Final -- foundation
> foundation/plugins/org.jboss.tools.foundation.core/.options
> foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/Trace.java
> foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/ecf/internal/InternalURLTransport.java
> foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/ecf/internal/URLTransportCache.java
> foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/BarrierProgressWaitJob.java
> foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/BarrierWaitJob.java
> foundation/plugins/org.jboss.tools.foundation.core/src/org/jboss/tools/foundation/core/jobs/InterruptableJoinJob.java
> foundation/pom.xml{code}
> No changes in Public API so far and hat means only service version should be incremented:
> 1.0.0-SNAPSHOT => 1.0.1-SNAPSHOT
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months
[JBoss JIRA] (JBIDE-13963) Port-Forwarding: wizard dialog should have "Cancel", "Start" and "Stop" buttons (not "OK" in the bottom & "Start All", "Stop All" to the right of the ports)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13963?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13963:
-------------------------------------
Summary: Port-Forwarding: wizard dialog should have "Cancel", "Start" and "Stop" buttons (not "OK" in the bottom & "Start All", "Stop All" to the right of the ports) (was: Improve the port-forwarding wizard UI)
> Port-Forwarding: wizard dialog should have "Cancel", "Start" and "Stop" buttons (not "OK" in the bottom & "Start All", "Stop All" to the right of the ports)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13963
> URL: https://issues.jboss.org/browse/JBIDE-13963
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: OpenShift_portforward.png
>
>
> the wizard buttons are a bit misleading: clicking on "Ok" at the bottom of the wizard closes the wizard but does not start or stop the port-forwarding (I got that problem a few times when I was preparing a demo).
> I think the wizard buttons should rather be "Start"/"Cancel" or "Stop/Cancel".
> The "Start all" and "stop all" buttons on the side of the tables should be removed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 7 months