May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22284) ConcurrentModificationException below ArquillianUIUtil.getActiveType (thrown in FeatureMapUtil$BasicFeatureEIterator.checkModCount)

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22284?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-22284: ---------------------------------- Fix Version/s: 4.4.0.Alpha2 > ConcurrentModificationException below ArquillianUIUtil.getActiveType (thrown in FeatureMapUtil$BasicFeatureEIterator.checkModCount) > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22284 > URL: https://issues.jboss.org/browse/JBIDE-22284 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Affects Versions: 4.3.1.Final > Reporter: Automated Error Reporting Bot > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha2 > > > The following problem was reported via the automated error reporting: > Message: HIDDEN > {noformat} > java.util.ConcurrentModificationException: null > at org.eclipse.emf.ecore.util.FeatureMapUtil$BasicFeatureEIterator.checkModCount(FeatureMapUtil.java:555) > at org.eclipse.emf.ecore.util.FeatureMapUtil$BasicFeatureEIterator.next(FeatureMapUtil.java:373) > at org.eclipse.jst.jee.model.internal.mergers.EjbJarMerger.mergeSessionBeans(EjbJarMerger.java:145) > at org.eclipse.jst.jee.model.internal.mergers.EjbJarMerger.process(EjbJarMerger.java:74) > at org.eclipse.jst.jee.model.internal.mergers.EjbJarMerger.process(EjbJarMerger.java:79) > at org.eclipse.jst.jee.model.internal.EJB3MergedModelProvider.mergeWithModel(EJB3MergedModelProvider.java:214) > at org.eclipse.jst.jee.model.internal.EJB3MergedModelProvider.merge(EJB3MergedModelProvider.java:204) > at org.eclipse.jst.jee.model.internal.EJB3MergedModelProvider.internalModelChanged(EJB3MergedModelProvider.java:174) > at org.eclipse.jst.jee.model.internal.EJB3MergedModelProvider.annotationModelChanged(EJB3MergedModelProvider.java:151) > at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider$AnnotationModelListener.modelsChanged(AbstractMergedModelProvider.java:83) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider$1.run(AbstractAnnotationModelProvider.java:189) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.notifyListeners(AbstractAnnotationModelProvider.java:184) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.notifyListeners(AbstractAnnotationModelProvider.java:157) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.internalPostReconcile(AbstractAnnotationModelProvider.java:467) > at org.eclipse.jst.jee.model.internal.common.AbstractAnnotationModelProvider.elementChanged(AbstractAnnotationModelProvider.java:446) > at org.eclipse.jdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1662) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1652) > at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1504) > at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1463) > at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:770) > at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:789) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1250) > at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1211) > at org.eclipse.jdt.internal.corext.util.JavaModelUtil.reconcile(JavaModelUtil.java:609) > at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:283) > at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:199) > at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:183) > at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getActiveType(ArquillianUIUtil.java:182) > at org.jboss.tools.arquillian.ui.internal.commands.ArquillianPropertyTester.test(ArquillianPropertyTester.java:62) > at org.eclipse.core.internal.expressions.Property.test(Property.java:58) > at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:100) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) > at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:106) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateOr(CompositeExpression.java:68) > at org.eclipse.core.internal.expressions.OrExpression.evaluate(OrExpression.java:22) > at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53) > at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:199) > 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.e4.ui.internal.workbench.ContributionsAnalyzer.isVisible(ContributionsAnalyzer.java:256) > at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.computeVisibility(ContributionRecord.java:166) > at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.updateVisibility(ContributionRecord.java:96) > at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:188) > at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:199) > at org.eclipse.ui.internal.WorkbenchWindow$8.run(WorkbenchWindow.java:707) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155) > {noformat} > Bundles: > | org.eclipse.core.expressions | 3.5.0.v20150421-2214 | 3.5.0.v20150421-2214 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 | > | org.eclipse.e4.ui.workbench | 1.3.1.v20160203-0951 | 1.3.1.v20160203-0951 | > | org.eclipse.e4.ui.workbench.renderers.swt | 0.13.0.v20150901-1347 | 0.13.0.v20150901-1347 | > | org.eclipse.emf | 2.6.0.v20160208-0841 | 2.6.0.v20160208-0841 | > | org.eclipse.emf.ecore | 2.11.2.v20160208-0816 | 2.11.2.v20160208-0816 | > | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.11.2.v20160212-1500 | > | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.11.2.v20160128-0629 | > | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.11.2.v20151123-1510 | > | org.eclipse.jst.jee | 1.0.700.v201404092004 | 1.0.700.v201404092004 | > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | > | org.jboss.tools.arquillian.ui | 1.2.1.Final-v20160331-0142-B69 | 1.2.1.Final-v20160331-0142-B69 | > Operating Systems: > | Windows | 10.0.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571f1795e4b08bd809...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22356) NPE when editing reveng.xml

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22356?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-22356. ------------------------------- Resolution: Done > NPE when editing reveng.xml > --------------------------- > > Key: JBIDE-22356 > URL: https://issues.jboss.org/browse/JBIDE-22356 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.0.Alpha2 > > > Create new reveng.xml. > When pushing the 'Include...' or 'Exclude...' buttons and no console configuration is selected observe a NPE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-181) Allow for search and pull images from any Docker registry [EBZ#469308]

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-181?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg closed ERT-181. ------------------------------- Resolution: Duplicate Issue This is a duplicate of ERT-169, which is currently being addressed. > Allow for search and pull images from any Docker registry [EBZ#469308] > ---------------------------------------------------------------------- > > Key: ERT-181 > URL: https://issues.jboss.org/browse/ERT-181 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > > The docker-client now allows for search on a docker registry, so we should leverage that API to search for images, display available info and let the user select the image(s) to pull on the current Docker deamon (ie, Docker host). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21720) Server Adapter: user choose default route when creating the server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21720?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21720: ------------------------------------------ merged your changes into https://github.com/jbosstools/jbosstools-openshift/pull/1156/ > Server Adapter: user choose default route when creating the server > ------------------------------------------------------------------ > > Key: JBIDE-21720 > URL: https://issues.jboss.org/browse/JBIDE-21720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter, server_adapter_wizard > Fix For: 4.4.0.Alpha2 > > > Currently the Show in Web Browser always asks the user which route to open, which tends to be annoying when using the menu several times. For LiveReload support, it's even worse, the 1st route is always selected, which always leads to some problems when several routes are available. > I believe it would be best to let the user select the server adapter' default route in the OpenShift 3 Server wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22324) LiveReload needs to update to newer Jetty

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22324?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22324: -------------------------------- Summary: LiveReload needs to update to newer Jetty (was: LiveRelead needs to update to newer Jetty) > LiveReload needs to update to newer Jetty > ----------------------------------------- > > Key: JBIDE-22324 > URL: https://issues.jboss.org/browse/JBIDE-22324 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, livereload, target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Mickael Istria > Assignee: Xavier Coulon > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > With move to M7, livereload build fails: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-livereloa... > It has to be updated to use newer version of Jetty. in TP (9.3.6). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21720) Server Adapter: user choose default route when creating the server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21720?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21720: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/964, https://github.com/jbosstools/jbosstools-openshift/pull/1138, https://github.com/jbosstools/jbosstools-openshift/pull/1156/ (was: https://github.com/jbosstools/jbosstools-openshift/pull/964, https://github.com/jbosstools/jbosstools-openshift/pull/1138) > Server Adapter: user choose default route when creating the server > ------------------------------------------------------------------ > > Key: JBIDE-21720 > URL: https://issues.jboss.org/browse/JBIDE-21720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter, server_adapter_wizard > Fix For: 4.4.0.Alpha2 > > > Currently the Show in Web Browser always asks the user which route to open, which tends to be annoying when using the menu several times. For LiveReload support, it's even worse, the 1st route is always selected, which always leads to some problems when several routes are available. > I believe it would be best to let the user select the server adapter' default route in the OpenShift 3 Server wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-166) Chromium Debug context menu's enabled for everything [EBZ#491480]

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/ERT-166?page=com.atlassian.jira.plugin.sy... ] Shane Bryzak reassigned ERT-166: -------------------------------- Assignee: Shane Bryzak > Chromium Debug context menu's enabled for everything [EBZ#491480] > ----------------------------------------------------------------- > > Key: ERT-166 > URL: https://issues.jboss.org/browse/ERT-166 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Shane Bryzak > Labels: Debug, bzira > > The context menu "V8 Debugging" is available for any type of selection. > I tracked this menu contribution to: "org.eclipse.wst.jsdt.chromium.debug.ui.ChromiumSourceFileActionsId.MenuId" > Should filter to only *.js files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3651) Reduce the delay between the main window opening and the first page being rendered

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3651?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3651: ----------------------------------- Here is some actual data from a profiler to put this into perspective: Reloading the app takes around 3.3 seconds on my machine (script execution and rendering) >From the 3.3 seconds: - 3 seconds (2979 ms) is script execution - around 80% of the scripting time (2392 ms) is consumed by babel transformation (called from jspm's systemjs) > Reduce the delay between the main window opening and the first page being rendered > ---------------------------------------------------------------------------------- > > Key: JBDS-3651 > URL: https://issues.jboss.org/browse/JBDS-3651 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc, ui > Fix For: 10.0.0.Alpha3 > > > Starting the installer right now leaves the user with about 3 seconds of staring at an empty window before the content shows up. > I've done a few tests on this matter and it seems majority of those 3 seconds is spent on angular bootstrap - mainly loading the required files and registering controllers. Replacing the index with simple static HTML causes the page to render almost instantaneously. > We should consider some way of showing the GUI before the user falls asleep (before angular fully loads the entire app). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22328) Connection wizard: 'OpenShift 3' is missing on drop down menu 'Server Type' (OpenShift 3 plugins wont get installed)

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22328?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22328. --------------------------------- > Connection wizard: 'OpenShift 3' is missing on drop down menu 'Server Type' (OpenShift 3 plugins wont get installed) > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22328 > URL: https://issues.jboss.org/browse/JBIDE-22328 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: JBT: 3.2.0.Alpha1-v20160509-1836-B1291 > Eclipse version: Neon Milestone 4 (4.6.0M5) > Reporter: Xia Zhao > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3 > Fix For: 4.4.0.Alpha2 > > Attachments: installation-works.png, jetty-plugin-missing.png, jetty-websocket-client.png, neon-update-site.png, openshift-plugins-version.png, Screenshot from 2016-05-11 13-40-59.png, software-update.png > > > After JBT 3.2.0.Alpha1-v20160509-1836-B1291 is installed successfully, run the New Connection Wizard, menuitem 'OpenShift 3' is missing on drop down menu 'Server Type' of 'New OpenShift Connection' window -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22354) Remediation page showing up because of Mylyn Wikitext

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22354?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22354: ---------------------------------------- Making it a blocker since it prevent all installation tests we have from being successful, so additionally to being an issue per so, it's also a high risk of hiding some other installation issue. > Remediation page showing up because of Mylyn Wikitext > ----------------------------------------------------- > > Key: JBIDE-22354 > URL: https://issues.jboss.org/browse/JBIDE-22354 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.4.0.Alpha2 > Reporter: Mickael Istria > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > Take an Eclipse JavaScript M7, and try to install all JBoss Tools from http://download.jboss.org/jbosstools/neon/snapshots/updates/ > It shows a remediation page because JBoss Tools ships an asciidoc feature which is in different version that the one upstream. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016