[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-16286:
------------------------------------
[~psrna] can someone from QE verify if this is still relevant ?
> CDI builder (not import, workspace rebuild) is very slow in wildfly
> -------------------------------------------------------------------
>
> Key: JBIDE-16286
> URL: https://issues.jboss.org/browse/JBIDE-16286
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, maven
> Affects Versions: 4.1.1.Final
> Reporter: Andre Dietisheim
> Priority: Critical
> Labels: performance
> Fix For: 4.5.0.AM2
>
> Attachments: VisualVM 1.3.2 _083.png, cdi-builder.ogv, cleanBuild.png, full-bundle-listing.txt, maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt, updatingPom.png
>
>
> When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me.
> Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me.
> [^cdi-builder.ogv]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-16286) CDI builder (not import, workspace rebuild) is very slow in wildfly
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-16286:
-------------------------------
Fix Version/s: 4.5.0.AM2
(was: 4.5.0.AM1)
> CDI builder (not import, workspace rebuild) is very slow in wildfly
> -------------------------------------------------------------------
>
> Key: JBIDE-16286
> URL: https://issues.jboss.org/browse/JBIDE-16286
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, maven
> Affects Versions: 4.1.1.Final
> Reporter: Andre Dietisheim
> Priority: Critical
> Labels: performance
> Fix For: 4.5.0.AM2
>
> Attachments: VisualVM 1.3.2 _083.png, cdi-builder.ogv, cleanBuild.png, full-bundle-listing.txt, maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt, updatingPom.png
>
>
> When working in a wildfly workspace with all wildfly projects imported and CDI builder enabled, workspace rebuilds (that you trigger by changing poms and then do maven update project) are a lot slower than without it. Re-building the whole workspace can easily take up to 20 minutes for me.
> Hard to give more general purpose details, I did a quick screencast to give an impression how slow things are for me.
> [^cdi-builder.ogv]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-23567) Integration tests global refactoring
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23567?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23567:
-------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.0.AM1)
> Integration tests global refactoring
> ------------------------------------
>
> Key: JBIDE-23567
> URL: https://issues.jboss.org/browse/JBIDE-23567
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: integration-test, integration_tests
> Fix For: 4.5.0.Final
>
>
> We should done some work on integration tests so that we can rely on them to improve our code quality and reduce the technical debt.
> A sprint will be dedicated.
> Here are the tasks we should work on:
> * run tests from Maven and document how to run them if specific steps are required
> * If failure, fix the failed tests
> * Refactor / move tests to the components repository
> * Fix/make sure tests are run in PR check
> This huge task should be done component per component. Sub-tasks JIRA will be created for each component.
> You can use this document as a starting point:[https://docs.google.com/document/d/1bl8pJ2aW65UpyGpr3qxoAUREDWL26N...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-17231) Migrate Usage to Universal Analytics
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17231?page=com.atlassian.jira.plugi... ]
Jeff MAURY closed JBIDE-17231.
------------------------------
Resolution: Won't Do
Rejected as GA will be moved to another provider in the short/middle term
> Migrate Usage to Universal Analytics
> ------------------------------------
>
> Key: JBIDE-17231
> URL: https://issues.jboss.org/browse/JBIDE-17231
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: usage
> Reporter: Alexey Kazakov
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.5.0.AM1
>
>
> https://developers.google.com/analytics/devguides/collection/upgrade/?hl=...
> {quote}
> Universal Analytics is a set of technological innovations that improve the way data is collected and processed in Google Analytics.
> The Universal Analytics Upgrade is a process you can use to upgrade all of your classic Google Analytics properties into Universal Analytics properties without losing any data or changing your account settings.
> All Google Analytics properties will soon be required to use Universal Analytics. *Any properties that don’t follow the upgrade process will be auto-transferred to Universal Analytics in the future*.{quote}
> The transition from classic Google Analytics to Universal Analytics is happening incrementally over several phases.
> The current phase is *Phase 3: Universal Analytics out of beta*.
> The next phase is *Phase 4: Universal Analytics is the operating standard for Google Analytics.*:
> {quote}All properties have been upgraded into Universal Analytics.
> The following features will be deprecated:
> ga.js
> urchin.js
> WAP/server-side snippets
> YT / MO
> Custom variables
> User defined variables
> *Data collected from the deprecated features will be processed for a minimum of 2 years*.{quote}
> Currently, JBT usage sends requests using ga.js format. We should investigate what's changed in Analytics.js. And get ready to migrate to that new format.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-21674) Enable hierarchical view by default in Project Explorer
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21674?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21674:
-------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.0.AM1)
> Enable hierarchical view by default in Project Explorer
> -------------------------------------------------------
>
> Key: JBIDE-21674
> URL: https://issues.jboss.org/browse/JBIDE-21674
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common, upstream
> Reporter: Xavier Coulon
> Assignee: Jeff MAURY
> Fix For: 4.5.0.Final
>
>
> Project Explorer has been supporting hierarchical view of projects since Mars, but this is not enabled by default in Eclipse (core) even though this is a valuable features, especially for Maven projects that include modules (ie, sub-projects).
> After discussing about it with [~mickael_istria] and [~nickboldt], we should see if we can enable this setting by default in DevStudio.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[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 updated JBIDE-22417:
-------------------------------
Fix Version/s: 4.5.0.AM2
(was: 4.5.0.AM1)
> 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.0.AM2
>
> 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.2.3#72005)
8 years, 9 months