[forge-issues] [JBoss JIRA] (FORGE-2067) The java-new-field generates getters/setters even if --generateGetter and --generateSetter are set to false
[
https://issues.jboss.org/browse/FORGE-2067?page=com.atlassian.jira.plugin...
]
Ståle Pedersen commented on FORGE-2067:
---------------------------------------
after a quick look its seems that forge is specifying if a field should have a value or
not in æsh here;
https://github.com/forge/core/blob/master/shell/impl/src/main/java/org/jb...
(i might be wrong, but it looks like it)
so either we can add another field called hasValue (or something) to WithAttributes where
you can override the default behaviour thats currently in CommandLineUtil, or you can
change the default behaviour.
[~lincolnthree] [~gastaldi] wdyt?
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)