February 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-23997) JBoss data source file schema error

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-23997?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-23997. --------------------------------- > JBoss data source file schema error > ----------------------------------- > > Key: JBIDE-23997 > URL: https://issues.jboss.org/browse/JBIDE-23997 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jst > Affects Versions: 4.4.3.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.11.0.AM1 > > > An error message is shown, when new datasource file is added to a project: > {code:java} > Description Resource Path Location Type > cvc-elt.1: Cannot find the declaration of element 'datasources'. sa-ds.xml /testteast line 2 XML Problem > {code} > Datasource file: > {code:java} > <?xml version="1.0" encoding="UTF-8"?> > <datasources xmlns="http://www.jboss.org/ironjacamar/schema"> > <datasource jndi-name="java:jboss/datasources/sa" enabled="true" > use-java-context="true" pool-name="sa"> > <connection-url>jdbc:h2:tcp://localhost/sakila</connection-url> > <driver>h2-1.3.161.jar</driver> > <pool></pool> > <security> > <user-name>sa</user-name> > <password></password> > </security> > </datasource> > </datasources> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26502) Add support for WildFly 15

by Josef Kopriva (Jira)

[ https://issues.jboss.org/browse/JBIDE-26502?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26502. --------------------------------- Closing. WF15 support is added. Verified in: Red Hat CodeReady Studio Version: 12.11.0.AM1 Build id: AM1-v20190218-0530-B4081 Build date: 20190218-0530 > Add support for WildFly 15 > -------------------------- > > Key: JBIDE-26502 > URL: https://issues.jboss.org/browse/JBIDE-26502 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.11.0.AM1 > Reporter: Josef Kopriva > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.AM1 > > > WildFly 15 is out and available for download: http://wildfly.org/downloads/ > We should add support for it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4756) Cannot start devstudio on mac os with jdk 11

by Pavol Srna (Jira)

[ https://issues.jboss.org/browse/JBDS-4756?page=com.atlassian.jira.plugin.... ] Pavol Srna commented on JBDS-4756: ---------------------------------- I've tried manually on Mac OS 10.14.3 (Mojave) with Oracle JDK 11.0.2 without any problems. >From automation perspective this is still critical -- need to investigate if it is a jdk/slave configuration, or something else. > Cannot start devstudio on mac os with jdk 11 > -------------------------------------------- > > Key: JBDS-4756 > URL: https://issues.jboss.org/browse/JBDS-4756 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 12.11.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Critical > Fix For: 12.x > > Attachments: Screenshot_20190204_115602.png > > > I can easily install devstudio on mac os with default jdk 11 (from /qa/tools/opt/osx/jdk11_last) but I cannot make it start. No other errors or warnings except the one here: > !Screenshot_20190204_115602.png|thumbnail! > More info links [here|https://support.apple.com/kb/DL1572?locale=en_US]. > I can also see installer [tests|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...] failures on mac os 10.12 and 10.13 with this tack trace: > {code} > java.awt.HeadlessException > at java.desktop/sun.awt.HeadlessToolkit.getScreenSize(HeadlessToolkit.java:186) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:244) > at org.netbeans.jemmy.util.PNGEncoder.captureScreen(PNGEncoder.java:237) > at com.jboss.jbds.installer.test.InstallerTest.testInstall(InstallerTest.java:49) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) > at com.sun.proxy.$Proxy0.invoke(Unknown Source) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) > {code} > It might be possible to at least to try the installation and run on some bare metal to verify this error. Could someone possibly assist here, please? I have a suspicion that it might be performance related as the time needed to even open the jdk folder on the shared drive takes quite some time. Thanks! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26557) Update WildFly from version 11 to version 15 in maven.itests

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26557?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26557: ------------------------------------ Summary: Update WildFly from version 11 to version 15 in maven.itests (was: Update WildFly from version 11 to 15 in maven.itests) > Update WildFly from version 11 to version 15 in maven.itests > ------------------------------------------------------------ > > Key: JBIDE-26557 > URL: https://issues.jboss.org/browse/JBIDE-26557 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: maven > Affects Versions: 4.11.0.AM1 > Environment: All environments. > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > > WildFly needs to be updated from version 11 to version 15. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26558) Update WildFly from version 11 to version 15 in examples.itests

by Zbyněk Červinka (Jira)

Zbyněk Červinka created JBIDE-26558: --------------------------------------- Summary: Update WildFly from version 11 to version 15 in examples.itests Key: JBIDE-26558 URL: https://issues.jboss.org/browse/JBIDE-26558 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Affects Versions: 4.11.0.AM1 Environment: All environments Reporter: Zbyněk Červinka Assignee: Zbyněk Červinka Update WindFly from version 11 to version 15 in examples.itests -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26557) Update WildFly from version 11 to 15 in maven.itests

by Zbyněk Červinka (Jira)

[ https://issues.jboss.org/browse/JBIDE-26557?page=com.atlassian.jira.plugi... ] Zbyněk Červinka updated JBIDE-26557: ------------------------------------ Summary: Update WildFly from version 11 to 15 in maven.itests (was: Update WildFly from version 11 to 15) > Update WildFly from version 11 to 15 in maven.itests > ---------------------------------------------------- > > Key: JBIDE-26557 > URL: https://issues.jboss.org/browse/JBIDE-26557 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: maven > Affects Versions: 4.11.0.AM1 > Environment: All environments. > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > > WildFly needs to be updated from version 11 to version 15. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26557) Update WildFly from version 11 to 15

by Zbyněk Červinka (Jira)

Zbyněk Červinka created JBIDE-26557: --------------------------------------- Summary: Update WildFly from version 11 to 15 Key: JBIDE-26557 URL: https://issues.jboss.org/browse/JBIDE-26557 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: maven Affects Versions: 4.11.0.AM1 Environment: All environments. Reporter: Zbyněk Červinka Assignee: Zbyněk Červinka WildFly needs to be updated from version 11 to version 15. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26547) NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600

by Andre Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26547?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26547: ------------------------------------------ [~jeffmaury] With this breaking change we now require Eclipse 208-12. I dont see any such requirement in the PRs for https://issues.jboss.org/browse/JBIDE-26461. Shouldn't we make sure that one cannot install JBT 4.10 in Eclipse 208-09? > NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600 > ------------------------------------------------------------------------ > > Key: JBIDE-26547 > URL: https://issues.jboss.org/browse/JBIDE-26547 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.9.0.Final > Environment: Linux with Eclipse 20181214-0600 > Reporter: Thomas Zauner > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.AM1 > > > When refactoring variables/methods this fails silent and changes are reverted. This is caused by the following error: > Caused by: java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/corext/refactoring/tagging/IReferenceUpdating > at org.jboss.tools.common.model.refactoring.RenameProcessorRunner.updateReferences(RenameProcessorRunner.java:52) > at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.updateReferences(JSFRenameFieldParticipant.java:121) > at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.createChange(JSFRenameFieldParticipant.java:61) > at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:309) > at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:125) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:210) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322) > at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:89) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26547) NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600

by Andre Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26547?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-26547. ------------------------------------ Resolution: Done Re-closing. > NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600 > ------------------------------------------------------------------------ > > Key: JBIDE-26547 > URL: https://issues.jboss.org/browse/JBIDE-26547 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.9.0.Final > Environment: Linux with Eclipse 20181214-0600 > Reporter: Thomas Zauner > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.AM1 > > > When refactoring variables/methods this fails silent and changes are reverted. This is caused by the following error: > Caused by: java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/corext/refactoring/tagging/IReferenceUpdating > at org.jboss.tools.common.model.refactoring.RenameProcessorRunner.updateReferences(RenameProcessorRunner.java:52) > at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.updateReferences(JSFRenameFieldParticipant.java:121) > at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.createChange(JSFRenameFieldParticipant.java:61) > at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:309) > at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:125) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:210) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322) > at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:89) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-26547) NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600

by Andre Dietisheim (Jira)

[ https://issues.jboss.org/browse/JBIDE-26547?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26547: ------------------------------------------ My current guess in trying to understand this is that this was caused by JBIDE-26461 > NoClassDefFoundError in RenameProcessorRunner with Eclipse 20181214-0600 > ------------------------------------------------------------------------ > > Key: JBIDE-26547 > URL: https://issues.jboss.org/browse/JBIDE-26547 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.9.0.Final > Environment: Linux with Eclipse 20181214-0600 > Reporter: Thomas Zauner > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.11.0.AM1 > > > When refactoring variables/methods this fails silent and changes are reverted. This is caused by the following error: > Caused by: java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/corext/refactoring/tagging/IReferenceUpdating > at org.jboss.tools.common.model.refactoring.RenameProcessorRunner.updateReferences(RenameProcessorRunner.java:52) > at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.updateReferences(JSFRenameFieldParticipant.java:121) > at org.jboss.tools.jsf.model.handlers.bean.JSFRenameFieldParticipant.createChange(JSFRenameFieldParticipant.java:61) > at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:309) > at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:125) > at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:210) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2295) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2322) > at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:89) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 February 2019