November 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18810) 'Angular' plugin won't be loaded by default when Tern/Angular will be moved to 0.7.x stream

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18810?page=com.atlassian.jira.plugi... ] Victor Rubezhny updated JBIDE-18810: ------------------------------------ Fix Version/s: 4.2.1.Final > 'Angular' plugin won't be loaded by default when Tern/Angular will be moved to 0.7.x stream > ------------------------------------------------------------------------------------------- > > Key: JBIDE-18810 > URL: https://issues.jboss.org/browse/JBIDE-18810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.1.CR1 > Reporter: Victor Rubezhny > Fix For: 4.2.1.Final > > > 'Angular' plugin won't be loaded by default when Tern.java/AngularJS-eclipse will be moved to 0.7.x stream. > The 'angular' plug-in must be contributed as a default module by tern's nature adapter extension point explicitly. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3076) Move JMX/JVM Monitoring features from Fuse Tools to server core

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3076?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3076: ----------------------------- CDW release: + (was: ?) > Move JMX/JVM Monitoring features from Fuse Tools to server core > --------------------------------------------------------------- > > Key: JBDS-3076 > URL: https://issues.jboss.org/browse/JBDS-3076 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: requirements, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 8.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3076) Move JMX/JVM Monitoring features from Fuse Tools to server core

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3076?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3076: ----------------------------- CDW qa_ack: + (was: ?) > Move JMX/JVM Monitoring features from Fuse Tools to server core > --------------------------------------------------------------- > > Key: JBDS-3076 > URL: https://issues.jboss.org/browse/JBDS-3076 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: requirements, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 8.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3076) Move JMX/JVM Monitoring features from Fuse Tools to server core

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3076?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3076: ----------------------------- CDW docs_ack: + (was: ?) > Move JMX/JVM Monitoring features from Fuse Tools to server core > --------------------------------------------------------------- > > Key: JBDS-3076 > URL: https://issues.jboss.org/browse/JBDS-3076 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: requirements, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 8.0.0.Beta3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18810) 'Angular' plugin won't be loaded by default when Tern/Angular will be moved to 0.7.x stream

by Victor Rubezhny (JIRA)

Victor Rubezhny created JBIDE-18810: --------------------------------------- Summary: 'Angular' plugin won't be loaded by default when Tern/Angular will be moved to 0.7.x stream Key: JBIDE-18810 URL: https://issues.jboss.org/browse/JBIDE-18810 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing Affects Versions: 4.2.1.CR1 Reporter: Victor Rubezhny 'Angular' plugin won't be loaded by default when Tern.java/AngularJS-eclipse will be moved to 0.7.x stream. The 'angular' plug-in must be contributed as a default module by tern's nature adapter extension point explicitly. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18752) Freemarker plugin does not work for square bracket (since JBT 4.2.0.Final)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18752?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18752: ----------------------------------- Fix Version/s: 4.2.1.Final (was: 4.2.1.CR1) > Freemarker plugin does not work for square bracket (since JBT 4.2.0.Final) > -------------------------------------------------------------------------- > > Key: JBIDE-18752 > URL: https://issues.jboss.org/browse/JBIDE-18752 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Fix For: 4.2.1.Final > > > From https://github.com/jbosstools/jbosstools-freemarker/issues/26 > {quote} > When using the plugin to edit freemarker files that use the square bracket syntax the editor fails to highlight the syntax (this is happening in JBoss Tools 4.20 Final). > I think the file: src / org / jboss / ide / eclipse / freemarker / editor / DocumentProvider.java > on line 70 is causing the syntax highlighting problem: > {code}if (ch != LexicalConstants.SQUARE_SYNTAX_MARKER.charAt(i)) { > return SyntaxMode.ANGLE; > } > SQUARE_SYNTAX_MARKER.charAt(i) > {code} > It should start in 0 and have a different index than i (the index of the file content) to have a proper string matching. Also, SQUARE_SYNTAX_MARKER is [#ftl, not all files start with a ftl tag, so I don't see the need for "ftl" at the end, so that's why in the following example fix I put j < 2. > e.g. > {code} > int j =0; > for (; i < docLength && j < 2; i++) { > char ch = document.getChar(i); > if (ch != LexicalConstants.SQUARE_SYNTAX_MARKER.charAt(j)) { > return SyntaxMode.ANGLE; > } > j++; > } > {code} > {quote} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18712) Add wildfly archetypes to JBoss Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18712?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18712: -------------------------------- Fix Version/s: 4.2.1.CR1 (was: 4.2.1.Final) > Add wildfly archetypes to JBoss Central > --------------------------------------- > > Key: JBIDE-18712 > URL: https://issues.jboss.org/browse/JBIDE-18712 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.2.1.CR1 > > > JBoss Central doesn't propose the Wildfly archetypes when a Wildfly runtime is selected, even though they have been released in Maven Central : http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.wildfly.archetype%22 > They should be added to stacks.yaml, with environment: web-ee7 for the pure webapp and environment: full-ee7 for the EAR -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18712) Add wildfly archetypes to JBoss Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18712?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-18712. --------------------------------- Resolution: Done This has been fixed a while ago already > Add wildfly archetypes to JBoss Central > --------------------------------------- > > Key: JBIDE-18712 > URL: https://issues.jboss.org/browse/JBIDE-18712 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.2.1.Final > > > JBoss Central doesn't propose the Wildfly archetypes when a Wildfly runtime is selected, even though they have been released in Maven Central : http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.wildfly.archetype%22 > They should be added to stacks.yaml, with environment: web-ee7 for the pure webapp and environment: full-ee7 for the EAR -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18598) "Configure->Add JSF Capabilities ..." throws exception on OK/Apply button pressed for Dynamic Web Project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18598?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18598: ----------------------------------- Fix Version/s: (was: 4.2.1.CR1) > "Configure->Add JSF Capabilities ..." throws exception on OK/Apply button pressed for Dynamic Web Project > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18598 > URL: https://issues.jboss.org/browse/JBIDE-18598 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, upstream > Affects Versions: 4.2.0.CR2 > Reporter: Denis Golovin > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Alpha1 > > > {code}java.util.ConcurrentModificationException > at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:859) > at java.util.ArrayList$Itr.remove(ArrayList.java:845) > at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.addManagedResource(JEE5ModelProvider.java:142) > at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.getModelResource(JEE5ModelProvider.java:186) > at org.eclipse.jst.jee.model.internal.Web25ModelProvider.getModelObject(Web25ModelProvider.java:44) > at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.getModelObject(JEE5ModelProvider.java:231) > at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getLastModificationTimeOfDDFile(AbstractMergedModelProvider.java:235) > at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.hasToReloadModel(AbstractMergedModelProvider.java:229) > at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getMergedModel(AbstractMergedModelProvider.java:218) > at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getModelObject(AbstractMergedModelProvider.java:139) > at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvider.getCachedContentProvider(JEE5ContentProvider.java:98) > at org.eclipse.jst.jee.ui.internal.navigator.Web25ContentProvider.getChildren(Web25ContentProvider.java:35) > at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:96) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$1.run(NavigatorContentServiceContentProvider.java:152) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.internalGetChildren(NavigatorContentServiceContentProvider.java:139) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.getChildren(NavigatorContentServiceContentProvider.java:119) > at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvider$1.run(JEE5ContentProvider.java:142) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:175) > at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:390) > at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:527) > at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage.performOk(FacetsPropertyPage.java:257) > at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage.performApply(FacetsPropertyPage.java:313) > at org.eclipse.jface.preference.PreferencePage$2.widgetSelected(PreferencePage.java:284) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.jboss.tools.jsf.ui.internal.handlers.AddJSFNatureHandler.addJSFNature(AddJSFNatureHandler.java:137) > at org.jboss.tools.jsf.ui.internal.handlers.AddJSFNatureHandler.execute(AddJSFNatureHandler.java:73) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:825) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:701) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$6(HandledContributionItem.java:685) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:613) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > 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:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438){code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg directories for consistency across JBT/JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3208: ---------------------------------- See https://issues.jboss.org/browse/JBDS-3163?focusedCommentId=13021099&page=... for more suggestions for new structure (cc: [~mickael_istria] ) > reorg directories for consistency across JBT/JBDS > ------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > {code} > download.jboss.org > <earlyaccess,updates,discovery>/mars > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/mars/stable is a pointer back into updates/mars) > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > and > {code} > devstudio.redhat.com > <earlyaccess,updates,discovery>/9.0 > /snapshots > /staging > /development > /stable (updates/9.0/stable is a pointer back into updates/9.0) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 9 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 November 2014