September 2019 - jbosstools-issues

[JBoss JIRA] (JBIDE-26400) Maven New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26400?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26400: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Maven New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26400 > URL: https://issues.jboss.org/browse/JBIDE-26400 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.13.0.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Maven JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Maven, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Maven by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26391 #comment Create N&N for Maven 4.10.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Maven for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26397) Usage Analytics New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26397?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26397: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Usage Analytics New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26397 > URL: https://issues.jboss.org/browse/JBIDE-26397 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: usage > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.13.0.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Usage Analytics JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Usage Analytics, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Usage Analytics by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26391 #comment Create N&N for Usage Analytics 4.10.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Usage Analytics for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26394) Webservices / Rest New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26394?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26394: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Webservices / Rest New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26394 > URL: https://issues.jboss.org/browse/JBIDE-26394 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.13.0.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Webservices / Rest JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Webservices / Rest, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Webservices / Rest by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26391 #comment Create N&N for Webservices / Rest 4.10.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Webservices / Rest for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26395) Hibernate New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26395?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26395: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Hibernate New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26395 > URL: https://issues.jboss.org/browse/JBIDE-26395 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Koen Aers > Priority: Critical > Labels: task > Fix For: 4.13.0.Final > > > Koen Aers, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Hibernate JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Hibernate, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Hibernate by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26391 #comment Create N&N for Hibernate 4.10.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Hibernate for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26393) CDI New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26393?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26393: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > CDI New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26393 > URL: https://issues.jboss.org/browse/JBIDE-26393 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.13.0.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed CDI JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for CDI, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for CDI by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26391 #comment Create N&N for CDI 4.10.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for CDI for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26391) Create New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26391?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26391: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Create New and Noteworthy for 4.10.0.AM1 > ---------------------------------------- > > Key: JBIDE-26391 > URL: https://issues.jboss.org/browse/JBIDE-26391 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.13.0.Final > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26392) Central New and Noteworthy for 4.10.0.AM1

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26392?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26392: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Central New and Noteworthy for 4.10.0.AM1 > ---------------------------------------------------- > > Key: JBIDE-26392 > URL: https://issues.jboss.org/browse/JBIDE-26392 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.13.0.Final > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Central JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Central, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Central by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26391 #comment Create N&N for Central 4.10.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Central for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24963) Create CDI 2 integration tests

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-24963?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24963: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Create CDI 2 integration tests > ------------------------------ > > Key: JBIDE-24963 > URL: https://issues.jboss.org/browse/JBIDE-24963 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi, integration-tests > Affects Versions: 4.5.1.AM2 > Reporter: Lukáš Valach > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.13.0.Final > > > The support for CDI 2.0 has been added recently, see JBIDE-24949. > Spec: > http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html > Change log: > https://issues.jboss.org/secure/ReleaseNote.jspa?version=12325406&styleNa... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26543) Reorganize plugins and test plugins in a more coherent module hierarchy

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26543?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26543: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Reorganize plugins and test plugins in a more coherent module hierarchy > ----------------------------------------------------------------------- > > Key: JBIDE-26543 > URL: https://issues.jboss.org/browse/JBIDE-26543 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.10.0.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Major > Fix For: 4.13.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26541) Mylyn: refresh builds does not work under JDK11

by Jeff MAURY (Jira)

[ https://issues.jboss.org/browse/JBIDE-26541?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-26541: ------------------------------- Fix Version/s: 4.13.0.Final (was: 4.13.0.AM1) > Mylyn: refresh builds does not work under JDK11 > ----------------------------------------------- > > Key: JBIDE-26541 > URL: https://issues.jboss.org/browse/JBIDE-26541 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.11.0.AM1 > Environment: F29 + JDK11 > Reporter: Josef Kopriva > Priority: Major > Fix For: 4.13.0.Final > > > Message from error log: > {code:java} > eclipse.buildId=12.11.0.AM1-v20190128-0120-B3931 > java.version=11.0.1 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/jkopriva/git/workspace-spring/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.eclipse.mylyn.commons.repositories.ui > Error > Fri Feb 01 14:33:04 CET 2019 > Unexpected error during repository validation. > java.lang.reflect.InvocationTargetException > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:401) > at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:977) > at org.eclipse.mylyn.commons.ui.dialogs.EnhancedWizardDialog.run(EnhancedWizardDialog.java:138) > at org.eclipse.mylyn.commons.repositories.ui.RepositoryWizardPage.run(RepositoryWizardPage.java:98) > at org.eclipse.mylyn.commons.repositories.ui.RepositoryLocationPart.validate(RepositoryLocationPart.java:554) > at org.eclipse.mylyn.builds.ui.spi.BuildServerPart$1.widgetSelected(BuildServerPart.java:180) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:252) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5663) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1386) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4931) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4472) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:822) > at org.eclipse.jface.window.Window.open(Window.java:798) > at org.eclipse.mylyn.commons.repositories.ui.RepositoryUi.openNewRepositoryDialog(RepositoryUi.java:90) > at org.eclipse.mylyn.internal.builds.ui.view.NewBuildServerAction.run(NewBuildServerAction.java:35) > at org.eclipse.mylyn.internal.builds.ui.view.BuildsView$2.widgetSelected(BuildsView.java:326) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:252) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5663) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1386) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412) > at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1526) > at org.eclipse.swt.widgets.Link.gtk_button_release_event(Link.java:387) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1946) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:6298) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5880) > at org.eclipse.swt.internal.gtk.GTK._gtk_main_do_event(Native Method) > at org.eclipse.swt.internal.gtk.GTK.gtk_main_do_event(GTK.java:3969) > at org.eclipse.swt.widgets.Display.eventProc(Display.java:1385) > at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) > at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:1581) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4470) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) > 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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595) > at org.eclipse.equinox.launcher.Main.run(Main.java:1501) > at org.eclipse.equinox.launcher.Main.main(Main.java:1474) > Caused by: java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException > at org.eclipse.mylyn.internal.hudson.core.client.RestfulHudsonClient.validate(RestfulHudsonClient.java:463) > at org.eclipse.mylyn.internal.hudson.core.HudsonServerBehaviour.validate(HudsonServerBehaviour.java:956) > at org.eclipse.mylyn.builds.internal.core.BuildServer.validate(BuildServer.java:369) > at org.eclipse.mylyn.builds.ui.spi.BuildServerPart$Validator.run(BuildServerPart.java:114) > at org.eclipse.mylyn.commons.repositories.ui.RepositoryLocationPart$2.run(RepositoryLocationPart.java:558) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.eclipse.mylyn.hudson.core_1.16.0.v20180403-2055 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:511) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:422) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:414) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:153) > at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) > ... 6 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2019