August 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1073) REST plugin does not parse the application path correctly from an existing project

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1073: -------------------------------------- Summary: REST plugin does not parse the application path correctly from an existing project Key: FORGE-1073 URL: https://issues.jboss.org/browse/FORGE-1073 Project: Forge Issue Type: Bug Components: Builtin Plugins Affects Versions: 1.3.3.Final Reporter: Vineet Reynolds Given an existing {{@ApplicationPath}} annotation like : {{@ApplicationPath("/rest")}}, the value {{"/rest"}} is stored as the rootpath in {{.forge_settings}}. This is in contrast to {{/rest}} when input via the Shell. We should canonicalize the stored value, i.e. parse the annotation correctly for existing projects. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-122) AngularJS scaffolding is aborted when no suitable fields are found for display

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-122?page=com.atlassian.jira.... ] Vineet Reynolds resolved FORGEPLUGINS-122. ------------------------------------------ Resolution: Done Pushed upstream: https://github.com/forge/angularjs-scaffoldx-plugin/commit/a4a3028963ebac... > AngularJS scaffolding is aborted when no suitable fields are found for display > ------------------------------------------------------------------------------ > > Key: FORGEPLUGINS-122 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-122 > Project: Forge Plugins > Issue Type: Bug > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > This is based on the current TicketMonster model. When scaffolding the model, the following exception is thrown on processing the {{Show}} entity: > {noformat} > java.lang.IllegalArgumentException: promptChoice() Cannot ask user to select from a list of nothing. Ensure you have values in your options list. > at org.jboss.forge.shell.AbstractShellPrompt.promptChoiceTyped(AbstractShellPrompt.java:305) > at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.promptChoiceTyped(ShellImpl$Proxy$_$$_WeldClientProxy.java) > at org.jboss.forge.scaffold.angularjs.InspectionResultProcessor.chooseRelationshipOptionLabels(InspectionResultProcessor.java:110) > at org.jboss.forge.scaffold.angularjs.InspectionResultProcessor.enhanceResults(InspectionResultProcessor.java:54) > at org.jboss.forge.scaffold.angularjs.AngularScaffold.generateFrom(AngularScaffold.java:214) > at org.jboss.forge.scaffoldx.plugins.ScaffoldXPlugin.generateFromResources(ScaffoldXPlugin.java:118) > 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:601) > at org.jboss.forge.shell.command.Execution.perform(Execution.java:160) > at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109) > at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47) > at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:795) > at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:818) > at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:608) > 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:601) > at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48) > at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125) > at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java) > 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:601) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) > at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) > at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616) > at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:186) > at java.lang.Thread.run(Thread.java:722) > {noformat} > The underlying reason for this exception is that all of the properties are association on other JPA entities (and hence not treated as displayable) or happen to be treated as hidden fields (the generated Id is treated as hidden by Metawidget). > The {{@Id}} annotated field should be used in such cases if no displayable properties are found. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-122) AngularJS scaffolding is aborted when no suitable fields are found for display

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGEPLUGINS-122: -------------------------------------------- Summary: AngularJS scaffolding is aborted when no suitable fields are found for display Key: FORGEPLUGINS-122 URL: https://issues.jboss.org/browse/FORGEPLUGINS-122 Project: Forge Plugins Issue Type: Bug Components: AngularJS Scaffold Reporter: Vineet Reynolds Assignee: Vineet Reynolds This is based on the current TicketMonster model. When scaffolding the model, the following exception is thrown on processing the {{Show}} entity: {noformat} java.lang.IllegalArgumentException: promptChoice() Cannot ask user to select from a list of nothing. Ensure you have values in your options list. at org.jboss.forge.shell.AbstractShellPrompt.promptChoiceTyped(AbstractShellPrompt.java:305) at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.promptChoiceTyped(ShellImpl$Proxy$_$$_WeldClientProxy.java) at org.jboss.forge.scaffold.angularjs.InspectionResultProcessor.chooseRelationshipOptionLabels(InspectionResultProcessor.java:110) at org.jboss.forge.scaffold.angularjs.InspectionResultProcessor.enhanceResults(InspectionResultProcessor.java:54) at org.jboss.forge.scaffold.angularjs.AngularScaffold.generateFrom(AngularScaffold.java:214) at org.jboss.forge.scaffoldx.plugins.ScaffoldXPlugin.generateFromResources(ScaffoldXPlugin.java:118) 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:601) at org.jboss.forge.shell.command.Execution.perform(Execution.java:160) at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109) at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47) at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:795) at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:818) at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:608) 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:601) at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125) at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java) 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:601) at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622) at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616) at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:186) at java.lang.Thread.run(Thread.java:722) {noformat} The underlying reason for this exception is that all of the properties are association on other JPA entities (and hence not treated as displayable) or happen to be treated as hidden fields (the generated Id is treated as hidden by Metawidget). The {{@Id}} annotated field should be used in such cases if no displayable properties are found. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1015) Java source/target versions should be configurable in JavaCompilerFacet

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1015?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1015: -------------------------------------- Fix Version/s: 2.x Future > Java source/target versions should be configurable in JavaCompilerFacet > ----------------------------------------------------------------------- > > Key: FORGE-1015 > URL: https://issues.jboss.org/browse/FORGE-1015 > Project: Forge > Issue Type: Enhancement > Components: Maven Plugin > Affects Versions: 1.3.3.Final > Reporter: Fred Bricon > Fix For: 2.x Future > > > I see https://github.com/forge/core/blob/master/project-model-maven/src/main/ja... has hardcoded source/target versions for the maven-compiler-plugin configuration > IMHO, these (along the encoding) should be overrideable via CLI options. Also, the default version should be inferred from the currently running JVM. One caveat though, is that would make forge build tests dependent on the running JVM. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1072) DependenyInstaller should support resolution of Project Properties via MetadataFacet

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1072?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1072. ------------------------------------- Resolution: Done > DependenyInstaller should support resolution of Project Properties via MetadataFacet > ------------------------------------------------------------------------------------ > > Key: FORGE-1072 > URL: https://issues.jboss.org/browse/FORGE-1072 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 2.0.0.Alpha9 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha10 > > -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1072) DependenyInstaller should support resolution of Project Properties via MetadataFacet

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1072?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1072: ----------------------------------------- Assignee: Lincoln Baxter III > DependenyInstaller should support resolution of Project Properties via MetadataFacet > ------------------------------------------------------------------------------------ > > Key: FORGE-1072 > URL: https://issues.jboss.org/browse/FORGE-1072 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 2.0.0.Alpha9 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha10 > > -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1071) Java compiler configuration should be split away from JavaSourceFacet

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1071?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1071. ------------------------------------- Resolution: Done > Java compiler configuration should be split away from JavaSourceFacet > --------------------------------------------------------------------- > > Key: FORGE-1071 > URL: https://issues.jboss.org/browse/FORGE-1071 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins, Parsers / File Manipulation > Affects Versions: 2.0.0.Alpha9 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha10 > > -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1068) Addons created with 'addons' should be configured to use the test harness.

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1068?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1068. ------------------------------------- Resolution: Done > Addons created with 'addons' should be configured to use the test harness. > -------------------------------------------------------------------------- > > Key: FORGE-1068 > URL: https://issues.jboss.org/browse/FORGE-1068 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 2.0.0.Alpha9 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha10 > > > Currently, the test harness is not configured in simple or complex addon project layouts. It should be. -- 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1070) FacetFactory should consider @RequiresFacet annotations as part of facet.isInstalled() check;

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1070?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1070: ----------------------------------------- Assignee: Lincoln Baxter III > FacetFactory should consider @RequiresFacet annotations as part of facet.isInstalled() check; > --------------------------------------------------------------------------------------------- > > Key: FORGE-1070 > URL: https://issues.jboss.org/browse/FORGE-1070 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 2.0.0.Alpha9 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > 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

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1069) Property management methods should be on MetadataFacet, not DependencyFacet

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1069?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1069. ------------------------------------- Fix Version/s: 2.0.0.Alpha10 (was: 2.x Future) Resolution: Done > Property management methods should be on MetadataFacet, not DependencyFacet > --------------------------------------------------------------------------- > > Key: FORGE-1069 > URL: https://issues.jboss.org/browse/FORGE-1069 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 2.0.0.Alpha9 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha10 > > -- 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

11 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2013