August 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-97) Invoking commands using minus sign seems to break "run" plugin

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-97?page=com.atlassian.jira.plugin.s... ] George Gastaldi reassigned FORGE-97: ------------------------------------ Assignee: George Gastaldi > Invoking commands using minus sign seems to break "run" plugin > -------------------------------------------------------------- > > Key: FORGE-97 > URL: https://issues.jboss.org/browse/FORGE-97 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > > {code} > [no project] JAX $ > [no project] JAX $ run forge-conftrack-demo.fsh > ***ERROR*** Exception encountered: [Error: illegal function name or use of reserved word] > [Near : {... -demo_fsh_1064826090() {currentStep = 1;v = SHELL. ....}] > ^ > [Line: 1, Column: 39] (type "set VERBOSE true" to enable stack traces) > [no project] JAX $ run demo.fsh > ? Start at which step? > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-562) Display Forge version on startup

by George Gastaldi (JIRA)

George Gastaldi created FORGE-562: ------------------------------------- Summary: Display Forge version on startup Key: FORGE-562 URL: https://issues.jboss.org/browse/FORGE-562 Project: Forge Issue Type: Enhancement Reporter: George Gastaldi It would be nice to display the Forge version number. Preferred idea is to display above the logo itself on top of the F[or]ge. To the right of the F, at the top -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
4
0 / 0

[JBoss JIRA] (FORGE-619) bad support of field with the following naming pattern aFIELD

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.... ] Koen Aers commented on FORGE-619: --------------------------------- I believe for now this issue should be in the main Forge project. > bad support of field with the following naming pattern aFIELD > ------------------------------------------------------------- > > Key: FORGE-619 > URL: https://issues.jboss.org/browse/FORGE-619 > Project: Forge > Issue Type: Bug > Reporter: Anthony Patricio > > Step to reproduce the issue, create an entity from forge with a field named aFIELD > Check the get/set generated method, > As per the javabean naming convention, we should have getaFIELD,setaFIELD but we have getAFIELD setAFIELD. > When generated by eclipse then scaffolding, problem can appear, more important if the id is following the same naming pattern. > Richard fixed almost everything related to meta widget. > However the ForgePropertyStyle still needs some polishing. > Check the forum reference. > Cheers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-619) bad support of field with the following naming pattern aFIELD

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.... ] Koen Aers moved FORGEPLUGINS-45 to FORGE-619: --------------------------------------------- Project: Forge (was: Forge Plugins) Key: FORGE-619 (was: FORGEPLUGINS-45) > bad support of field with the following naming pattern aFIELD > ------------------------------------------------------------- > > Key: FORGE-619 > URL: https://issues.jboss.org/browse/FORGE-619 > Project: Forge > Issue Type: Bug > Reporter: Anthony Patricio > > Step to reproduce the issue, create an entity from forge with a field named aFIELD > Check the get/set generated method, > As per the javabean naming convention, we should have getaFIELD,setaFIELD but we have getAFIELD setAFIELD. > When generated by eclipse then scaffolding, problem can appear, more important if the id is following the same naming pattern. > Richard fixed almost everything related to meta widget. > However the ForgePropertyStyle still needs some polishing. > Check the forum reference. > Cheers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2) 'mv' command does not function on directories

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2?page=com.atlassian.jira.plugin.sy... ] George Gastaldi resolved FORGE-2. --------------------------------- Fix Version/s: 1.0.6.Final Resolution: Done Fixed by José Donizetti > 'mv' command does not function on directories > --------------------------------------------- > > Key: FORGE-2 > URL: https://issues.jboss.org/browse/FORGE-2 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha2 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Labels: Starter > Fix For: 1.0.6.Final > > > [forge-distribution] dist $ cd ~/Projects/ > [no project] Projects $ mv > jline/ gshell/ plugin-prettyfaces/ seam-render/ > gcode-issue-import/ prettyfaces/ viPlugin.license shrinkwrap-descriptors/ > maven-debug/ fpak/ javarebel.lic eclipse-code-formatter-profile.xml > forge/ > [no project] Projects $ mv > [source (of type org.jboss.seam.forge.resources.Resource)] > jline/ gshell/ plugin-prettyfaces/ seam-render/ > gcode-issue-import/ prettyfaces/ viPlugin.license shrinkwrap-descriptors/ > maven-debug/ fpak/ javarebel.lic eclipse-code-formatter-profile.xml > forge/ > [no project] Projects $ mv plugin-prettyfaces/ > [target (of type java.lang.String)] > [no project] Projects $ mv plugin-prettyfaces/ prettyfaces/forge-plugin > ***ERROR*** [mv] [UnknownFileResource] can have no children > [no project] Projects $ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2) 'mv' command does not function on directories

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2?page=com.atlassian.jira.plugin.sy... ] George Gastaldi reassigned FORGE-2: ----------------------------------- Assignee: George Gastaldi > 'mv' command does not function on directories > --------------------------------------------- > > Key: FORGE-2 > URL: https://issues.jboss.org/browse/FORGE-2 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha2 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Labels: Starter > > [forge-distribution] dist $ cd ~/Projects/ > [no project] Projects $ mv > jline/ gshell/ plugin-prettyfaces/ seam-render/ > gcode-issue-import/ prettyfaces/ viPlugin.license shrinkwrap-descriptors/ > maven-debug/ fpak/ javarebel.lic eclipse-code-formatter-profile.xml > forge/ > [no project] Projects $ mv > [source (of type org.jboss.seam.forge.resources.Resource)] > jline/ gshell/ plugin-prettyfaces/ seam-render/ > gcode-issue-import/ prettyfaces/ viPlugin.license shrinkwrap-descriptors/ > maven-debug/ fpak/ javarebel.lic eclipse-code-formatter-profile.xml > forge/ > [no project] Projects $ mv plugin-prettyfaces/ > [target (of type java.lang.String)] > [no project] Projects $ mv plugin-prettyfaces/ prettyfaces/forge-plugin > ***ERROR*** [mv] [UnknownFileResource] can have no children > [no project] Projects $ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2012