[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ]
Pavol Srna edited comment on JBIDE-24897 at 2/13/18 9:28 AM:
-------------------------------------------------------------
[~nickboldt] reopening since the feature says "supported" instead of "technology preview"
!Screenshot 2018-02-13 15.22.41.png!
was (Author: psrna):
[~nickboldt] reopening since the feature says "supported" instead of "technology preview"
> add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24897
> URL: https://issues.jboss.org/browse/JBIDE-24897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: fabric8
> Affects Versions: 4.5.2.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM1
>
> Attachments: IE-screenshot.png, Screenshot (2).png, Screenshot 2018-02-13 15.22.41.png, Screenshot 2018-02-13 15.25.37.png, fab8anal-in-ds-central.png, fab8anal-in-jbt-central-installed.png, fab8anal-in-jbt-central.png, fabric8-connector.png, screenshot-1.png, screenshot-2.png, stack analysis.mp4, stack report 20180119.png
>
>
> Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra]
> Assuming we also want to create a Central connector to advertise this optional feature.
> In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala]
> Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin
> Affected:
> * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml)
> * https://github.com/jbosstools/jbosstools-build-sites (category.xml)
> * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-24897) add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24897?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-24897:
-------------------------------
Attachment: Screenshot 2018-02-13 15.25.37.png
Screenshot 2018-02-13 15.22.41.png
> add fabric8 analytics feature to jbosstools and devstudio (optional feature, new Central connector)
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24897
> URL: https://issues.jboss.org/browse/JBIDE-24897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: fabric8
> Affects Versions: 4.5.2.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.3.AM1
>
> Attachments: IE-screenshot.png, Screenshot (2).png, Screenshot 2018-02-13 15.22.41.png, Screenshot 2018-02-13 15.25.37.png, fab8anal-in-ds-central.png, fab8anal-in-jbt-central-installed.png, fab8anal-in-jbt-central.png, fabric8-connector.png, screenshot-1.png, screenshot-2.png, stack analysis.mp4, stack report 20180119.png
>
>
> Once authentication (to access Fabric8 Analytics API) is fixed we can add this to JBoss Tools and devstudio. cc: [~gbatra]
> Assuming we also want to create a Central connector to advertise this optional feature.
> In future we could also consider adding a Marketplace connector (separate from JBT/devstudio), if that's desired. cc: [~maxandersen] [~adisakala]
> Sources: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin
> Affected:
> * https://github.com/jbdevstudio/jbdevstudio-product (category.xml, feature.xml)
> * https://github.com/jbosstools/jbosstools-build-sites (category.xml)
> * https://github.com/jbosstools/jbosstools-discovery (plugin.xml x 2, plus new icon if applicable?)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-25378) Add cdk itests for multiple server adapters using minishift profile feature
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25378?page=com.atlassian.jira.plugi... ]
Ondrej Dockal edited comment on JBIDE-25378 at 2/13/18 8:06 AM:
----------------------------------------------------------------
Verification steps:
Use case 1: CDK 3.2+ Server Adapter can be operated (covered by o.j.t.cdk.ui.bot.test.server.adapter.CDK32IntegrationTest)
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift)
3. EXEC: Start/Stop/Restart server adapter
4. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped)
Use case 2: CDK 3.2+ Server Adapter can operate another profile
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with profile set to value different than "minishift"
3. EXEC: Start/Stop/Restart server adapter
4. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
5. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped)
Use case 3: CDK 3.2+ Server adapter can operate two profile simultaneously
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift)
3. EXEC: Create New CDK 3.2+ server with profile set to value different than "minishift"
4. EXEC: Start default server adapter with default profile
5. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
6. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped)
7. EXEC: Start server adapter with named profile set
8. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
9. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped)
10. EXEC: Stop named profile
11. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli), SA state is stopped
12. EXEC: Stop default profile
13. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli), SA state is stopped
was (Author: odockal):
Verification steps:
Use case 1: CDK 3.2+ Server Adapter can be operated (covered by o.j.t.cdk.ui.bot.test.CDK32IntegrationTest)
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift)
3. EXEC: Start/Stop/Restart server adapter
4. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped)
Use case 2: CDK 3.2+ Server Adapter can operate another profile
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with profile set to value different than "minishift"
3. EXEC: Start/Stop/Restart server adapter
4. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
5. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped)
Use case 3: CDK 3.2+ Server adapter can operate two profile simultaneously
1. EXEC: There is no old CDK configuration, have CDK with profiles feature downloaded, 'setup-cdk' called - happens out of IDE
2. EXEC: Create New CDK 3.2+ server with default values (profile = minishift)
3. EXEC: Create New CDK 3.2+ server with profile set to value different than "minishift"
4. EXEC: Start default server adapter with default profile
5. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
6. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped)
7. EXEC: Start server adapter with named profile set
8. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli)
9. ASSERT: Check that OS 3 connection was created (SSL Cert. was accepted), Docker connection was created, SA state is started (stopped)
10. EXEC: Stop named profile
11. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli), SA state is stopped
12. EXEC: Stop default profile
13. ASSERT: Proper profile was started/stopped (check via --profile ProfileName on cli), SA state is stopped
> Add cdk itests for multiple server adapters using minishift profile feature
> ---------------------------------------------------------------------------
>
> Key: JBIDE-25378
> URL: https://issues.jboss.org/browse/JBIDE-25378
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: integration-tests
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Labels: cdk, cdk_server_adapter
> Fix For: 4.5.3.AM1
>
>
> Implement base scenarios for CDK 3.2+ server adapter's profile feature that would include work with two server adapters. https://docs.openshift.org/latest/minishift/using/profiles.html
> Test cases can be derived from https://issues.jboss.org/browse/JBIDE-25055. This jira will cover 2nd and 3rd use case.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (JBIDE-22417) Eclipse will not run with java9 - NoClassDefFoundError
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22417?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-22417.
------------------------------
> Eclipse will not run with java9 - NoClassDefFoundError
> ------------------------------------------------------
>
> Key: JBIDE-22417
> URL: https://issues.jboss.org/browse/JBIDE-22417
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.4.0.Alpha2
> Reporter: Martin Malina
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: java9
> Fix For: 4.5.1.Final
>
> Attachments: e, eclipse.log.20161021-1321.txt
>
>
> As of the latest build of Oracle JDK 9, Eclipse Neon M7 will not start.
> Java version:
> {code}
> $ java -version
> java version "9-ea"
> Java(TM) SE Runtime Environment (build 9-ea+118)
> Java HotSpot(TM) 64-Bit Server VM (build 9-ea+118, mixed mode)
> {code}
> Error log:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2016-05-19 11:14:42.241
> !MESSAGE Application error
> !STACK 1
> org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:386)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:490)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:504)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:203)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:626)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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 jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:531)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375)
> ... 22 more
> Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:394)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(java.base@9-ea/ClassLoader.java:419)
> ... 24 more
> !ENTRY org.eclipse.e4.ui.workbench 4 0 2016-05-19 11:14:42.248
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> java.lang.NoClassDefFoundError: javax/annotation/PreDestroy
> at org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:426)
> at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:154)
> at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:78)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.handleInvalid(TrackableComputationExt.java:74)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:175)
> at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.dispose(EclipseContextOSGi.java:106)
> at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.bundleChanged(EclipseContextOSGi.java:139)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:903)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213)
> at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120)
> at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112)
> at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:156)
> at org.eclipse.osgi.container.Module.publishEvent(Module.java:476)
> at org.eclipse.osgi.container.Module.doStop(Module.java:634)
> at org.eclipse.osgi.container.Module.stop(Module.java:498)
> at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:191)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165)
> at java.lang.Thread.run(java.base@9-ea/Thread.java:804)
> Caused by: java.lang.ClassNotFoundException: javax.annotation.PreDestroy cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:394)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(java.base@9-ea/ClassLoader.java:419)
> ... 21 more
> {code}
> Upstream issue - targeted for Neon.1:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=493761
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month