August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25206) Integration Tests: TriggerBuildTest

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25206?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25206: ---------------------------------- Sprint: devex #154 September 2018 > Integration Tests: TriggerBuildTest > ----------------------------------- > > Key: JBIDE-25206 > URL: https://issues.jboss.org/browse/JBIDE-25206 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: integration_tests > Fix For: 4.9.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26298) OpenShift ITests: Fix Docker ITests for oc cluster up

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26298?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26298: ---------------------------------- Fix Version/s: 4.9.0.AM3 > OpenShift ITests: Fix Docker ITests for oc cluster up > ----------------------------------------------------- > > Key: JBIDE-26298 > URL: https://issues.jboss.org/browse/JBIDE-26298 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, openshift > Affects Versions: 4.9.0.AM2 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.9.0.AM3 > > > openShift ITests for docker are not working for oc cluster up. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4652) JDK9 Certification - javascript

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4652?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4652: ----------------------------- Fix Version/s: 12.9.0.AM3 (was: 12.9.0.AM1) > JDK9 Certification - javascript > ------------------------------- > > Key: JBDS-4652 > URL: https://issues.jboss.org/browse/JBDS-4652 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: javascript > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 12.9.0.AM3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4642) JDK9 Certification - *running* Devstudio with jdk9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4642?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4642: ----------------------------- Fix Version/s: 12.9.0.AM3 (was: 12.9.0.AM1) > JDK9 Certification - *running* Devstudio with jdk9 > -------------------------------------------------- > > Key: JBDS-4642 > URL: https://issues.jboss.org/browse/JBDS-4642 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: build > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 12.9.0.AM3 > > > This is an epic for tracking JDK9 Devstudio Certification. > All components need to be retested (run) with JDK9. > Please link issues found here. > Please do only resolve the subtasks, when the component *is* certified running with jdk9. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4711) Add support for LFS via egit to Devstudio/JBoss Tools? (was ClassNotFoundException in Error Log after start: Builtin LFS support not present/detected)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4711?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4711: ----------------------------- Fix Version/s: 12.9.0.AM3 (was: 12.9.0.AM1) > Add support for LFS via egit to Devstudio/JBoss Tools? (was ClassNotFoundException in Error Log after start: Builtin LFS support not present/detected) > ------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-4711 > URL: https://issues.jboss.org/browse/JBDS-4711 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, upstream > Affects Versions: 12.0.0.GA > Environment: F28 + 12.0.0.GA-v20180625-0632-B2859 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Minor > Fix For: 12.9.0.AM3 > > > After every start of devstudio, there is a warning: > {code:java} > eclipse.buildId=12.0.0.GA-v20180625-0632-B2859 > java.version=1.8.0_172 > 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/devstudio_B2859_2/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.eclipse.egit.core > Warning > Mon Jun 25 13:18:32 CEST 2018 > Builtin LFS support not present/detected > java.lang.ClassNotFoundException: org.eclipse.jgit.lfs.BuiltinLFS cannot be found by org.eclipse.egit.core_5.0.0.201806131550-r > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:508) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:419) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:411) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:264) > at org.eclipse.egit.core.Activator.registerBuiltinLFS(Activator.java:279) > at org.eclipse.egit.core.Activator.start(Activator.java:212) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:779) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:772) > at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:729) > at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1002) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:354) > at org.eclipse.osgi.container.Module.doStart(Module.java:581) > at org.eclipse.osgi.container.Module.start(Module.java:449) > at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:468) > at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:114) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:505) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328) > at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:392) > at org.eclipse.osgi.internal.loader.sources.SingleSourcePackage.loadClass(SingleSourcePackage.java:36) > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:454) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:419) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:411) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.egit.ui.Activator$RepositoryChangeScanner.<init>(Activator.java:921) > at org.eclipse.egit.ui.Activator.setupRepoChangeScanner(Activator.java:1034) > at org.eclipse.egit.ui.Activator.start(Activator.java:336) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:779) > at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:772) > at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:729) > at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1002) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:354) > at org.eclipse.osgi.container.Module.doStart(Module.java:581) > at org.eclipse.osgi.container.Module.start(Module.java:449) > at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:468) > at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:114) > at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:505) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328) > at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:392) > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:470) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:419) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:411) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:609) > at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:177) > at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:931) > at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) > at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:60) > at org.eclipse.ui.internal.services.WorkbenchServiceRegistry.getSourceProviders(WorkbenchServiceRegistry.java:174) > at org.eclipse.ui.internal.services.SourceProviderService.readRegistry(SourceProviderService.java:104) > at org.eclipse.ui.internal.Workbench$34.runWithException(Workbench.java:2378) > at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:32) > at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233) > at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144) > at org.eclipse.swt.widgets.Display.syncExec(Display.java:5831) > at org.eclipse.ui.internal.StartupThreading.runWithoutExceptions(StartupThreading.java:95) > at org.eclipse.ui.internal.Workbench.initializeDefaultServices(Workbench.java:2373) > at org.eclipse.ui.internal.Workbench.init(Workbench.java:1654) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2859) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:597) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:656) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:592) > at org.eclipse.equinox.launcher.Main.run(Main.java:1498) > at org.eclipse.equinox.launcher.Main.main(Main.java:1471) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26238) CDI New and Noteworthy for 4.9.0.AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26238?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26238: ------------------------------- Fix Version/s: 4.9.0.AM3 (was: 4.9.0.AM2) > CDI New and Noteworthy for 4.9.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26238 > URL: https://issues.jboss.org/browse/JBIDE-26238 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.9.0.AM3 > > > 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-26236 #comment Create N&N for CDI 4.9.0.AM2 #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.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26237) Central New and Noteworthy for 4.9.0.AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26237?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26237: ------------------------------- Fix Version/s: 4.9.0.AM3 (was: 4.9.0.AM2) > Central New and Noteworthy for 4.9.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26237 > URL: https://issues.jboss.org/browse/JBIDE-26237 > 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.9.0.AM3 > > > 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-26236 #comment Create N&N for Central 4.9.0.AM2 #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.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26236) Create New and Noteworthy for 4.9.0.AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26236?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26236: ------------------------------- Fix Version/s: 4.9.0.AM3 (was: 4.9.0.AM2) > Create New and Noteworthy for 4.9.0.AM2 > --------------------------------------- > > Key: JBIDE-26236 > URL: https://issues.jboss.org/browse/JBIDE-26236 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.9.0.AM3 > > > 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.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26247) Server New and Noteworthy for 4.9.0.AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26247?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26247: ------------------------------- Fix Version/s: 4.9.0.AM3 (was: 4.9.0.AM2) > Server New and Noteworthy for 4.9.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26247 > URL: https://issues.jboss.org/browse/JBIDE-26247 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Labels: task > Fix For: 4.9.0.AM3 > > > Rob Stryker, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Server 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 Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Server 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-26236 #comment Create N&N for Server 4.9.0.AM2 #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 Server for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26246) Batch New and Noteworthy for 4.9.0.AM2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26246?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26246: ------------------------------- Fix Version/s: 4.9.0.AM3 (was: 4.9.0.AM2) > Batch New and Noteworthy for 4.9.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26246 > URL: https://issues.jboss.org/browse/JBIDE-26246 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: task > Fix For: 4.9.0.AM3 > > > Jeff MAURY, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Batch 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 Batch, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Batch 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-26236 #comment Create N&N for Batch 4.9.0.AM2 #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 Batch for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 7 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 August 2018