March 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1684) Port the MetawidgetInspectorFacade API from the Forge 1 scaffold-x API

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1684?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1684: ----------------------------------- Priority: Major (was: Minor) > Port the MetawidgetInspectorFacade API from the Forge 1 scaffold-x API > ---------------------------------------------------------------------- > > Key: FORGE-1684 > URL: https://issues.jboss.org/browse/FORGE-1684 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.2.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > The MetawidgetInspectorFacade was introduced in the Forge 1 scaffold-x API for use by other scaffolding providers that could use Metawidget only for inspecting classes and producing inspection results that could be enhanced and later using in templating. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1684) Port the MetawidgetInspectorFacade API from the Forge 1 scaffold-x API

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1684: -------------------------------------- Summary: Port the MetawidgetInspectorFacade API from the Forge 1 scaffold-x API Key: FORGE-1684 URL: https://issues.jboss.org/browse/FORGE-1684 Project: Forge Issue Type: Feature Request Components: Scaffold Affects Versions: 2.2.0.Final Reporter: Vineet Reynolds Assignee: Vineet Reynolds Priority: Minor The MetawidgetInspectorFacade was introduced in the Forge 1 scaffold-x API for use by other scaffolding providers that could use Metawidget only for inspecting classes and producing inspection results that could be enhanced and later using in templating. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1683) Usage of abstract Resource should be preferred over FileResource and DirectoryResource in addons depending on the Resource addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1683?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1683: ----------------------------------- Priority: Critical (was: Major) > Usage of abstract Resource should be preferred over FileResource and DirectoryResource in addons depending on the Resource addon > -------------------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-1683 > URL: https://issues.jboss.org/browse/FORGE-1683 > Project: Forge > Issue Type: Enhancement > Components: Projects > Affects Versions: 2.2.0.Final > Reporter: George Gastaldi > Priority: Critical > Fix For: 2.x Future > > > [~sbryzak2] needs to store the contents of a project in a virtual filesystem (a database for example). The problem is that many addons (specially the projects addon) refer directly to DirectoryResource and FileResource. Other addons may require changes as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1683) Usage of abstract Resource should be preferred over FileResource and DirectoryResource in addons depending on the Resource addon

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1683: -------------------------------------- Summary: Usage of abstract Resource should be preferred over FileResource and DirectoryResource in addons depending on the Resource addon Key: FORGE-1683 URL: https://issues.jboss.org/browse/FORGE-1683 Project: Forge Issue Type: Feature Request Components: Projects Affects Versions: 2.2.0.Final Reporter: George Gastaldi Fix For: 2.x Future [~sbryzak2] needs to store the contents of a project in a virtual filesystem (a database for example). The problem is that many addons (specially the projects addon) refer directly to DirectoryResource and FileResource. Other addons may require changes as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1683) Usage of abstract Resource should be preferred over FileResource and DirectoryResource in addons depending on the Resource addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1683?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1683: ----------------------------------- Issue Type: Enhancement (was: Feature Request) > Usage of abstract Resource should be preferred over FileResource and DirectoryResource in addons depending on the Resource addon > -------------------------------------------------------------------------------------------------------------------------------- > > Key: FORGE-1683 > URL: https://issues.jboss.org/browse/FORGE-1683 > Project: Forge > Issue Type: Enhancement > Components: Projects > Affects Versions: 2.2.0.Final > Reporter: George Gastaldi > Fix For: 2.x Future > > > [~sbryzak2] needs to store the contents of a project in a virtual filesystem (a database for example). The problem is that many addons (specially the projects addon) refer directly to DirectoryResource and FileResource. Other addons may require changes as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1680) Cannot start Forge 2 in Eclipse if Furnace fails to start.

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1680?page=com.atlassian.jira.plugin... ] Vineet Reynolds commented on FORGE-1680: ---------------------------------------- I remember this was fixed for 2.2.0.Final - https://github.com/forge/core/commit/a84194f3a53e6fb110ea014a1dbd13be3dbf... and https://github.com/forge/core/commit/4744f940a2af29c05e27b925a845810d9bee... . This might be something to do with using 2.2.0 with older addons in {{.forge}}. Maybe a cleanup will fix this specific instance ? I discussed this with [~gastaldi] and it would be useful to point out what addons in addon repositories are causing this. That would be a big plus, since certain addons in {{.forge}} may eventually become incompatible (wrt to dependency cycles) if they depend on core addons. > Cannot start Forge 2 in Eclipse if Furnace fails to start. > ---------------------------------------------------------- > > Key: FORGE-1680 > URL: https://issues.jboss.org/browse/FORGE-1680 > Project: Forge > Issue Type: Feature Request > Components: UI - Eclipse > Affects Versions: 2.1.1.Final > Reporter: Lincoln Baxter III > Assignee: Koen Aers > > {code}org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.convert.ConverterFactory] could be found in any started addons. > at org.jboss.forge.furnace.impl.addons.ImportedImpl.get(ImportedImpl.java:80) > 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.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:98) > at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) > at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:71) > at org.jboss.forge.furnace.services.Imported_$$_javassist_1c698202-6757-4f29-a47f-9e5b7ee818ad.get(Imported_$$_javassist_1c698202-6757-4f29-a47f-9e5b7ee818ad.java) > at org.jboss.tools.forge.ext.core.FurnaceService.lookup(FurnaceService.java:87) > at org.jboss.tools.forge.ext.core.FurnaceService.getConverterFactory(FurnaceService.java:61) > at org.jboss.tools.forge.ui.ext.context.UIContextImpl.<init>(UIContextImpl.java:55) > at org.jboss.tools.forge.ui.ext.dialog.WizardDialogHelper.<init>(WizardDialogHelper.java:50) > at org.jboss.tools.forge.ui.ext.dialog.UICommandListDialog.<init>(UICommandListDialog.java:65) > at org.jboss.tools.forge.ui.ext.handlers.ForgeCommandHandler.execute(ForgeCommandHandler.java:39) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) > 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:213) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:285) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:504) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:555) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:376) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:322) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:84) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1080) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4165) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1489) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1474) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1503) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1499) > at org.eclipse.swt.widgets.Canvas.sendKeyEvent(Canvas.java:496) > at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1060) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5648) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSResponder.interpretKeyEvents(NSResponder.java:68) > at org.eclipse.swt.widgets.Composite.keyDown(Composite.java:594) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5558) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221) > at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2104) > at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2318) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5620) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5057) > at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5206) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3648) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > 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:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > Caused by: org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.convert.ConverterFactory] could be found in any started addons. > ... 82 more{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1682) Highlighter Scanners should be more extensible

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1682?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1682: ---------------------------------------- One idea would be to get rid of the {{org.jboss.forge.addon.text.highlight.Scanner.Type}} enum and use the {{org.jboss.forge.addon.text.highlight.Scanner.Factory}} to locate the appropriate {{Scanner}} given the file name > Highlighter Scanners should be more extensible > ---------------------------------------------- > > Key: FORGE-1682 > URL: https://issues.jboss.org/browse/FORGE-1682 > Project: Forge > Issue Type: Enhancement > Components: Text > Affects Versions: 2.2.1.Final > Reporter: George Gastaldi > Priority: Minor > Fix For: 2.x Future > > > Addons could create extensions for the Highlight API to allow additional {{Scanner}} implementations for specific file types, for example -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1682) Highlighter Scanners should be more extensible

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1682: -------------------------------------- Summary: Highlighter Scanners should be more extensible Key: FORGE-1682 URL: https://issues.jboss.org/browse/FORGE-1682 Project: Forge Issue Type: Enhancement Components: Text Affects Versions: 2.2.1.Final Reporter: George Gastaldi Priority: Minor Fix For: 2.x Future Addons could create extensions for the Highlight API to allow additional {{Scanner}} implementations for specific file types, for example -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1681) Extend the Highlighter for Properties files

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1681: -------------------------------------- Summary: Extend the Highlighter for Properties files Key: FORGE-1681 URL: https://issues.jboss.org/browse/FORGE-1681 Project: Forge Issue Type: Feature Request Components: Text Affects Versions: 2.2.1.Final Reporter: George Gastaldi Priority: Minor Fix For: 2.x Future -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (FORGE-833) java new-field improvements

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-833?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-833: ---------------------------------- Description: It should be possible to add getters and setters when a new field is created using the following command: {code} java new-field --named partType --type ~.model.PartType --accessType PRIVATE --generateMutator --generateAccessor {code} Where: - named: The field name - type: the field type - accessModifier: The access modifier of this field: (PUBLIC,PRIVATE,PROTECTED,PACKAGE) - generateMutator: generate setter - generateAccessor: generate getter was: It should be possible to add getters and setters when a new field is created using the following command: {code} java new-field --named partType --type ~.model.PartType --accessType PRIVATE --asJavaBean {code} Where: - named: The field name - type: the field type - accessModifier: The access modifier of this field: (PUBLIC,PRIVATE,PROTECTED,PACKAGE) - asJavaBean: generate getters and setters > java new-field improvements > --------------------------- > > Key: FORGE-833 > URL: https://issues.jboss.org/browse/FORGE-833 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.2.Final > Reporter: George Gastaldi > Assignee: Ivan St. Ivanov > Labels: starter > Fix For: 2.x Future > > > It should be possible to add getters and setters when a new field is created using the following command: > {code} > java new-field --named partType --type ~.model.PartType --accessType PRIVATE --generateMutator --generateAccessor > {code} > Where: > - named: The field name > - type: the field type > - accessModifier: The access modifier of this field: (PUBLIC,PRIVATE,PROTECTED,PACKAGE) > - generateMutator: generate setter > - generateAccessor: generate getter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2014