August 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1095) Support the use of Lambdaj in the generated DTOs for REST resources

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1095: -------------------------------------- Summary: Support the use of Lambdaj in the generated DTOs for REST resources Key: FORGE-1095 URL: https://issues.jboss.org/browse/FORGE-1095 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Reporter: Vineet Reynolds Arising out of the work in FORGE-1060, it would be beneficial to support the use of functional programming paradigms in the generated DTOs. Since Java 6 and 7 do not support these natively, support would be added through the use of libraries. One of them is Lambdaj. Note - to support other libraries for functional programming, raise a new feature request. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1086) JavaParser fails to identify types of ArrayType in field types

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1086?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1086: ----------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 1.3.4.Final Resolution: Done Pushed upstream: https://github.com/forge/java-parser/commit/13c7ddedae9ddec62a57722774a64... > JavaParser fails to identify types of ArrayType in field types > -------------------------------------------------------------- > > Key: FORGE-1086 > URL: https://issues.jboss.org/browse/FORGE-1086 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.3.4.Final > > > Similar to FORGE-1026, {{org.jboss.forge.parser.java.Field.getQualifiedType()}} converts array types into simple types resulting in loss of information about the field type. > This is due to Arrays being stripped away when org.jboss.forge.parser.java.impl.AbstractJavaSource.resolveType(String) is invoked. The type returned by AbstractJavaSource omits any information about the ArrayType in the provided argument, and this is not accounted for when returning the qualified type. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-891) Support the APK packaging type in Maven projects

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-891?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-891: ---------------------------------- Fix Version/s: 2.x Future (was: 1.x Future) > Support the APK packaging type in Maven projects > ------------------------------------------------ > > Key: FORGE-891 > URL: https://issues.jboss.org/browse/FORGE-891 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.3.Final, 2.0.0.Alpha3 > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > This is related to the addition of support for Maven-based Android app development in Forge. > If we follow the approach recommended by the Sonatype book - [Maven: The Complete Reference|http://books.sonatype.com/mvnref-book/reference/android-dev.html], then we'd need to support packaging type of APK in the project POM, to enable Android app development using Maven. > The Android Maven Plugin is very nice for this - https://code.google.com/p/maven-android-plugin/ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1092) Upgrade to Arquillian 1.1.1.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1092?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1092. ---------------------------------- Resolution: Done > Upgrade to Arquillian 1.1.1.Final > --------------------------------- > > Key: FORGE-1092 > URL: https://issues.jboss.org/browse/FORGE-1092 > Project: Forge > Issue Type: Component Upgrade > Components: Test Harness > Affects Versions: 2.0.0.Alpha10 > Reporter: George Gastaldi > Priority: Trivial > Fix For: 2.0.0.Alpha11 > > > Minor bug fixes -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1092) Upgrade to Arquillian 1.1.1.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1092?page=com.atlassian.jira.plugin... ] George Gastaldi reopened FORGE-1092: ------------------------------------ Assignee: George Gastaldi > Upgrade to Arquillian 1.1.1.Final > --------------------------------- > > Key: FORGE-1092 > URL: https://issues.jboss.org/browse/FORGE-1092 > Project: Forge > Issue Type: Component Upgrade > Components: Test Harness > Affects Versions: 2.0.0.Alpha10 > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Trivial > Fix For: 2.0.0.Alpha11 > > > Minor bug fixes -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1092) Upgrade to Arquillian 1.1.1.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1092?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1092. ---------------------------------- Resolution: Done > Upgrade to Arquillian 1.1.1.Final > --------------------------------- > > Key: FORGE-1092 > URL: https://issues.jboss.org/browse/FORGE-1092 > Project: Forge > Issue Type: Component Upgrade > Components: Test Harness > Affects Versions: 2.0.0.Alpha10 > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Trivial > Fix For: 2.0.0.Alpha11 > > > Minor bug fixes -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-891) Support the APK packaging type in Maven projects

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-891?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-891: --------------------------------------- Hi [~rajonjava], PackagingFacet.setPackagingType(String) is already implemented in Forge 2. I'd suggest you to try to port your plugin to Forge 2 if possible, and develop an Android addon if possible. Best Regards, George > Support the APK packaging type in Maven projects > ------------------------------------------------ > > Key: FORGE-891 > URL: https://issues.jboss.org/browse/FORGE-891 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.3.Final, 2.0.0.Alpha3 > Reporter: Vineet Reynolds > Fix For: 1.x Future > > > This is related to the addition of support for Maven-based Android app development in Forge. > If we follow the approach recommended by the Sonatype book - [Maven: The Complete Reference|http://books.sonatype.com/mvnref-book/reference/android-dev.html], then we'd need to support packaging type of APK in the project POM, to enable Android app development using Maven. > The Android Maven Plugin is very nice for this - https://code.google.com/p/maven-android-plugin/ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-891) Support the APK packaging type in Maven projects

by Rajmahendra Hegde (JIRA)

[ https://issues.jboss.org/browse/FORGE-891?page=com.atlassian.jira.plugin.... ] Rajmahendra Hegde commented on FORGE-891: ----------------------------------------- We can make packagingFacet.setPackagingType(String) accepts as String and default value is jar. Lets user set it as packagingFacet.setPackagingType("war") etc. So we can accommodate not only apk but (hudsom/jenkin plugin(just a thought).. Java ME etc) anything comes in future.. > Support the APK packaging type in Maven projects > ------------------------------------------------ > > Key: FORGE-891 > URL: https://issues.jboss.org/browse/FORGE-891 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.3.Final, 2.0.0.Alpha3 > Reporter: Vineet Reynolds > Fix For: 1.x Future > > > This is related to the addition of support for Maven-based Android app development in Forge. > If we follow the approach recommended by the Sonatype book - [Maven: The Complete Reference|http://books.sonatype.com/mvnref-book/reference/android-dev.html], then we'd need to support packaging type of APK in the project POM, to enable Android app development using Maven. > The Android Maven Plugin is very nice for this - https://code.google.com/p/maven-android-plugin/ -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1094) Support creation of REST resources based on business services

by Vineet Reynolds (JIRA)

Vineet Reynolds created FORGE-1094: -------------------------------------- Summary: Support creation of REST resources based on business services Key: FORGE-1094 URL: https://issues.jboss.org/browse/FORGE-1094 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Affects Versions: 1.3.3.Final Reporter: Vineet Reynolds Related to FORGE-1061, it would be beneficial to support creation of REST resources based on domain/business services instead of JPA entities. This would lend itself to more cohesive DTOs instead of having a DTO model that is mostly a mirror of the underlying JPA data/object model. -- 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, 2 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 closed FORGEPLUGINS-122. ---------------------------------------- > 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2013