March 2015 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2282) Upgrade to Furnace 2.15.3.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2282?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2282. ---------------------------------- Resolution: Done > Upgrade to Furnace 2.15.3.Final > ------------------------------- > > Key: FORGE-2282 > URL: https://issues.jboss.org/browse/FORGE-2282 > Project: Forge > Issue Type: Component Upgrade > Components: Furnace (Container) > Affects Versions: 2.15.1.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.15.2.Final > > > This version introduces some utilities in the {{Versions}} class -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2284) Provide a method for updating the user's installation automatically.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2284?page=com.atlassian.jira.plugin... ] George Gastaldi deleted FORGE-2284: ----------------------------------- > Provide a method for updating the user's installation automatically. > -------------------------------------------------------------------- > > Key: FORGE-2284 > URL: https://issues.jboss.org/browse/FORGE-2284 > Project: Forge > Issue Type: Feature Request > Reporter: Matej Briskar > Assignee: Matej Briskar > > This is cloned MIGR-198 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2284) Provide a method for updating the user's installation automatically.

by Matej Briskar (JIRA)

[ https://issues.jboss.org/browse/FORGE-2284?page=com.atlassian.jira.plugin... ] Matej Briskar closed FORGE-2284. -------------------------------- > Provide a method for updating the user's installation automatically. > -------------------------------------------------------------------- > > Key: FORGE-2284 > URL: https://issues.jboss.org/browse/FORGE-2284 > Project: Forge > Issue Type: Feature Request > Reporter: Matej Briskar > Assignee: Matej Briskar > > This is cloned MIGR-198 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2284) Provide a method for updating the user's installation automatically.

by Matej Briskar (JIRA)

Matej Briskar created FORGE-2284: ------------------------------------ Summary: Provide a method for updating the user's installation automatically. Key: FORGE-2284 URL: https://issues.jboss.org/browse/FORGE-2284 Project: Forge Issue Type: Feature Request Reporter: Matej Briskar Assignee: Matej Briskar This is cloned MIGR-198 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2283) Provide a method for updating the user's installation automatically.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2283?page=com.atlassian.jira.plugin... ] George Gastaldi moved MIGR-231 to FORGE-2283: --------------------------------------------- Project: Forge (was: Migration) Key: FORGE-2283 (was: MIGR-231) Workflow: GIT Pull Request workflow (was: CDW v1) > Provide a method for updating the user's installation automatically. > -------------------------------------------------------------------- > > Key: FORGE-2283 > URL: https://issues.jboss.org/browse/FORGE-2283 > Project: Forge > Issue Type: Feature Request > Reporter: George Gastaldi > Assignee: Matej Briskar > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2283) Provide a method for updating the user's installation automatically.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2283?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2283: ----------------------------------- Reporter: Lincoln Baxter III (was: George Gastaldi) > Provide a method for updating the user's installation automatically. > -------------------------------------------------------------------- > > Key: FORGE-2283 > URL: https://issues.jboss.org/browse/FORGE-2283 > Project: Forge > Issue Type: Feature Request > Reporter: Lincoln Baxter III > Assignee: Matej Briskar > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2282) Upgrade to Furnace 2.15.3.Final

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2282: -------------------------------------- Summary: Upgrade to Furnace 2.15.3.Final Key: FORGE-2282 URL: https://issues.jboss.org/browse/FORGE-2282 Project: Forge Issue Type: Component Upgrade Components: Furnace (Container) Affects Versions: 2.15.1.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.15.2.Final This version introduces some utilities in the {{Versions}} class -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2281) toString generation shouldn't take injected fields into account

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2281?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2281: ------------------------------------- Description: Today, when we create an injected field to a class, the toString method takes it into account. For example, the following script generates a Java class, one injected field with no toString (--updateToString=false), and then a second field with a toString: {code} project-new --named test cdi-setup java-new-class --named MyClass java-new-field --named attnoget --generateGetter=false --generateSetter=false --updateToString=false java-add-annotation --annotation javax.inject.Inject --onProperty attnoget // Until this point there is no toString java-new-field --named att // Here the toString is generated with both att and attnoget {code} The generated code generates a toString with both attributes : {code} more MyClass.java package org.test; import javax.inject.Inject; import java.lang.Override; public class MyClass { @Inject private String attnoget; private String att; public String getAtt() { return att; } public void setAtt(String att) { this.att = att; } @Override public String toString() { String result = getClass().getSimpleName() + " "; if (attnoget != null && !attnoget.trim().isEmpty()) result += "attnoget: " + attnoget; if (att != null && !att.trim().isEmpty()) result += ", att: " + att; return result; } } {code} It would be good if the toString generation would be aware of injection field. For example, a field with @Inject, @PersistenceUnit, @PersistenceContext, @EJB, @WebServiceRef would not be taken into account in the toString. Or something easier, the toString generation could use the getters instead of the fields. was: Today, when we create an injected field to a class, the toString method takes it into account. For example, the following script generates a Java class, one injected field with no toString (--updateToString=false), and then a second field with a toString: {code} project-new --named test cdi-setup java-new-class --named MyClass java-new-field --named attnoget --generateGetter=false --generateSetter=false --updateToString=false java-add-annotation --annotation javax.inject.Inject --onProperty attnoget // Until this point there is no toString java-new-field --named att // Here the toString is generated with both att and attnoget {code} The generated code generates a toString with both attributes : {code} more MyClass.java package org.test; import javax.inject.Inject; import java.lang.Override; public class MyClass { @Inject private String attnoget; private String att; public String getAtt() { return att; } public void setAtt(String att) { this.att = att; } @Override public String toString() { String result = getClass().getSimpleName() + " "; if (attnoget != null && !attnoget.trim().isEmpty()) result += "attnoget: " + attnoget; if (att != null && !att.trim().isEmpty()) result += ", att: " + att; return result; } } {code} It would be good if the toString generation would be aware of injection field. For example, a field with @Inject, @PersistenceUnit, @PersistenceContext, @EJB, @WebServiceRef would not be taken into account in the toString > toString generation shouldn't take injected fields into account > --------------------------------------------------------------- > > Key: FORGE-2281 > URL: https://issues.jboss.org/browse/FORGE-2281 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 2.15.1.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Today, when we create an injected field to a class, the toString method takes it into account. For example, the following script generates a Java class, one injected field with no toString (--updateToString=false), and then a second field with a toString: > {code} > project-new --named test > cdi-setup > java-new-class --named MyClass > java-new-field --named attnoget --generateGetter=false --generateSetter=false --updateToString=false > java-add-annotation --annotation javax.inject.Inject --onProperty attnoget > // Until this point there is no toString > java-new-field --named att > // Here the toString is generated with both att and attnoget > {code} > The generated code generates a toString with both attributes : > {code} > more MyClass.java > package org.test; > import javax.inject.Inject; > import java.lang.Override; > public class MyClass > { > @Inject > private String attnoget; > private String att; > public String getAtt() > { > return att; > } > public void setAtt(String att) > { > this.att = att; > } > @Override > public String toString() > { > String result = getClass().getSimpleName() + " "; > if (attnoget != null && !attnoget.trim().isEmpty()) > result += "attnoget: " + attnoget; > if (att != null && !att.trim().isEmpty()) > result += ", att: " + att; > return result; > } > } > {code} > It would be good if the toString generation would be aware of injection field. For example, a field with @Inject, @PersistenceUnit, @PersistenceContext, @EJB, @WebServiceRef would not be taken into account in the toString. > Or something easier, the toString generation could use the getters instead of the fields. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2281) toString generation shouldn't take injected fields into account

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2281?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2281: ------------------------------------- Fix Version/s: 2.x Future > toString generation shouldn't take injected fields into account > --------------------------------------------------------------- > > Key: FORGE-2281 > URL: https://issues.jboss.org/browse/FORGE-2281 > Project: Forge > Issue Type: Enhancement > Components: Java EE > Affects Versions: 2.15.1.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Today, when we create an injected field to a class, the toString method takes it into account. For example, the following script generates a Java class, one injected field with no toString (--updateToString=false), and then a second field with a toString: > {code} > project-new --named test > cdi-setup > java-new-class --named MyClass > java-new-field --named attnoget --generateGetter=false --generateSetter=false --updateToString=false > java-add-annotation --annotation javax.inject.Inject --onProperty attnoget > // Until this point there is no toString > java-new-field --named att > // Here the toString is generated with both att and attnoget > {code} > The generated code generates a toString with both attributes : > {code} > more MyClass.java > package org.test; > import javax.inject.Inject; > import java.lang.Override; > public class MyClass > { > @Inject > private String attnoget; > private String att; > public String getAtt() > { > return att; > } > public void setAtt(String att) > { > this.att = att; > } > @Override > public String toString() > { > String result = getClass().getSimpleName() + " "; > if (attnoget != null && !attnoget.trim().isEmpty()) > result += "attnoget: " + attnoget; > if (att != null && !att.trim().isEmpty()) > result += ", att: " + att; > return result; > } > } > {code} > It would be good if the toString generation would be aware of injection field. For example, a field with @Inject, @PersistenceUnit, @PersistenceContext, @EJB, @WebServiceRef would not be taken into account in the toString -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2281) toString generation shouldn't take injected fields into account

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2281: ---------------------------------------- Summary: toString generation shouldn't take injected fields into account Key: FORGE-2281 URL: https://issues.jboss.org/browse/FORGE-2281 Project: Forge Issue Type: Enhancement Components: Java EE Affects Versions: 2.15.1.Final Reporter: Antonio Goncalves Today, when we create an injected field to a class, the toString method takes it into account. For example, the following script generates a Java class, one injected field with no toString (--updateToString=false), and then a second field with a toString: {code} project-new --named test cdi-setup java-new-class --named MyClass java-new-field --named attnoget --generateGetter=false --generateSetter=false --updateToString=false java-add-annotation --annotation javax.inject.Inject --onProperty attnoget // Until this point there is no toString java-new-field --named att // Here the toString is generated with both att and attnoget {code} The generated code generates a toString with both attributes : {code} more MyClass.java package org.test; import javax.inject.Inject; import java.lang.Override; public class MyClass { @Inject private String attnoget; private String att; public String getAtt() { return att; } public void setAtt(String att) { this.att = att; } @Override public String toString() { String result = getClass().getSimpleName() + " "; if (attnoget != null && !attnoget.trim().isEmpty()) result += "attnoget: " + attnoget; if (att != null && !att.trim().isEmpty()) result += ", att: " + att; return result; } } {code} It would be good if the toString generation would be aware of injection field. For example, a field with @Inject, @PersistenceUnit, @PersistenceContext, @EJB, @WebServiceRef would not be taken into account in the toString -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2015