June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14760) Cannot connect to OpenShift Enterprise with hostname: javax.net.ssl.SSLProtocolException (WATCHER)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14760?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-14760: ------------------------------------------------- Jason DeTiberus <jdetiber(a)redhat.com> made a comment on [bug 970805|https://bugzilla.redhat.com/show_bug.cgi?id=970805] Finally, enterprise updates: https://github.com/openshift/enterprise-server/pull/78 > Cannot connect to OpenShift Enterprise with hostname: javax.net.ssl.SSLProtocolException (WATCHER) > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-14760 > URL: https://issues.jboss.org/browse/JBIDE-14760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Environment: jdk7 > Reporter: jing zh > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta2 > > Attachments: JBT_test.png > > > If trying to connect openshift server ,it would be failed with following error shown. > Could not verify credentials for jinzhang1: Could not request https://broker.osetestv2.com/broker/rest/api: javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-2720: ----------------------------------- [~maxandersen] [~dgolovin] [~mickael_istria] [~yradtsevich] we need to decide what to do here for Beta2. Should the new Xulrunner w/ Win64 be included in JBT/JBDS out of the box? Should we wrap the single plugin w/ a feature, and put it into Central? Should the plugin be added to the JBT update site by itself, optionally installable by itself (but not in Marketplace or Central) ? Xulrunner 1.9.2 site: http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/ Xulrunner 1.9.2 w/ Win64 site: http://download.jboss.org/jbosstools/builds/staging/xulrunner-1.9.2_win64... > Need 64-bit windows support > --------------------------- > > Key: JBIDE-2720 > URL: https://issues.jboss.org/browse/JBIDE-2720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha > Reporter: Samuel Mendenhall > Assignee: Yahor Radtsevich > Fix For: 4.1.0.Beta2 > > Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png > > > If you use a 64 bit jdk, the XULRunner parts of JBoss Tools does not load. > We should look into providing a xulrunner for windows 64 bit. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14826) Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14826?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-14826. ------------------------------------ Resolution: Out of Date I can't reproduce this issue in JBoss Tools 4.1.0.Beta2 (JBDS 7.0). Seam project with EAP 6.1.0 has both classes in its classpath. So the issues seems to be fixed in the latest JBT. > Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime > --------------------------------------------------------------------------- > > Key: JBIDE-14826 > URL: https://issues.jboss.org/browse/JBIDE-14826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2, server > Affects Versions: 4.0.1.Final > Environment: JBDS 6.0.1, WFK 2.3.0.ER1 Seam 2.3.1.Final (I guess it's same for the community latest release) > Reporter: Tomas Remes > Assignee: Alexey Kazakov > Fix For: 4.1.0.Beta2 > > > When you create Seam2.3 project with EAP 6.1.0 (tech preview) runtime, the EAP libraries won't be present on its classpath. This fact cause following problems, when you try to create new Seam form or reverse engineer entities from database: > "The type javax.validation.ConstraintViolation cannot be resolved. It is indirectly referenced from required .class files" > "The project was not built since its build path is incomplete. Cannot find the class file for javax.persistence.EntityManager." -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14826) Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14826?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14826: ----------------------------------- Fix Version/s: 4.1.0.Beta2 > Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime > --------------------------------------------------------------------------- > > Key: JBIDE-14826 > URL: https://issues.jboss.org/browse/JBIDE-14826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2 > Affects Versions: 4.0.1.Final > Environment: JBDS 6.0.1, WFK 2.3.0.ER1 Seam 2.3.1.Final (I guess it's same for the community latest release) > Reporter: Tomas Remes > Fix For: 4.1.0.Beta2 > > > When you create Seam2.3 project with EAP 6.1.0 (tech preview) runtime, the EAP libraries won't be present on its classpath. This fact cause following problems, when you try to create new Seam form or reverse engineer entities from database: > "The type javax.validation.ConstraintViolation cannot be resolved. It is indirectly referenced from required .class files" > "The project was not built since its build path is incomplete. Cannot find the class file for javax.persistence.EntityManager." -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14826) Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14826?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14826: ----------------------------------- Component/s: server > Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime > --------------------------------------------------------------------------- > > Key: JBIDE-14826 > URL: https://issues.jboss.org/browse/JBIDE-14826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2, server > Affects Versions: 4.0.1.Final > Environment: JBDS 6.0.1, WFK 2.3.0.ER1 Seam 2.3.1.Final (I guess it's same for the community latest release) > Reporter: Tomas Remes > Fix For: 4.1.0.Beta2 > > > When you create Seam2.3 project with EAP 6.1.0 (tech preview) runtime, the EAP libraries won't be present on its classpath. This fact cause following problems, when you try to create new Seam form or reverse engineer entities from database: > "The type javax.validation.ConstraintViolation cannot be resolved. It is indirectly referenced from required .class files" > "The project was not built since its build path is incomplete. Cannot find the class file for javax.persistence.EntityManager." -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14826) Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14826?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-14826: -------------------------------------- Assignee: Alexey Kazakov > Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime > --------------------------------------------------------------------------- > > Key: JBIDE-14826 > URL: https://issues.jboss.org/browse/JBIDE-14826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2, server > Affects Versions: 4.0.1.Final > Environment: JBDS 6.0.1, WFK 2.3.0.ER1 Seam 2.3.1.Final (I guess it's same for the community latest release) > Reporter: Tomas Remes > Assignee: Alexey Kazakov > Fix For: 4.1.0.Beta2 > > > When you create Seam2.3 project with EAP 6.1.0 (tech preview) runtime, the EAP libraries won't be present on its classpath. This fact cause following problems, when you try to create new Seam form or reverse engineer entities from database: > "The type javax.validation.ConstraintViolation cannot be resolved. It is indirectly referenced from required .class files" > "The project was not built since its build path is incomplete. Cannot find the class file for javax.persistence.EntityManager." -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14537) BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14537?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-14537. -------------------------------- Resolution: Done [~kmarmaliykov] blocked by upstream issue: JBIDE-14833, otherwise yes I agree. :) > BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent > -------------------------------------------------------------------------------- > > Key: JBIDE-14537 > URL: https://issues.jboss.org/browse/JBIDE-14537 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.0.Beta1 > Reporter: Yahor Radtsevich > Assignee: Nick Boldt > Fix For: 4.1.0.Beta2 > > > https://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_4.1.keple... > org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent > {code} > org.eclipse.swt.SWTError: No more handles > at org.eclipse.swt.SWT.error(SWT.java:4418) > at org.eclipse.swt.SWT.error(SWT.java:4307) > at org.eclipse.swt.SWT.error(SWT.java:4278) > at org.eclipse.swt.browser.Browser.<init>(Browser.java:103) > at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:9) > at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:24) > at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:38) > at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:36) > at org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent(WebKitTests.java:39) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at junit.framework.TestCase.runTest(TestCase.java:176) > at junit.framework.TestCase.runBare(TestCase.java:141) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3692) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3341) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > {code} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14760) Cannot connect to OpenShift Enterprise with hostname: javax.net.ssl.SSLProtocolException (WATCHER)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14760?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-14760: ------------------------------------------------- openshift-github-bot <openshift-github-bot(a)redhat.com> made a comment on [bug 970805|https://bugzilla.redhat.com/show_bug.cgi?id=970805] Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/6dc5503401a78a337c11f71... <oo-diagnostics> Bug 970805 - Add check for broker SSL cert https://bugzilla.redhat.com/show_bug.cgi?id=970805 Add a test for verifying that the broker SSL cert is valid and that ServerName matches the certificate Common Name > Cannot connect to OpenShift Enterprise with hostname: javax.net.ssl.SSLProtocolException (WATCHER) > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-14760 > URL: https://issues.jboss.org/browse/JBIDE-14760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Beta2 > Environment: jdk7 > Reporter: jing zh > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta2 > > Attachments: JBT_test.png > > > If trying to connect openshift server ,it would be failed with following error shown. > Could not verify credentials for jinzhang1: Could not request https://broker.osetestv2.com/broker/rest/api: javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14833) bump parent pom version used in root pom to Beta2

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-14833: ---------------------------------- Summary: bump parent pom version used in root pom to Beta2 Key: JBIDE-14833 URL: https://issues.jboss.org/browse/JBIDE-14833 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Visual Page Editor core Affects Versions: 4.1.0.Beta2 Reporter: Nick Boldt Fix For: 4.1.0.Beta2 Need to use Beta2 parent pom in master branch in prep for Beta2 codefreeze. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-60) Modify devstudio site build to use jbosstools build as input

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-60?page=com.atlassian.jira.plugin.s... ] Paul Leacu commented on JBTIS-60: --------------------------------- This commit has the necesssary changes. Waiting for some kepler pieces before merging. ref JBTIS-79. https://github.com/pleacu/jbosstools-integration-stack/commit/d49c030cf02... > Modify devstudio site build to use jbosstools build as input > ------------------------------------------------------------ > > Key: JBTIS-60 > URL: https://issues.jboss.org/browse/JBTIS-60 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Rob Cernich > Assignee: Paul Leacu > > Ideally, the devstudio build should pull in dependencies from the JBT-IS target platform and an existing JBT-IS update site. This removes the need for maintaining two sets of composite*.xml files. It also ensures that a JBT-IS build exists prior to building JBDS-IS. > This can be accomplished by changing the URL of the repository being used to build devstudio from the local directory to a JBT-IS update site URL. -- 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, 10 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 June 2013