October 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2067) The java-new-field generates getters/setters even if --generateGetter and --generateSetter are set to false

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2067?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-2067: -------------------------------------- Assignee: Ståle Pedersen > The java-new-field generates getters/setters even if --generateGetter and --generateSetter are set to false > ----------------------------------------------------------------------------------------------------------- > > Key: FORGE-2067 > URL: https://issues.jboss.org/browse/FORGE-2067 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Assignee: Ståle Pedersen > Fix For: 2.x Future > > > No matter if you set {{generateGetter}} or {{generateSetter}} to true or false, get/set are always generated. The following commands generate get/set (which is normal) : > {code} > java-new-class --named DatabaseProducer ; > java-new-field --named em --type javax.persistence.EntityManager ; > {code} > But the following command should not generate get/set : > {code} > java-new-class --named DatabaseProducer ; > java-new-field --named em --type javax.persistence.EntityManager --generateGetter false --generateSetter false ; > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2067) The java-new-field generates getters/setters even if --generateGetter and --generateSetter are set to false

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2067?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-2067: ------------------------------------------- The issue here is something to do with Aesh syntax: this fails, get/set are created —> {code} java-new-field --named field4 --generateGetter false --generateSetter false {code} this succeeds, get/set are NOT created —> {code} java-new-field --named field4 --generateGetter=false --generateSetter=false {code} > The java-new-field generates getters/setters even if --generateGetter and --generateSetter are set to false > ----------------------------------------------------------------------------------------------------------- > > Key: FORGE-2067 > URL: https://issues.jboss.org/browse/FORGE-2067 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > No matter if you set {{generateGetter}} or {{generateSetter}} to true or false, get/set are always generated. The following commands generate get/set (which is normal) : > {code} > java-new-class --named DatabaseProducer ; > java-new-field --named em --type javax.persistence.EntityManager ; > {code} > But the following command should not generate get/set : > {code} > java-new-class --named DatabaseProducer ; > java-new-field --named em --type javax.persistence.EntityManager --generateGetter false --generateSetter false ; > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2067) The java-new-field generates getters/setters even if --generateGetter and --generateSetter are set to false

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-2067?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-2067: ------------------------------------------- So it looks like boolean values are not properly being set when using the standard syntax > The java-new-field generates getters/setters even if --generateGetter and --generateSetter are set to false > ----------------------------------------------------------------------------------------------------------- > > Key: FORGE-2067 > URL: https://issues.jboss.org/browse/FORGE-2067 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Assignee: Ståle Pedersen > Fix For: 2.x Future > > > No matter if you set {{generateGetter}} or {{generateSetter}} to true or false, get/set are always generated. The following commands generate get/set (which is normal) : > {code} > java-new-class --named DatabaseProducer ; > java-new-field --named em --type javax.persistence.EntityManager ; > {code} > But the following command should not generate get/set : > {code} > java-new-class --named DatabaseProducer ; > java-new-field --named em --type javax.persistence.EntityManager --generateGetter false --generateSetter false ; > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2067) The java-new-field generates getters/setters even if --generateGetter and --generateSetter are set to false

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2067?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2067: ------------------------------------- Description: No matter if you set {{generateGetter}} or {{generateSetter}} to true or false, get/set are always generated. The following commands generate get/set (which is normal) : {code} java-new-class --named DatabaseProducer ; java-new-field --named em --type javax.persistence.EntityManager ; {code} But the following command should not generate get/set : {code} java-new-class --named DatabaseProducer ; java-new-field --named em --type javax.persistence.EntityManager --generateGetter false --generateSetter false ; {code} was: No matter if you set {{--generateGetter}} or {{--generateSetter}} to true or false, get/set are always generated. The following commands generate get/set (which is normal) : {code} java-new-class --named DatabaseProducer ; java-new-field --named em --type javax.persistence.EntityManager ; {code} But the following command should not generate get/set : {code} java-new-class --named DatabaseProducer ; java-new-field --named em --type javax.persistence.EntityManager --generateGetter false --generateSetter false ; {code} > The java-new-field generates getters/setters even if --generateGetter and --generateSetter are set to false > ----------------------------------------------------------------------------------------------------------- > > Key: FORGE-2067 > URL: https://issues.jboss.org/browse/FORGE-2067 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > No matter if you set {{generateGetter}} or {{generateSetter}} to true or false, get/set are always generated. The following commands generate get/set (which is normal) : > {code} > java-new-class --named DatabaseProducer ; > java-new-field --named em --type javax.persistence.EntityManager ; > {code} > But the following command should not generate get/set : > {code} > java-new-class --named DatabaseProducer ; > java-new-field --named em --type javax.persistence.EntityManager --generateGetter false --generateSetter false ; > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2068) When creating a new field, updating toString should be optional

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2068?page=com.atlassian.jira.plugin... ] Antonio Goncalves reassigned FORGE-2068: ---------------------------------------- Assignee: Antonio Goncalves > When creating a new field, updating toString should be optional > --------------------------------------------------------------- > > Key: FORGE-2068 > URL: https://issues.jboss.org/browse/FORGE-2068 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.x Future > > > Today, when we create a new field to a Java class (or CDI bean...), the field is automatically added to the {{toString}} method. It would be good to have the option not to update it, by adding a {{--updateToString}} boolean parameter. > The following command create a class, adds two fields, one updating the toString, the other no : > {code} > java-new-class --named MyClass > java-new-field --named defaultUpdatesToString > java-new-field --named doesNotUpdateToString --updateToString false > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2068) When creating a new field, updating toString should be optional

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2068?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2068: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/516 > When creating a new field, updating toString should be optional > --------------------------------------------------------------- > > Key: FORGE-2068 > URL: https://issues.jboss.org/browse/FORGE-2068 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Today, when we create a new field to a Java class (or CDI bean...), the field is automatically added to the {{toString}} method. It would be good to have the option not to update it, by adding a {{--updateToString}} boolean parameter. > The following command create a class, adds two fields, one updating the toString, the other no : > {code} > java-new-class --named MyClass > java-new-field --named defaultUpdatesToString > java-new-field --named doesNotUpdateToString --updateToString false > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2065) CDI commands should have implicit setup

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2065?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2065: ------------------------------------- Parent: FORGE-1926 Issue Type: Sub-task (was: Enhancement) > CDI commands should have implicit setup > --------------------------------------- > > Key: FORGE-2065 > URL: https://issues.jboss.org/browse/FORGE-2065 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.x Future > > > The following CDI commands still need an explicit {{cdi-setup}}, otherwise they won't work : > {code} > cdi-new-bean > cdi-new-qualifier > cdi-new-scope > cdi-new-stereotype > {code} > They need to implement {{PrerequisiteCommandsProvider}} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2068) When creating a new field, updating toString should be optional

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2068?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2068: ------------------------------------- Parent: FORGE-1926 Issue Type: Sub-task (was: Enhancement) > When creating a new field, updating toString should be optional > --------------------------------------------------------------- > > Key: FORGE-2068 > URL: https://issues.jboss.org/browse/FORGE-2068 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Today, when we create a new field to a Java class (or CDI bean...), the field is automatically added to the {{toString}} method. It would be good to have the option not to update it, by adding a {{--updateToString}} boolean parameter. > The following command create a class, adds two fields, one updating the toString, the other no : > {code} > java-new-class --named MyClass > java-new-field --named defaultUpdatesToString > java-new-field --named doesNotUpdateToString --updateToString false > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2068) When creating a new field, updating toString should be optional

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2068: ---------------------------------------- Summary: When creating a new field, updating toString should be optional Key: FORGE-2068 URL: https://issues.jboss.org/browse/FORGE-2068 Project: Forge Issue Type: Enhancement Components: Java EE Affects Versions: 2.12.0.Final Reporter: Antonio Goncalves Fix For: 2.x Future Today, when we create a new field to a Java class (or CDI bean...), the field is automatically added to the {{toString}} method. It would be good to have the option not to update it, by adding a {{--updateToString}} boolean parameter. The following command create a class, adds two fields, one updating the toString, the other no : {code} java-new-class --named MyClass java-new-field --named defaultUpdatesToString java-new-field --named doesNotUpdateToString --updateToString false {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2066) In jta-setup version should be renamed to jtaVersion

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2066?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2066: ------------------------------------- Parent: FORGE-1926 Issue Type: Sub-task (was: Enhancement) > In jta-setup version should be renamed to jtaVersion > ---------------------------------------------------- > > Key: FORGE-2066 > URL: https://issues.jboss.org/browse/FORGE-2066 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Assignee: Antonio Goncalves > Fix For: 2.x Future > > > In all the {{setup}} commands, the {{version}} is always prefixed by the specification, except in JTA : > {code} > jpa-setup --jpaVersion > cdi-setup --cdiVersion > websocket-setup --webSocketVersion > ejb-setup --ejbVersion > faces-setup --facesVersion > jms-setup --jmsVersion > jstl-setup --jstlVersion > servlet-setup --servletVersion > rest-setup --jaxrsVersion > soap-setup --jaxwsVersion > {code} > JTA uses : > {code} > jta-setup --version > {code} > And should be renamed > {code} > jta-setup --jtaVersion > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2014