June 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-918) Faces Scaffolding interprets long x[][] fields as long

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-918?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-918: ---------------------------------- Component/s: Scaffold > Faces Scaffolding interprets long x[][] fields as long > ------------------------------------------------------ > > Key: FORGE-918 > URL: https://issues.jboss.org/browse/FORGE-918 > Project: Forge > Issue Type: Bug > Components: Scaffold > Reporter: Vineet Reynolds > Fix For: 1.3.1.Final > > > This is from TicketMonster. The {{SectionAllocation}} class contains a {{long allocated[][]}} field. With the getters and setters (one may need to add the setters; see FORGE-917), the generated view does not contain a widget for the n-dimensional array type, and instead displays a single numerical entry widget. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-957) Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-957?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-957: ---------------------------------- Component/s: Blessed Plugins > Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs > ------------------------------------------------------------------------------------------------------ > > Key: FORGE-957 > URL: https://issues.jboss.org/browse/FORGE-957 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha5 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > This will allow things like, detecting that the user is on Wildfly AS, and subsequently selecting appropriate versions of specifications, libraries, and other setup configurations. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-535) Support gradle as a build tool

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-535?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-535: ---------------------------------- Component/s: Build Tools - Gradle > Support gradle as a build tool > ------------------------------ > > Key: FORGE-535 > URL: https://issues.jboss.org/browse/FORGE-535 > Project: Forge > Issue Type: Feature Request > Components: Build Tools - Gradle > Reporter: Lincoln Baxter III > Assignee: Adam Wyłuda > Fix For: 2.x Future > > > Much like the current Maven support. It would be nice if Forge could be used to manipulate Gradle 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

1
0
0 / 0

[JBoss JIRA] (FORGE-707) Forge 2 should support non-CDI addons / service registration via ServiceLoader

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-707?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-707: ---------------------------------- Component/s: Container > Forge 2 should support non-CDI addons / service registration via ServiceLoader > ------------------------------------------------------------------------------ > > Key: FORGE-707 > URL: https://issues.jboss.org/browse/FORGE-707 > Project: Forge > Issue Type: Feature Request > Components: Container > 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

1
0
0 / 0

[JBoss JIRA] (FORGE-773) entities for scaffold could be binary, not source

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-773?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-773: ---------------------------------- Component/s: Parsers / File Manipulation Scaffold > entities for scaffold could be binary, not source > ------------------------------------------------- > > Key: FORGE-773 > URL: https://issues.jboss.org/browse/FORGE-773 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation, Scaffold > Reporter: John Franey > Fix For: 1.x Future > > > I have already a jar file full of JPA entity classes, built by another project. To generate scaffold on forge 1.2.1, I create a forge project and unpack the source code of the jpa project into the forge project, then I can run the scaffold. > I'd like a parameter to accept a dependency and a package or class name: scaffold from-entity [groupId:artifactId:]entity-name > if groupId:artifactId were provided, then the plugin would find that dependency, open that jar and look for the class(es) with that name, convert those to JavaClass implementation that wraps a java.lang.Class and call the scaffold provider. > FacesScaffold facet operates on JavaClass. Thanks to architects that made this an interface, its not hard to implement as a wrapper to java.lang.Class; same for other interfaces in forge's java api. In other words, using these wrappers, FacesScaffold can operate on java class data. > However, there seem to be a few roadblocks for me: > # The ScaffoldPlugin can accept a JavaResource, a source file. There is no method on the plugin to accept a JavaClass Is it possible to override, perhaps by defining a brand new plugin that derives from ScaffoldPlugin and provides the method that accepts a JavaClass? > # The ShellImpl has a fixed conversion from string to JavaResource. Is it possible to provide a custom conversion in order for the shell to call a plugin method with a JavaCLass parameter? > # The Dependency facet does not have a method that gives access to the jar file of the dependency. I'm not confident that getSystemPath() returns the path to the actual jar file. This data derives from the apache Maven's method Dependency.getSystemPath() which has a javadoc saying: "don't call this method." I think Eclipse and maven have different dependency resolution mechanisms, so this facet would be different in each. > Have I read the forge code wrong? Is there a roadmap that navigates these issues? -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-554) Tab AutoCompletion in forge ignores already typed options

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-554?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-554: ---------------------------------- Component/s: UI - Shell Usability Windows > Tab AutoCompletion in forge ignores already typed options > --------------------------------------------------------- > > Key: FORGE-554 > URL: https://issues.jboss.org/browse/FORGE-554 > Project: Forge > Issue Type: Bug > Components: UI - Shell, Usability, Windows > Environment: Windows 7 64bits > Reporter: George Gastaldi > Fix For: 1.x Future > > > Inside a project, when you "cd" and press <TAB> to navigate between nested folders, the prompt resets to "cd" only, losing the folders previously selected when typing. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-690) field relationship manytomany doesn't support join tables

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-690?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-690. --------------------------------- Fix Version/s: (was: 1.x Future) Resolution: Duplicate Issue Duplicate of FORGE-691 > field relationship manytomany doesn't support join tables > --------------------------------------------------------- > > Key: FORGE-690 > URL: https://issues.jboss.org/browse/FORGE-690 > Project: Forge > Issue Type: Feature Request > Reporter: Kevin Hooke > > Using field with a relationship type of manytomany does not give the option to add JPA mappings using a join table. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-691) scaffolding does not support entities using a manytomany relationship with a join table

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-691?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-691: ---------------------------------- Component/s: Scaffold > scaffolding does not support entities using a manytomany relationship with a join table > --------------------------------------------------------------------------------------- > > Key: FORGE-691 > URL: https://issues.jboss.org/browse/FORGE-691 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Reporter: Kevin Hooke > Fix For: 1.x Future > > > using field with a relationship type of manytomany does not give the option to generate the relationship using a join table. If you map this relationship by hand with JPA annotations using oneToMany from either side to an association entity, Forge scaffolding does not know how to generate view pages to handle creation of the relationship. It currently attempts to populate a list to allow the user to select an instance of the association class, which doesn't make any sense. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-693) Need an auto-update feature for plugins

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-693?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-693: ---------------------------------- Component/s: Builtin Plugins > Need an auto-update feature for plugins > --------------------------------------- > > Key: FORGE-693 > URL: https://issues.jboss.org/browse/FORGE-693 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Reporter: George Gastaldi > Fix For: 1.x Future > > > FORGE-217 auto-updates the core and the core plugins. There should be a way to update the current installed plugins. > Depending on the time taken to check, this could be done in the Forge startup. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-781) forge install-plugin command fails with cygwin

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-781?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-781: ---------------------------------- Component/s: Windows > forge install-plugin command fails with cygwin > ----------------------------------------------- > > Key: FORGE-781 > URL: https://issues.jboss.org/browse/FORGE-781 > Project: Forge > Issue Type: Bug > Components: Init Scripts, Windows > Affects Versions: 1.1.2.Final, 1.1.3.Final, 1.2.0.Final > Environment: cygwin > Reporter: Andreas Karalus > Fix For: 1.x Future > > > @See: https://community.jboss.org/message/797250 > forge install-plugin <plugin> command fails if it is called from cygwin. > I tried this with different forge versions (1.1.2, 1.1.3, 1.2.0) and different plugins (jboss-as-7, richfaces) > I think the problem relies in the path resolution for loading modules with cygwin. This path ist not present: C:\cygwin\home\297646\.forge\plugins > {code} > roots: D:\Programme\forge-distribution-1.2.0.Final\modules,C:\cygwin\home\297646\.forge\plugins,D:\workspaces\forge-jbossas-quickstart\ > {code} > The .forge folder is installed under: C:\Users\297646\.forge\plugin (even if forge was called from cygwin first time). > {code} > 297646@TB01448C ~/workspaces/forge-jbossas-quickstart > # forge > Failed loading: org.richfaces.forge.richfaces-forge-plugin:1.0.5.Final:1.0.0-SNAPSHOT-d292c53d-b7ad-41b8-800e-8c2b4ea1475b > org.jboss.modules.ModuleNotFoundException: Module org.richfaces.forge.richfaces-forge-plugin:1.0.0-SNAPSHOT-d292c53d-b7ad-41b8-800e-8c2b4ea1475b is not found in local module loader @2fcac6db (roots: D:\Programme\forge-distribution-1.2.0.Final\modules,C:\cygwin\home\297646\.forge\plugins,D:\workspaces\forge-jbossas-quickstart\.) > at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126) > at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) > at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) > at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:204) > at org.jboss.forge.shell.Bootstrap.loadPlugins(Bootstrap.java:254) > at org.jboss.forge.shell.Bootstrap.access$200(Bootstrap.java:38) > at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:125) > at java.lang.Thread.run(Thread.java:662) > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 1.2.0.Final ] - JBoss, by Red Hat, Inc. [ http://jboss.org/forge ] > [jboss-as-quickstarts-parent] forge-jbossas-quickstart $ > {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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2013