January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1254) calling setStatic(true) on a static method add keyword "static" twice

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1254?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1254: ----------------------------------- Fix Version/s: 1.4.4.Final > calling setStatic(true) on a static method add keyword "static" twice > --------------------------------------------------------------------- > > Key: FORGE-1254 > URL: https://issues.jboss.org/browse/FORGE-1254 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 1.4.1.Final > Reporter: Michael Schwartz > Assignee: Salem Elrahal > Priority: Minor > Fix For: 1.4.4.Final, 2.0.0.CR1 > > > Testclass: > {code:java} > class Tester() { > static void testit() { > } > } > {code} > Forge: > {code:java} > Method<?> method = entityclass.getMethod("testit"); > method.setStatic(true); > // save the class > {code} > yields to: > {code} > static static void testit() {} > {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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1254) calling setStatic(true) on a static method add keyword "static" twice

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1254?page=com.atlassian.jira.plugin... ] George Gastaldi reopened FORGE-1254: ------------------------------------ > calling setStatic(true) on a static method add keyword "static" twice > --------------------------------------------------------------------- > > Key: FORGE-1254 > URL: https://issues.jboss.org/browse/FORGE-1254 > Project: Forge > Issue Type: Bug > Components: Parsers / File Manipulation > Affects Versions: 1.4.1.Final > Reporter: Michael Schwartz > Assignee: Salem Elrahal > Priority: Minor > Fix For: 2.0.0.CR1 > > > Testclass: > {code:java} > class Tester() { > static void testit() { > } > } > {code} > Forge: > {code:java} > Method<?> method = entityclass.getMethod("testit"); > method.setStatic(true); > // save the class > {code} > yields to: > {code} > static static void testit() {} > {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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1448) Cannot cd an Entity with TAB completion

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1448?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1448: ------------------------------------- Summary: Cannot cd an Entity with TAB completion (was: Cannot cd an with TAB completion) > Cannot cd an Entity with TAB completion > --------------------------------------- > > Key: FORGE-1448 > URL: https://issues.jboss.org/browse/FORGE-1448 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > When I create 2 entities, I can {{cd}} from on to another if I specify the class, but it doesn't work with TAB completion : > {code} > [Speaker.java]$ cd ../Talk.java > [Talk.java]$ cd ../Speaker.java > [Speaker.java]$ cd ../T TAB > {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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1448) Cannot cd an with TAB completion

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1448: ---------------------------------------- Summary: Cannot cd an with TAB completion Key: FORGE-1448 URL: https://issues.jboss.org/browse/FORGE-1448 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.Beta4 Reporter: Antonio Goncalves Fix For: 2.x Future When I create 2 entities, I can {{cd}} from on to another if I specify the class, but it doesn't work with TAB completion : {code} [Speaker.java]$ cd ../Talk.java [Talk.java]$ cd ../Speaker.java [Speaker.java]$ cd ../T TAB {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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1394) Rename bean-validation-setup command

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1394?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1394. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.CR1 (was: 2.x Future) Resolution: Done > Rename bean-validation-setup command > ------------------------------------ > > Key: FORGE-1394 > URL: https://issues.jboss.org/browse/FORGE-1394 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.0.CR1 > > > At the moment, {{setup}} commands are related to the core technology : > {code} > faces-new-converter faces-new-validator faces-new-validator-method faces-setup > jpa-new-entity jpa-new-field jpa-setup > {code} > For Bean Validation, there is a {{bean-validation-setup}} command. But, shouldn't it be {{constraint-setup}} ? Also see [FORGE-1393]. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1394) Rename bean-validation-setup command

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1394?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1394: ------------------------------------------ The command has been renamed {{validation-setup}} while the command to add a constraint is {{constraint-add}}. To make all the constraint command look the same, it should be renamed {{constraint-setup}} > Rename bean-validation-setup command > ------------------------------------ > > Key: FORGE-1394 > URL: https://issues.jboss.org/browse/FORGE-1394 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > At the moment, {{setup}} commands are related to the core technology : > {code} > faces-new-converter faces-new-validator faces-new-validator-method faces-setup > jpa-new-entity jpa-new-field jpa-setup > {code} > For Bean Validation, there is a {{bean-validation-setup}} command. But, shouldn't it be {{constraint-setup}} ? Also see [FORGE-1393]. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1447) Rename bean-validation-add-constraint

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1447?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1447. ---------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Duplicate Issue Duplicate of FORGE-1393 > Rename bean-validation-add-constraint > ------------------------------------- > > Key: FORGE-1447 > URL: https://issues.jboss.org/browse/FORGE-1447 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > > In [FORGE-1394] there is a proposition of renaming {{bean-validation}} commands into {{constraint}}. It might be clear (e.g. {{NotEmpty}} is not part of Bean Validation but a proprietary Hibernate Validator) and shorter commands. So instead of : > {code} > bean-validation-setup > bean-validation-add-constraint --property room --constraint NotNull > {code} > We should have > {code} > constraint-setup > constraint-add --property room --constraint NotNull > {code} > And to reflect [FORGE-1446] and [FORGE-944] we should have > {code} > constraint-add --named NotNull --onProperty room > {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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1447) Rename bean-validation-add-constraint

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1447: ---------------------------------------- Summary: Rename bean-validation-add-constraint Key: FORGE-1447 URL: https://issues.jboss.org/browse/FORGE-1447 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.Beta4 Reporter: Antonio Goncalves Fix For: 2.x Future In [FORGE-1394] there is a proposition of renaming {{bean-validation}} commands into {{constraint}}. It might be clear (e.g. {{NotEmpty}} is not part of Bean Validation but a proprietary Hibernate Validator) and shorter commands. So instead of : {code} bean-validation-setup bean-validation-add-constraint --property room --constraint NotNull {code} We should have {code} constraint-setup constraint-add --property room --constraint NotNull {code} And to reflect [FORGE-1446] and [FORGE-944] we should have {code} constraint-add --named NotNull --onProperty room {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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1446) bean-validation-add-constraint should be renamed --onProperty

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1446?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1446. ---------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Duplicate Issue This was already fixed in FORGE-1393 > bean-validation-add-constraint should be renamed --onProperty > ------------------------------------------------------------- > > Key: FORGE-1446 > URL: https://issues.jboss.org/browse/FORGE-1446 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Reporter: Antonio Goncalves > > In Forge 1.x to add a constraint on a property we do : > {code} > constraint NotNull --onProperty title > {code} > On Forge 2.Beta the attribute is called {{--property}} instead of {{--onProperty}} (which would make sense with {{--onAccessor}}) : > {code} > [Talk.java]$ bean-validation-add-constraint TAB > --onAccessor --constraint --property > {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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1446) bean-validation-add-constraint should be renamed --onProperty

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1446: ---------------------------------------- Summary: bean-validation-add-constraint should be renamed --onProperty Key: FORGE-1446 URL: https://issues.jboss.org/browse/FORGE-1446 Project: Forge Issue Type: Sub-task Reporter: Antonio Goncalves Fix For: 2.x Future In Forge 1.x to add a constraint on a property we do : {code} constraint NotNull --onProperty title {code} On Forge 2.Beta the attribute is called {{--property}} instead of {{--onProperty}} (which would make sense with {{--onAccessor}}) : {code} [Talk.java]$ bean-validation-add-constraint TAB --onAccessor --constraint --property {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

12 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2014