October 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-2101) jpa-new-field command should have a --nullable attribute

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2101?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-2101: ------------------------------------------ Of course we could even go further : {code} field string --named title --nullable=false --update=true --insertable=false; {code} You will get : {code} @Column(nullable = false, updatable = true, insertable = false) private String title; {code} > jpa-new-field command should have a --nullable attribute > -------------------------------------------------------- > > Key: FORGE-2101 > URL: https://issues.jboss.org/browse/FORGE-2101 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.12.1.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > It would be good to be able to set the nullable attribute of a field on an entity. If you do : > {code} > field string --named title --nullable true; > {code} > You will get : > {code} > @Column(nullable = true) > private String title; > {code} > That's important for DDL generation -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2101) jpa-new-field command should have a --nullable attribute

by Nicolas Challut (JIRA)

[ https://issues.jboss.org/browse/FORGE-2101?page=com.atlassian.jira.plugin... ] Nicolas Challut commented on FORGE-2101: ---------------------------------------- This is probably a silly question ^^ but why nullable and not updatable ? > jpa-new-field command should have a --nullable attribute > -------------------------------------------------------- > > Key: FORGE-2101 > URL: https://issues.jboss.org/browse/FORGE-2101 > Project: Forge > Issue Type: Sub-task > Components: Java EE > Affects Versions: 2.12.1.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > It would be good to be able to set the nullable attribute of a field on an entity. If you do : > {code} > field string --named title --nullable true; > {code} > You will get : > {code} > @Column(nullable = true) > private String title; > {code} > That's important for DDL generation -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2101) jpa-new-field command should have a --nullable attribute

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2101: ---------------------------------------- Summary: jpa-new-field command should have a --nullable attribute Key: FORGE-2101 URL: https://issues.jboss.org/browse/FORGE-2101 Project: Forge Issue Type: Sub-task Components: Java EE Affects Versions: 2.12.1.Final Reporter: Antonio Goncalves Fix For: 2.x Future It would be good to be able to set the nullable attribute of a field on an entity. If you do : {code} field string --named title --nullable true; {code} You will get : {code} @Column(nullable = true) private String title; {code} That's important for DDL generation -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2058) Being able to create fields with generics types

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2058?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2058. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.12.2.Final (was: 2.x Future) Resolution: Done Fixed in Roaster 2.8.3.Final (using SNAPSHOT for now). Make sure to use double-quotes. Eg: {code} java-new-field --named log --type "java.util.List<String>" {code} > Being able to create fields with generics types > ----------------------------------------------- > > Key: FORGE-2058 > URL: https://issues.jboss.org/browse/FORGE-2058 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.12.2.Final > > > At the moment we can add a new field to a Java class : > {code} > java-new-field --named log --type java.util.List > {code} > It would be very useful to be able to add generics. Something like : > {code} > java-new-field --named log --type java.util.List<String> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2100) Upgrade to Roaster 2.8.3.Final

by George Gastaldi (JIRA)

George Gastaldi created FORGE-2100: -------------------------------------- Summary: Upgrade to Roaster 2.8.3.Final Key: FORGE-2100 URL: https://issues.jboss.org/browse/FORGE-2100 Project: Forge Issue Type: Component Upgrade Components: Parsers / File Manipulation Affects Versions: 2.12.1.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.12.2.Final -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-42) Cannot set Generic types on fields

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/ROASTER-42?page=com.atlassian.jira.plugin... ] George Gastaldi closed ROASTER-42. ---------------------------------- Resolution: Done > Cannot set Generic types on fields > ---------------------------------- > > Key: ROASTER-42 > URL: https://issues.jboss.org/browse/ROASTER-42 > Project: Roaster > Issue Type: Bug > Components: JDT > Affects Versions: 2.8.2.Final > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.8.3.Final > > > The following code: > {code} > JavaClassSource javaClass = Roaster.create(JavaClassSource.class); > FieldSource<JavaClassSource> field = javaClass.addField(); > field.setPrivate().setName("email").setType("java.util.List<String>"); > {code} > Throws the following exception > {code} > java.lang.IllegalArgumentException: Invalid identifier : >List<String>< > at org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:199) > at org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:2202) > at org.eclipse.jdt.core.dom.AST.newName(AST.java:1965) > at org.jboss.forge.roaster.model.impl.FieldImpl.setType(FieldImpl.java:374) > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ROASTER-42) Cannot set Generic types on fields

by George Gastaldi (JIRA)

George Gastaldi created ROASTER-42: -------------------------------------- Summary: Cannot set Generic types on fields Key: ROASTER-42 URL: https://issues.jboss.org/browse/ROASTER-42 Project: Roaster Issue Type: Bug Components: JDT Affects Versions: 2.8.2.Final Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.8.3.Final The following code: {code} JavaClassSource javaClass = Roaster.create(JavaClassSource.class); FieldSource<JavaClassSource> field = javaClass.addField(); field.setPrivate().setName("email").setType("java.util.List<String>"); {code} Throws the following exception {code} java.lang.IllegalArgumentException: Invalid identifier : >List<String>< at org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:199) at org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:2202) at org.eclipse.jdt.core.dom.AST.newName(AST.java:1965) at org.jboss.forge.roaster.model.impl.FieldImpl.setType(FieldImpl.java:374) {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2058) Being able to create fields with generics types

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2058?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-2058: ---------------------------------------- The following exception is thrown: {code} java.lang.IllegalArgumentException: Invalid identifier : >List<String>< at org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:199) at org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:2202) at org.eclipse.jdt.core.dom.AST.newName(AST.java:1965) at org.jboss.forge.roaster.model.impl.FieldImpl.setType(FieldImpl.java:374) {code} > Being able to create fields with generics types > ----------------------------------------------- > > Key: FORGE-2058 > URL: https://issues.jboss.org/browse/FORGE-2058 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.12.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > At the moment we can add a new field to a Java class : > {code} > java-new-field --named log --type java.util.List > {code} > It would be very useful to be able to add generics. Something like : > {code} > java-new-field --named log --type java.util.List<String> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2099) scaffold-generate command should have a --targetPackage attribute

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-2099?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-2099: ------------------------------------------ {quote} vineetr_ agoncal: Changes should be done here: https://github.com/forge/core/blob/master/javaee/faces/src/main/java/org/... vineetr_ specifically this line should be changed to the user-configurable value: viewBean.setPackage(java.getBasePackage() + ".view"); vineetr_ java.getBasePackage() would return a safe value from groupId+artifactId, to be used in a package name {quote} > scaffold-generate command should have a --targetPackage attribute > ----------------------------------------------------------------- > > Key: FORGE-2099 > URL: https://issues.jboss.org/browse/FORGE-2099 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.12.1.Final > Reporter: Antonio Goncalves > Fix For: 2.12.2.Final > > > Today, the {{scaffold-generate}} command has the following attributes : > {code} > scaffold-generate --provider --webRoot --targets --pageTemplate > {code} > {{webRoot}} is to change the default directory of where the pages are generated. It would be good to have a {{targetPackage}} attribute as well, to customize the default package of the generated JSF Beans -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2099) scaffold-generate command should have a --targetPackage attribute

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-2099: ---------------------------------------- Summary: scaffold-generate command should have a --targetPackage attribute Key: FORGE-2099 URL: https://issues.jboss.org/browse/FORGE-2099 Project: Forge Issue Type: Sub-task Components: Scaffold Affects Versions: 2.12.1.Final Reporter: Antonio Goncalves Fix For: 2.12.2.Final Today, the {{scaffold-generate}} command has the following attributes : {code} scaffold-generate --provider --webRoot --targets --pageTemplate {code} {{webRoot}} is to change the default directory of where the pages are generated. It would be good to have a {{targetPackage}} attribute as well, to customize the default package of the generated JSF Beans -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 5 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