[JBoss JIRA] (JBDS-2709) Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ]
Radim Hopp closed JBDS-2709.
----------------------------
> Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central
> ----------------------------------------------------------
>
> Key: JBDS-2709
> URL: https://issues.jboss.org/browse/JBDS-2709
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central, updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Vlado Pakan
> Fix For: 7.1.0.GA
>
>
> As reported here:
> https://issues.jboss.org/browse/JBDS-2485?focusedCommentId=12791354&page=...
> {quote}
> Subclipse 1.10 has support for the new 1.8 working copy format, which is the format used by the current stable versions of Windows tools like TortoiseSVN and SlikSVN.
> http://subclipse.tigris.org/update_1.10.x
> Local repository compatibility between these tools and JBDS is very nice to have.
> Unfortunately, this version of SubClipse supports only JavaHL, not SVNKit, because version 1.8.0 of the latter is still in alpha. And since we can't reliably use JavaHL (see JBIDE-14795), using 1.8.0 is out of the question.
> {quote}
> http://www.svnkit.com/download.php
> Once there's a more stable version of SVNKit 1.8 that works with Subclipse 1.10, we can explore updating Central to include the newer version.
--
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, 2 months
[JBoss JIRA] (JBIDE-16592) Allow to update/remove software installed from Central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16592?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-16592 at 2/18/14 3:20 AM:
-----------------------------------------------------------------
The "Show install" checkbox is probably about to disappear. A unit currently has 2 possible status (INSTALLED or NOT INSTALLED). With support of updates, it will add another possible status (UPDATE AVAILABLE). Early access support (cf JBIDE-16375) will probably add yet another status (EARLY ACCESS INSTALLED or something like that).
So I don't believe we should take the checkbox into account. I could actually remove it now.
I also plan to add colors for status:
* Not Installed: grey or black
* Installed: green
* Update available: orange
was (Author: mickael_istria):
The "Show install" checkbox is probably about to disappear. A unit currently has 2 possible status (INSTALLED or NOT INSTALLED). With support of updates, it will add another possible status (UPDATE AVAILABLE). Early access support (cf JBIDE-16375) will probably add yet another status (EARLY ACCESS INSTALLED or something like that).
So I don't believe we should take the checkbox into account. I could actually remove it now.
> Allow to update/remove software installed from Central
> ------------------------------------------------------
>
> Key: JBIDE-16592
> URL: https://issues.jboss.org/browse/JBIDE-16592
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta1
>
> Attachments: JBIDE-16592-wip.jpeg
>
>
> Central software page should allow user to update or uninstall some modules.
--
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, 2 months
[JBoss JIRA] (JBIDE-14768) Connection dialog: 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 resolved JBIDE-14768.
--------------------------------------
Resolution: Done
> Connection dialog: 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
> Priority: Critical
> Labels: connection_wizard, new_and_noteworthy
> Fix For: 4.2.0.Alpha2
>
> Attachments: accept-certificate.png, certificate-dialog.png
>
>
> 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, 2 months
[JBoss JIRA] (JBIDE-14768) Connection dialog: 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 closed JBIDE-14768.
------------------------------------
re-closing
> Connection dialog: 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
> Priority: Critical
> Labels: connection_wizard, new_and_noteworthy
> Fix For: 4.2.0.Alpha2
>
> Attachments: accept-certificate.png, certificate-dialog.png
>
>
> 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, 2 months
[JBoss JIRA] (JBIDE-14768) Connection dialog: 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:
-------------------------------------
Labels: connection_wizard new_and_noteworthy (was: connection_wizard)
> Connection dialog: 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
> Priority: Critical
> Labels: connection_wizard, new_and_noteworthy
> Fix For: 4.2.0.Alpha2
>
> Attachments: accept-certificate.png, certificate-dialog.png
>
>
> 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, 2 months
[JBoss JIRA] (JBIDE-16592) Allow to update/remove software installed from Central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16592?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16592:
----------------------------------------
The "Show install" checkbox is probably about to disappear. A unit currently has 2 possible status (INSTALLED or NOT INSTALLED). With support of updates, it will add another possible status (UPDATE AVAILABLE). Early access support (cf JBIDE-16375) will probably add yet another status (EARLY ACCESS INSTALLED or something like that).
So I don't believe we should take the checkbox into account. I could actually remove it now.
> Allow to update/remove software installed from Central
> ------------------------------------------------------
>
> Key: JBIDE-16592
> URL: https://issues.jboss.org/browse/JBIDE-16592
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta1
>
> Attachments: JBIDE-16592-wip.jpeg
>
>
> Central software page should allow user to update or uninstall some modules.
--
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, 2 months
[JBoss JIRA] (JBDS-2842) Add UI for central connectors update
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2842?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-2842:
--------------------------------------
The big benefit of showing what can be updated from Central is to encourage users to always use the most recent version instead of sticking to an old one. In JBIDE-16592 I proposed a beginning of UI on this topic. The general idea is to add a column to each entry showing the status of this central installable unit (INSTALLED, NOT INSTALLED, UPDATE AVAILABLE...) and to replace the checkbox by selection of possible action.
[~mmurray] already provided some feedback here, you're welcome to join.
> Add UI for central connectors update
> ------------------------------------
>
> Key: JBDS-2842
> URL: https://issues.jboss.org/browse/JBDS-2842
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: central, requirements
> Affects Versions: 7.1.0.GA
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 8.0.0.Beta1
>
>
> Provide UI to inform users that there is an updated connector in JBoss Central.
> Currently, when a user has a connector installed (e.g. GPE) and this connector gets updated, the only indication of that is that the connector is visible in Central even though it has been installed (and therefore would not normally show up).
> There should be some element telling users that a given installed connector can be updated, rather than it appearing as new.
--
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, 2 months
[JBoss JIRA] (JBIDE-16592) Allow to update/remove software installed from Central
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16592?page=com.atlassian.jira.plugi... ]
Michelle Murray commented on JBIDE-16592:
-----------------------------------------
Interesting implementation but I think it is too complex and duplicates existing functionality:
* There's already a 'show installed' check box so installed/not installed are differentiated by bold and grey text so don't need explicit text 'Not Installed'
* To install user can already check the tick boxes of items they want to install and then click one install button (vs click drop down list, select install, click install button)
What I found interesting when playing around in JBoss Central Update tab is that if you click the check box for an already installed item you get a pop-up window saying item is already installed. Could we use this in some way to instead ask the user 'selecting the check box means this item will be uninstalled, are you sure you want to unistall?' We could either require users to uninstall items one at a time or, like for installing, allow users to select a number of check boxes some to be installed and some to be uninstalled and then click the install/uninstall button.
Alternatively, when user clicks 'show installed' check box - the already installed items could each have their own uninstall button like in eclipse marketplace lists.
As for how to alert users to updates, perhaps nothing needs to happen - see JBDS-2842 discussion.
> Allow to update/remove software installed from Central
> ------------------------------------------------------
>
> Key: JBIDE-16592
> URL: https://issues.jboss.org/browse/JBIDE-16592
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta1
>
> Attachments: JBIDE-16592-wip.jpeg
>
>
> Central software page should allow user to update or uninstall some modules.
--
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, 2 months
[JBoss JIRA] (JBIDE-16606) New Server Wizard updated for 'profiles'
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-16606:
-----------------------------------
Summary: New Server Wizard updated for 'profiles'
Key: JBIDE-16606
URL: https://issues.jboss.org/browse/JBIDE-16606
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: server
Affects Versions: 4.2.0.Beta1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.2.0.Beta1
With the additions of server profiles, servers in the rse profile (or others) do not necessarily require a local runtime. This means in a new server wizard, we don't need to force the user to create a runtime until they're in a profile that requires one.
This will make changes to the new server wizard workflow which may affect some swt bot tests and documentation
--
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, 2 months