April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23433) SSL Cerrtificate: create unit-tests

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23433?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23433: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > SSL Cerrtificate: create unit-tests > ----------------------------------- > > Key: JBIDE-23433 > URL: https://issues.jboss.org/browse/JBIDE-23433 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.6.x > > > We should create unit-tests for the partial fix provided in JBIDE-23208 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24555) Test Failure(s) in JBIDE 4.5.0.AM1 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24555?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24555: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Test Failure(s) in JBIDE 4.5.0.AM1 for jst component - org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24555 > URL: https://issues.jboss.org/browse/JBIDE-24555 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jst > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Jeff MAURY > Priority: Blocker > Labels: testfailure > Fix For: 4.6.x > > > *2 Test Failure(s) in JBIDE 4.5.0.AM2 for jst component:* > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > [Search for Test Failure JIRAs in JBIDE 4.5.0.AM1 for jst component|https://issues.jboss.org/issues/?jql=labels%20IN%20(%22testfail...] > ----- > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML 0.22 sec 194 > org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML 1.1 sec 194 > {code} > {code} > Failed > org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests) > Failing for the past 194 builds (Since #1 ) > Took 0.22 sec. > Error Message > Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15) > Stacktrace > junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 302 (line - 16 position - 15) > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.TestCase.fail(TestCase.java:227) > at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkHyperlinksInTextEditor(HyperlinkTestUtil.java:203) > at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinks(DatalistHyperlinkDetectorTest.java:64) > at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testHyperlinksHTML(DatalistHyperlinkDetectorTest.java:57){code} > {code} > Failed > org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML (from org.jboss.tools.jst.web.ui.openon.test.JstTextExtAllTests) > Failing for the past 194 builds (Since #1 ) > Took 1.1 sec. > Error Message > Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14) > Stacktrace > junit.framework.AssertionFailedError: Wrong detection for region - <browsers> 301 - 309 line - 16 position - 14 offset - 301 (line - 16 position - 14) > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.TestCase.fail(TestCase.java:227) > at org.jboss.tools.jst.jsp.test.openon.HyperlinkTestUtil.checkRegionsInTextEditor(HyperlinkTestUtil.java:546) > at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.checkHyperlinkDetector(DatalistHyperlinkDetectorTest.java:53) > at org.jboss.tools.jst.web.ui.openon.test.DatalistHyperlinkDetectorTest.testDetectorHTML(DatalistHyperlinkDetectorTest.java:47){code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24794) Hibernate Reverse Engineering doesn't work on 4.5.0.AM2

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24794?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24794: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Hibernate Reverse Engineering doesn't work on 4.5.0.AM2 > ------------------------------------------------------- > > Key: JBIDE-24794 > URL: https://issues.jboss.org/browse/JBIDE-24794 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Dmitrii Bocharov > Assignee: Koen Aers > Fix For: 4.6.x > > Attachments: 4.4.4.Final-works.webm, 4.5.0.AM2-doesnt-work.webm > > > Reverse Engineering doesn't work at the moment, but it worked in 4.4.4.Final. See the attahced screencasts for details. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18925) Choose a default target server runtime as the latest available

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18925?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18925: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Choose a default target server runtime as the latest available > -------------------------------------------------------------- > > Key: JBIDE-18925 > URL: https://issues.jboss.org/browse/JBIDE-18925 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, project-examples > Reporter: Marek Novotny > Fix For: 4.6.x > > > This suggestion for enhancement distilled from JBDS-3240 comments. > The creating of new project from Maven archetype (Start from Scratch in JBoss Central) is the starting point. > Could a runtime in the Target runtime field be set by default (the latest is the best) from available runtimes ? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21127) Can't add "Table&Columns" while using hibernate plug in Eclipse

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21127?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-21127: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Can't add "Table&Columns" while using hibernate plug in Eclipse > --------------------------------------------------------------- > > Key: JBIDE-21127 > URL: https://issues.jboss.org/browse/JBIDE-21127 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Environment: eclipse.buildId=4.4.0.I20140606-1215 > java.version=1.8.0_25 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product > Reporter: hu tang > Assignee: Koen Aers > Priority: Minor > Fix For: 4.6.x > > > I used hibernate plug(JBoss Tool) in "eclipse-jee-luna-R-win32-x86_64", when I tried to add "Table&Columns" in "Hibernate Reverse Engineering Editor". It threw out an exception "Unhandled event loop exception", the details as below: I tried to reinstall both eclipse and hibernate plug but not work. > java.lang.NullPointerException > at org.hibernate.eclipse.mapper.editors.reveng.TablePropertiesBlock.doAdd(TablePropertiesBlock.java:209) > at org.hibernate.eclipse.mapper.editors.reveng.TablePropertiesBlock$1.widgetSelected(TablePropertiesBlock.java:127) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18654) run jdeps on our jars to see how dependent we are on api that might go away in Java 9

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18654?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-18654: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > run jdeps on our jars to see how dependent we are on api that might go away in Java 9 > ------------------------------------------------------------------------------------- > > Key: JBIDE-18654 > URL: https://issues.jboss.org/browse/JBIDE-18654 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Jeff MAURY > Fix For: 4.6.x > > > Java 9 JDK team have been pinging various teams to check if they got depedency on API that is scheduled to disappear in Java 9. > There is a tool called jdeps that we can use to check for this using the -jdkinternals flag. > https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool > The sooner the better we get this done as it is feedback to the Java 9 team. > If we can we should try run it on *all* jars, even eclipse ones to see what will be affected - but first of all jboss tools plugins. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16638) Improve UI of Deployment Scanner settings

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16638?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-16638: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Improve UI of Deployment Scanner settings > ----------------------------------------- > > Key: JBIDE-16638 > URL: https://issues.jboss.org/browse/JBIDE-16638 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Alpha2 > Environment: JBDS 8.0.0.Alpha2b B71 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.6.x > > Attachments: scanner-options-mockup.png, scanner-options.png > > > Looking at the new options introduced in JBIDE-15287, I don't quite like to look of it. > Let me know if you disagree, but using "(default)" in a field that's supposed to take numbers is not very nice. > !scanner-options.png! > Instead, I propose adding a checkbox in front of the options: > !scanner-options-mockup.png! > Excuse the ugly picture, but the idea is that if the checkbox is not checked, the field is greyed out (and empty). If it is checked, a value is expected. WDYT? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15673) Better contextual menu for JAXRS

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15673?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-15673: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Better contextual menu for JAXRS > -------------------------------- > > Key: JBIDE-15673 > URL: https://issues.jboss.org/browse/JBIDE-15673 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Affects Versions: 4.1.0.1.Final > Reporter: ehsavoie Hugonnet > Assignee: Xavier Coulon > Priority: Minor > Labels: jax-rs > Fix For: 4.6.x > > Attachments: jbosstools_jaxrs.png > > > When right clicking on the "JAX-RS Web Services" resources view I expect a create new RestFull Web Service entry in the menu. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15023) Remove references to struts from jsf/common

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15023?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-15023: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Remove references to struts from jsf/common > ------------------------------------------- > > Key: JBIDE-15023 > URL: https://issues.jboss.org/browse/JBIDE-15023 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common, jsf, struts/shale > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25258) Integration Tests: Server adapter wizard and editor dont allow invalid devmode-/debug-port-key nor debug port value

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25258?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25258: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Integration Tests: Server adapter wizard and editor dont allow invalid devmode-/debug-port-key nor debug port value > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25258 > URL: https://issues.jboss.org/browse/JBIDE-25258 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.1.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_editor, server_adapter_wizard > Fix For: 4.6.x > > Attachments: server-adapter-wizard.png, server-adater-editor.png > > > In JBIDE-25108 the server adapter wizard and -editor were changed so that they would only allow valid values for > * devmode key > * debug port key > * debug port value > The editor should not allow saving if there are invalid values, the wizard would not allow one to finish it. > !server-adater-editor.png|thumbnail! > !server-adapter-wizard.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018