[JBoss JIRA] (JBIDE-22038) Errors on startup with Java 9
by Jan Richter (JIRA)
Jan Richter created JBIDE-22038:
-----------------------------------
Summary: Errors on startup with Java 9
Key: JBIDE-22038
URL: https://issues.jboss.org/browse/JBIDE-22038
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 4.3.1.CR1
Reporter: Jan Richter
Starting fresh JBT/JBDS with Java 9 results in an error dialog popping up with these two errors:
{noformat}An internal error occurred during: "Update project wizard list".
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
at org.jboss.tools.project.examples.internal.FavoriteExampleManager.<init>(FavoriteExampleManager.java:38)
at org.jboss.tools.project.examples.internal.FavoriteExampleManager.<init>(FavoriteExampleManager.java:31)
at org.jboss.tools.project.examples.internal.ProjectExamplesActivator.getFavoriteExampleManager(ProjectExamplesActivator.java:1064)
at org.jboss.tools.central.editors.GettingStartedHtmlPage$5$2.collectFavorites(GettingStartedHtmlPage.java:282)
at org.jboss.tools.central.editors.GettingStartedHtmlPage$5$2.run(GettingStartedHtmlPage.java:273)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.1.CR1-v20160324-1911-B99
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
... 6 more{noformat}
{noformat}An internal error occurred during: "Download quickstarts list".
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
at org.jboss.tools.project.examples.model.ProjectExampleUtil.fetchCategories(ProjectExampleUtil.java:396)
at org.jboss.tools.project.examples.model.ProjectExampleUtil.getCategories(ProjectExampleUtil.java:273)
at org.jboss.tools.project.examples.model.ProjectExampleUtil.getCategories(ProjectExampleUtil.java:263)
at org.jboss.tools.project.examples.internal.ProjectExampleXmlProvider.getExamples(ProjectExampleXmlProvider.java:28)
at org.jboss.tools.project.examples.internal.ProjectExampleManager.getExamples(ProjectExampleManager.java:60)
at org.jboss.tools.central.editors.GettingStartedHtmlPage$RefreshQuickstartsJob.run(GettingStartedHtmlPage.java:102)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.1.CR1-v20160324-1911-B99
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
... 7 more{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Thomas Mäder (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Thomas Mäder commented on JBIDE-21857:
--------------------------------------
Double checked on IBM JDK 8 and the issue exists there, too, but becuase it allows for more types of changes, it's more rare.
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22025) For JBIDE 4.3.1.CR1: Prepare for Final/GA [Webservices]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22025?page=com.atlassian.jira.plugi... ]
Xavier Coulon closed JBIDE-22025.
---------------------------------
Resolution: Done
parent version in pom.xml was upgraded and build was verified on minimum and maximum TP versions.
> For JBIDE 4.3.1.CR1: Prepare for Final/GA [Webservices]
> -------------------------------------------------------
>
> Key: JBIDE-22025
> URL: https://issues.jboss.org/browse/JBIDE-22025
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.CR1
>
>
> For JBIDE 4.3.1.CR1 [Webservices]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.CR1 or Final
> [Unresolved JIRAs with fixVersion = 4.3.1.CR1, 4.3.1.Final, 9.1.0.CR1, 9.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. Check out your existing *{color:blue}jbosstools-4.3.x{color}* branch:
> {code}
> git checkout jbosstools-4.3.x
> {code}
> 2. Update your *{color:blue}jbosstools-4.3.x branch{color}* root pom to use the latest parent pom version, *{color:blue}4.3.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch
> 3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Final-SNAPSHOT (4.50 = Eclipse Mars.0)
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Final-SNAPSHOT
> {code}
> 3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Final-SNAPSHOT (4.52 = Eclipse Mars.2)
> {code}
> mvn clean verify -Dtpc.version=4.52.0.Final-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3742) Cygwin setup exdecutable should be installed as well
by Hardy Ferentschik (JIRA)
Hardy Ferentschik created JBDS-3742:
---------------------------------------
Summary: Cygwin setup exdecutable should be installed as well
Key: JBDS-3742
URL: https://issues.jboss.org/browse/JBDS-3742
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Components: installer
Reporter: Hardy Ferentschik
Priority: Minor
As part of the installer Cygwin gets installed. However, the setup executable and package manager of Cygwin does not seem to get copied as well. Without it the user won't be able to extend/change the Cygwin configuration.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3741) Developer Studio should install under developer-studio instead of DeveloperStudio
by Hardy Ferentschik (JIRA)
Hardy Ferentschik created JBDS-3741:
---------------------------------------
Summary: Developer Studio should install under developer-studio instead of DeveloperStudio
Key: JBDS-3741
URL: https://issues.jboss.org/browse/JBDS-3741
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Components: installer
Reporter: Hardy Ferentschik
Priority: Trivial
Attachments: directories.png
Currently Developer studio is installed under the folder {{DeveloperStudio}} within the installation directory. All other programs use lower case directory names for their install directory (eg vagrant, cygwun, jdk8, etc). For consistency it should be developerstudio or developer-studio. See screenshot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21474) Hibernate libraries are not being validated
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21474?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-21474.
------------------------------------
verified in JBDS 9.1.0.CR1-v20160326-0059-B443
> Hibernate libraries are not being validated
> -------------------------------------------
>
> Key: JBIDE-21474
> URL: https://issues.jboss.org/browse/JBIDE-21474
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.1.Beta1
> Reporter: Rastislav Wagner
> Assignee: Koen Aers
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> enablement of HibernateUserLibraryValidator is not correctly defined in o.j.t.hibernate.jpt.core plugin.xml which causes this exception
> {code}
> org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.jpt.jpa.core.jpaPlatformGroup to type class org.eclipse.jpt.jpa.core.internal.libprov.JpaUserLibraryProviderInstallOperationConfig
> at org.eclipse.core.internal.expressions.TypeExtensionManager.getProperty(TypeExtensionManager.java:127)
> at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:97)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:75)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:31)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:55)
> at org.eclipse.jpt.common.core.internal.libval.LibraryValidatorConfig.isEnabled_(LibraryValidatorConfig.java:86)
> at org.eclipse.jpt.common.core.internal.libval.LibraryValidatorConfig.isEnabled(LibraryValidatorConfig.java:72)
> at org.eclipse.jpt.common.core.internal.libval.LibraryValidatorConfig$IsEnabled.evaluate(LibraryValidatorConfig.java:121)
> at org.eclipse.jpt.common.core.internal.libval.LibraryValidatorConfig$IsEnabled.evaluate(LibraryValidatorConfig.java:1)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.loadNext(FilteringIterator.java:80)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.next(FilteringIterator.java:68)
> at org.eclipse.jpt.common.utility.internal.iterator.TransformationIterator.next(TransformationIterator.java:54)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.loadNext(FilteringIterator.java:79)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.<init>(FilteringIterator.java:56)
> at org.eclipse.jpt.common.utility.internal.iterator.IteratorTools.filter(IteratorTools.java:886)
> at org.eclipse.jpt.common.utility.internal.iterable.FilteringIterable.iterator(FilteringIterable.java:48)
> at org.eclipse.jpt.common.core.internal.libprov.JptUserLibraryProviderInstallOperationConfig.validate(JptUserLibraryProviderInstallOperationConfig.java:42)
> at org.eclipse.jst.common.project.facet.core.libprov.LibraryInstallDelegate.validate(LibraryInstallDelegate.java:528)
> at org.eclipse.jst.common.project.facet.ui.libprov.LibraryFacetPropertyPage.performValidation(LibraryFacetPropertyPage.java:385)
> at org.eclipse.jpt.common.ui.internal.properties.JptProjectPropertiesPage.performValidation(JptProjectPropertiesPage.java:448)
> at org.eclipse.jst.common.project.facet.ui.libprov.LibraryFacetPropertyPage.updateValidation(LibraryFacetPropertyPage.java:346)
> at org.eclipse.jpt.common.ui.internal.properties.JptProjectPropertiesPage.validate(JptProjectPropertiesPage.java:396)
> at org.eclipse.jpt.common.ui.internal.properties.JptProjectPropertiesPage$ValidationListener.modelChanged(JptProjectPropertiesPage.java:390)
> at org.eclipse.jpt.common.utility.model.listener.AbstractChangeListener.modelChanged(AbstractChangeListener.java:101)
> at org.eclipse.jpt.common.utility.model.listener.AbstractChangeListener.propertyChanged(AbstractChangeListener.java:53)
> at org.eclipse.jpt.common.utility.internal.model.ChangeSupport.firePropertyChanged_(ChangeSupport.java:526)
> at org.eclipse.jpt.common.utility.internal.model.ChangeSupport.firePropertyChanged(ChangeSupport.java:491)
> at org.eclipse.jpt.common.utility.internal.model.SingleAspectChangeSupport.firePropertyChanged(SingleAspectChangeSupport.java:156)
> at org.eclipse.jpt.common.utility.internal.model.AbstractModel.firePropertyChanged(AbstractModel.java:189)
> at org.eclipse.jpt.common.utility.internal.model.value.BufferedModifiablePropertyValueModel.reset(BufferedModifiablePropertyValueModel.java:271)
> at org.eclipse.jpt.common.utility.internal.model.value.BufferedModifiablePropertyValueModel.setValue(BufferedModifiablePropertyValueModel.java:139)
> at org.eclipse.jpt.common.ui.internal.swt.bindings.BooleanButtonModelBinding.buttonSelected(BooleanButtonModelBinding.java:173)
> at org.eclipse.jpt.common.ui.internal.swt.bindings.BooleanButtonModelBinding$ButtonSelectionListener.widgetSelected(BooleanButtonModelBinding.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:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:157)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months