August 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-615) Add Forge exceptions to Eclipse Error Log view

by George Gastaldi (JIRA)

George Gastaldi created FORGE-615: ------------------------------------- Summary: Add Forge exceptions to Eclipse Error Log view Key: FORGE-615 URL: https://issues.jboss.org/browse/FORGE-615 Project: Forge Issue Type: Enhancement Components: JBoss Tools Integration Reporter: George Gastaldi Assignee: Koen Aers Every exception thrown during Forge execution should appear on the Error Log view in Eclipse -- 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

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] (FORGE-618) unix touch comand

by Jose Donizetti Brito Junior (JIRA)

Jose Donizetti Brito Junior created FORGE-618: ------------------------------------------------- Summary: unix touch comand Key: FORGE-618 URL: https://issues.jboss.org/browse/FORGE-618 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Reporter: Jose Donizetti Brito Junior Priority: Minor implement the touch command -- 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

13 years, 8 months

3
3
0 / 0

[JBoss JIRA] (FORGE-616) Automatically attempt to install a missing plugin if not found on current installation

by George Gastaldi (JIRA)

George Gastaldi created FORGE-616: ------------------------------------- Summary: Automatically attempt to install a missing plugin if not found on current installation Key: FORGE-616 URL: https://issues.jboss.org/browse/FORGE-616 Project: Forge Issue Type: Enhancement Reporter: George Gastaldi If would be nice if when you type a plugin that is not installed on a forge installation, Forge could search through the available plugins and install them automatically. Also, if a command is invalid, maybe the user could have typed wrong, so, it would be nice to display a message like "Did you mean this?" and list the possible options. -- 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

13 years, 8 months

2
7
0 / 0

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

by Richard Kennard (JIRA)

[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.... ] Richard Kennard commented on FORGE-619: --------------------------------------- Thanks Lincoln. Note there is another part to this issue that needs your attention. See the reference forum thread, re: 'forge is still generated broken get/set method names when using its entity command line' > 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 > Assignee: Richard Kennard > > 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

13 years, 9 months

1
0
0 / 0

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reassigned FORGE-619: ---------------------------------------- Assignee: Richard Kennard Thanks, Richard! > 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 > Assignee: Richard Kennard > > 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

13 years, 9 months

1
0
0 / 0

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

by Richard Kennard (JIRA)

[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.... ] Richard Kennard updated FORGE-619: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/184 Fix attached > 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-577) Minimal GitUndo plugin

by Jevgeni Zelenkov (JIRA)

Jevgeni Zelenkov created FORGE-577: -------------------------------------- Summary: Minimal GitUndo plugin Key: FORGE-577 URL: https://issues.jboss.org/browse/FORGE-577 Project: Forge Issue Type: Sub-task Components: Plugin Repository Reporter: Jevgeni Zelenkov Assignee: Jevgeni Zelenkov Priority: Minor First alpha version of the UndoPlugin. Should provide the following functionality: * installation of the plugin * list contents of the history branch * ResouceEvent listener which adds changes to the history branch Git features required for that functionality to materialize, will be added with this commit. -- 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

13 years, 9 months

3
3
0 / 0

[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 updated FORGE-97: --------------------------------- Fix Version/s: 1.0.6.Final Description: {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} was: {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} > 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 > Fix For: 1.0.6.Final > > > {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

13 years, 9 months

1
0
0 / 0

[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 closed FORGE-97. -------------------------------- > 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 > Fix For: 1.0.6.Final > > > {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

13 years, 9 months

1
0
0 / 0

[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 resolved FORGE-97. ---------------------------------- Resolution: Done > 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

13 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2012