June 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-791) Forge auto complete in windows doesn't display command until after I forge again

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-791?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-791: ---------------------------------- Component/s: Usability Windows > Forge auto complete in windows doesn't display command until after I forge again > -------------------------------------------------------------------------------- > > Key: FORGE-791 > URL: https://issues.jboss.org/browse/FORGE-791 > Project: Forge > Issue Type: Bug > Components: Usability, Windows > Reporter: John Ament > Fix For: 1.x Future > > > If I attempt to type in "sp" then tab, the screen fills with some blanks, then tells me the command was not filled in properly. So it identified the command I wanted, but didn't show it on the screen. > [ooph] ooph $ sp ^C > spartajs.io > ***ERROR*** [spartajs.io] Missing command for plugin [spartajs.io], available commands: [addRestResource, addJackson, remove, setup, add, javascriptModel] > [ooph] ooph $ > [ooph] ooph $ forge > _____ > | ___|__ _ __ __ _ ___ > | |_ / _ \| `__/ _` |/ _ \ \\ > | _| (_) | | | (_| | __/ // > |_| \___/|_| \__, |\___| > |___/ > JBoss Forge, version [ 1.2.1.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ] > After hitting forge again it does auto complete properly. -- 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-848) Forge should support a @CommandScoped annotation

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-848?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-848: ---------------------------------- Component/s: Container > Forge should support a @CommandScoped annotation > ------------------------------------------------ > > Key: FORGE-848 > URL: https://issues.jboss.org/browse/FORGE-848 > Project: Forge > Issue Type: Feature Request > Components: Container > Reporter: Vineet Reynolds > Fix For: 1.x Future > > > Forge should support a {{@CommandScoped}} just like the {{@ProjectScoped}} annotation. {{@CommandScoped}} objects would have a shorter lifetime since their lifecycle would be constrained to the execution of a command. This is equivalent to {{@RequestScoped}} instances, so we could renamed {{@CommandScoped}} to {{@RequestScoped}} if appropriate. > Options passed to the Forge plugins could be made available via this scope. Not a binding requirement, since ambiguous dependencies could be encountered when injecting into managed beans. -- 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-848) Forge should support a @CommandScoped annotation

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-848?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-848: ---------------------------------- Component/s: Plugin API > Forge should support a @CommandScoped annotation > ------------------------------------------------ > > Key: FORGE-848 > URL: https://issues.jboss.org/browse/FORGE-848 > Project: Forge > Issue Type: Feature Request > Components: Container, Plugin API > Reporter: Vineet Reynolds > Fix For: 1.x Future > > > Forge should support a {{@CommandScoped}} just like the {{@ProjectScoped}} annotation. {{@CommandScoped}} objects would have a shorter lifetime since their lifecycle would be constrained to the execution of a command. This is equivalent to {{@RequestScoped}} instances, so we could renamed {{@CommandScoped}} to {{@RequestScoped}} if appropriate. > Options passed to the Forge plugins could be made available via this scope. Not a binding requirement, since ambiguous dependencies could be encountered when injecting into managed beans. -- 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-825) Provide a JPQL query builder API to make it easier for plugins to generate JPQL queries

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-825?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-825: ---------------------------------- Component/s: Brainstorming > Provide a JPQL query builder API to make it easier for plugins to generate JPQL queries > --------------------------------------------------------------------------------------- > > Key: FORGE-825 > URL: https://issues.jboss.org/browse/FORGE-825 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming > Reporter: Vineet Reynolds > Fix For: 1.x Future > > > Coming in from the FORGE-813 issue, I believe it would be beneficial to have an API that would allow plugin developers to generate JPQL queries based on JavaClass instances provided to it. > It is akin to the JPA metamodel, except that the model here is based on Forge JavaClass instances. -- 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: Init Scripts > 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 > 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

[JBoss JIRA] (FORGE-852) RSS based news mechanism

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-852?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-852: ---------------------------------- Component/s: Builtin Plugins Usability > RSS based news mechanism > ------------------------ > > Key: FORGE-852 > URL: https://issues.jboss.org/browse/FORGE-852 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Usability > Affects Versions: 1.2.2.Final > Reporter: Michal Matloka > Fix For: 1.x Future > > > On Forge startup user could see a message e.g. taken from Forge RSS. This could help in such situations like this: http://forge.jboss.org/news/2013/04/08/forge-update.html > Possible workflow: > run forge -> request to rss/sth -> retrieved important messages -> show to user in e.g. console > Console is a starting point. It possibly could be developed into a more generic mechanism which could be used under different interfaces. -- 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-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-875: ---------------------------------- Component/s: Scaffold UI - Eclipse > the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml > ------------------------------------------------------------------------------ > > Key: FORGE-875 > URL: https://issues.jboss.org/browse/FORGE-875 > Project: Forge > Issue Type: Bug > Components: Scaffold, UI - Eclipse > Affects Versions: 1.2.2.Final > Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3 > Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1 > Reporter: Randy Thomas > Assignee: Koen Aers > Priority: Critical > Labels: forge > Fix For: 1.x Future > > > I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine. > The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database. > I was able to resolve the problem by adding the following lines to the script: > @/* Add beans.xml for CDI */; > touch src/main/webapp/WEB-INF/beans.xml > Lincoln indicated that this should have already been done by the > `scaffold setup --scaffoldType faces;` command. -- 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-779) Class parameters are not correctly loaded for the consuming addon's classloader

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-779?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-779: ---------------------------------- Component/s: Container > Class parameters are not correctly loaded for the consuming addon's classloader > ------------------------------------------------------------------------------- > > Key: FORGE-779 > URL: https://issues.jboss.org/browse/FORGE-779 > Project: Forge > Issue Type: Bug > Components: Container > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Critical > Fix For: 2.x Future > > > Having the following scenario: > Eclipse plugin -> calls ConverterFactory -> passes Resource.class as a parameter > {code:java} > ConverterFactory.getConverter(File.class, Resource.class) > {code} > in ResourceConverterGenerator (resources addon): > {code:java} > @Override > public boolean handles(Class<?> source, Class<?> target) > { > return Resource.class.isAssignableFrom(target); > } > {code} > Returns false, because the classloader that loaded the Resource class is the Eclipse classloader, not the Resource addon classloader AND Resource.class is not visible in the convert addon. -- 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-942) CommandHistory / Doskey display is not working in Windows.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-942?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-942: ---------------------------------- Fix Version/s: 1.x Future > CommandHistory / Doskey display is not working in Windows. > ---------------------------------------------------------- > > Key: FORGE-942 > URL: https://issues.jboss.org/browse/FORGE-942 > Project: Forge > Issue Type: Bug > Components: Windows > Affects Versions: 1.3.0.Final > Environment: Windows XP, java version "1.7.0_21", Forge 1.3.0-Final > Reporter: Rajmahendra Hegde > Fix For: 1.x Future > > > When I try to use Forege in command prompt in Windows, After executing couple of forge commands and try to use arrow key Up and Down. I cant see the command history. -- 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-949) Validation plugin generates incorrect validation.xml entries for EAP 6.1

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-949?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-949: ---------------------------------- Fix Version/s: 1.x Future > Validation plugin generates incorrect validation.xml entries for EAP 6.1 > ------------------------------------------------------------------------ > > Key: FORGE-949 > URL: https://issues.jboss.org/browse/FORGE-949 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.3.0.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 1.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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues June 2013