[JBoss JIRA] (JBIDE-14890) Application wizard: Use EGit recursive merge instead of copying git repository
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14890?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-14890:
-------------------------------------
Summary: Application wizard: Use EGit recursive merge instead of copying git repository (was: Use EGit recursive merge instead of copying git repository)
> Application wizard: Use EGit recursive merge instead of copying git repository
> ------------------------------------------------------------------------------
>
> Key: JBIDE-14890
> URL: https://issues.jboss.org/browse/JBIDE-14890
> 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
>
> Attachments: user-existing-project.png
>
>
> OpenShift tooling is working around missing recursive merge when importing into an existing Project ("use existing")
> !user-existing-project.png!
> When using the git command line one is told to merge by using the recursive merge startegy:
> {code}
> git merge -s recursive -X ours foo
> {code}
> When we created the JBoss Tools for OpenShift there was no recursive merge in EGit/JGit. We therefore worked around it by cloning the OpenShift repository and copying stuff over.
> EGit 3.0 introduced the recursive merge strategy and put it to the default that's being used:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=380314#c22
--
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, 4 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:
-------------------------------------
Summary: Connection dialog: Inform users about invalid SSL certificates and allow them to accept/refuse them (was: Inform users about invalid SSL certificates and allow them to accept/refuse them )
> 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
> 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, 4 months
[JBoss JIRA] (JBIDE-16222) Web services with CXF 2.x runtime deployment with Exceptions
by Radoslav Rábara (JIRA)
Radoslav Rábara created JBIDE-16222:
---------------------------------------
Summary: Web services with CXF 2.x runtime deployment with Exceptions
Key: JBIDE-16222
URL: https://issues.jboss.org/browse/JBIDE-16222
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.1.1.CR1
Reporter: Radoslav Rábara
Fix For: 4.2.x
Attachments: cxf server.log
Exceptions occurs during deployment of Web Service with CXF 2.4.6 runtime on EAP 6.1 . Project is successfully deployed but "org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054" is thrown during deployment
--
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, 4 months