January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1455) project-add-dependency command is missing

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1455?page=com.atlassian.jira.plugin... ] Lincoln Baxter III reassigned FORGE-1455: ----------------------------------------- Assignee: Lincoln Baxter III > project-add-dependency command is missing > ----------------------------------------- > > Key: FORGE-1455 > URL: https://issues.jboss.org/browse/FORGE-1455 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR1 > Reporter: Antonio Goncalves > Assignee: Lincoln Baxter III > Fix For: 2.x Future > > > This command is similar to the following on in Forge 1.x > {code} > project add-dependency javax:javaee-api:7.0:provided > {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-1477) Being able to create mapped superclasses

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1477?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1477: ------------------------------------------ YES !!! > Being able to create mapped superclasses > ---------------------------------------- > > Key: FORGE-1477 > URL: https://issues.jboss.org/browse/FORGE-1477 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.0.Final > > > For inheritance, it is important to create mapped superclasses as well as entities. So we need the following command : > {code} > jpa-new-mapped-superclass --named --targetPackage > {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-1477) Being able to create mapped superclasses

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1477?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1477. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Final (was: 2.x Future) Resolution: Done > Being able to create mapped superclasses > ---------------------------------------- > > Key: FORGE-1477 > URL: https://issues.jboss.org/browse/FORGE-1477 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.0.Final > > > For inheritance, it is important to create mapped superclasses as well as entities. So we need the following command : > {code} > jpa-new-mapped-superclass --named --targetPackage > {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-1496) @RequiresXXX annotations in Forge 1.x should be migrated to Forge 2

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1496?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1496: ---------------------------------------- Same goes to {{@FacetConstraint}} > @RequiresXXX annotations in Forge 1.x should be migrated to Forge 2 > ------------------------------------------------------------------- > > Key: FORGE-1496 > URL: https://issues.jboss.org/browse/FORGE-1496 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, UI - API > Affects Versions: 2.0.0.CR1 > Reporter: George Gastaldi > Fix For: 2.x Future > > > - {{@RequiresResource}} > - {{@RequiresPackagingType}} > - {{@RequiresProject}} > These annotations could be implemented in Forge 2.x as {{EnableHandlerCommand}} implementations. -- 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-1496) @RequiresXXX annotations in Forge 1.x should be migrated to Forge 2

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1496: -------------------------------------- Summary: @RequiresXXX annotations in Forge 1.x should be migrated to Forge 2 Key: FORGE-1496 URL: https://issues.jboss.org/browse/FORGE-1496 Project: Forge Issue Type: Feature Request Components: Brainstorming, UI - API Affects Versions: 2.0.0.CR1 Reporter: George Gastaldi Fix For: 2.x Future - {{@RequiresResource}} - {{@RequiresPackagingType}} - {{@RequiresProject}} These annotations could be implemented in Forge 2.x as {{EnableHandlerCommand}} implementations. -- 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-1444) jpa-new-field --entity disapearing on TAB completion

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1444?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1444: ------------------------------------------ Yes, I realized it with Bean Validation. I now add my constraints in the correct order : {code} constraint-add --onProperty firstname --constraint NotNull ; constraint-add --onProperty firstname --constraint Size --min 2 --max 50 ; constraint-add --onProperty lastname --constraint NotNull ; constraint-add --onProperty lastname --constraint Size --min 2 --max 50 ; constraint-add --onProperty bio --constraint Size --min 2 --max 5000 ; {code} It looked strange at the beginning but I'm getting use to it. Closing the JIRA > jpa-new-field --entity disapearing on TAB completion > ---------------------------------------------------- > > Key: FORGE-1444 > URL: https://issues.jboss.org/browse/FORGE-1444 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I want to create a One-to-Many relationship. When I type the following and hit TAB, I get the {{--entity}} parameter > {code} > [Talk.java]$ jpa-new-field --named speakers -- > --typeName --lob --relationshipType --entity --length --primitive > {code} > But if I set the relationship first, and then hit TAB, the {{--entity}} parameter doesn't show > {code} > [Talk.java]$ jpa-new-field --named speakers --relationshipType One-to-Many -- > --inverseFieldName --cascadeType --fetchType --required > {code} > Looks like there is an order on the parameters (e.g. if you enter one, then something else doesn't show up), but it's not very clear -- 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-1444) jpa-new-field --entity disapearing on TAB completion

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1444?page=com.atlassian.jira.plugin... ] Antonio Goncalves closed FORGE-1444. ------------------------------------ Resolution: Done > jpa-new-field --entity disapearing on TAB completion > ---------------------------------------------------- > > Key: FORGE-1444 > URL: https://issues.jboss.org/browse/FORGE-1444 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I want to create a One-to-Many relationship. When I type the following and hit TAB, I get the {{--entity}} parameter > {code} > [Talk.java]$ jpa-new-field --named speakers -- > --typeName --lob --relationshipType --entity --length --primitive > {code} > But if I set the relationship first, and then hit TAB, the {{--entity}} parameter doesn't show > {code} > [Talk.java]$ jpa-new-field --named speakers --relationshipType One-to-Many -- > --inverseFieldName --cascadeType --fetchType --required > {code} > Looks like there is an order on the parameters (e.g. if you enter one, then something else doesn't show up), but it's not very clear -- 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-1444) jpa-new-field --entity disapearing on TAB completion

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1444?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1444: ---------------------------------------- Hi Antonio, Yes, the order is important because it belongs to the second wizard step. Any option informed belonging to the previous step will automatically not appear in the completion list. > jpa-new-field --entity disapearing on TAB completion > ---------------------------------------------------- > > Key: FORGE-1444 > URL: https://issues.jboss.org/browse/FORGE-1444 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Final > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I want to create a One-to-Many relationship. When I type the following and hit TAB, I get the {{--entity}} parameter > {code} > [Talk.java]$ jpa-new-field --named speakers -- > --typeName --lob --relationshipType --entity --length --primitive > {code} > But if I set the relationship first, and then hit TAB, the {{--entity}} parameter doesn't show > {code} > [Talk.java]$ jpa-new-field --named speakers --relationshipType One-to-Many -- > --inverseFieldName --cascadeType --fetchType --required > {code} > Looks like there is an order on the parameters (e.g. if you enter one, then something else doesn't show up), but it's not very clear -- 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-1443) database.action property in persistence.xml should be drop-and-create

by Ivan St. Ivanov (JIRA)

[ https://issues.jboss.org/browse/FORGE-1443?page=com.atlassian.jira.plugin... ] Ivan St. Ivanov reassigned FORGE-1443: -------------------------------------- Assignee: Ivan St. Ivanov > database.action property in persistence.xml should be drop-and-create > --------------------------------------------------------------------- > > Key: FORGE-1443 > URL: https://issues.jboss.org/browse/FORGE-1443 > Project: Forge > Issue Type: Sub-task > Components: Scaffold > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Assignee: Ivan St. Ivanov > Fix For: 2.x Future > > > When you setup JPA in Forge 1.x you get : > {code} > <property name="eclipselink.ddl-generation" value="drop-and-create-tables"/> > {code} > In Forge 2.Beta instead of {{drop-and-create}} you get only {{create}} : > {code} > <property name="javax.persistence.schema-generation.database.action" value="create"/> > {code} > Instead you should have > {code} > <property name="javax.persistence.schema-generation.database.action" value="drop-and-create"/> > {code} > And by the way, why not generating the DDL script as well ? You could have : > {code} > <property name="javax.persistence.schema-generation.database.action" value="drop-and-create"/> > <property name="javax.persistence.schema-generation.scripts.action" value="drop-and-create"/> > <property name="javax.persistence.schema-generation.scripts.create-target" value="<projectName>Create.ddl"/> > <property name="javax.persistence.schema-generation.scripts.drop-target" value="<projectName>Drop.ddl"/> > {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-1495) Group or order related command parameters across wizard steps for the Shell UI

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1495?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1495: ----------------------------------- Description: Command parameters from all commands participating in a wizard are coalesced together. This becomes less intuitive when a large number of parameters are listed, especially in the parameter auto-complete list, like so: {noformat} [helloworld]$ scaffold-setup --facesVersion --container --ejbVersion --cdiVersion --provider --dbType --jpaVersion --configureMetadata --overwrite --target --servletVersion --persistenceUnitName --dataSourceName {noformat} It would be beneficial to group related command parameters together. Some ways to group related commands would be to use rows (with each row grouping related command parameters) or separate Shell colors (a separate color for a command parameter group), or a combination of both. was: Command parameters from all commands participating in a wizard are coalesced together. This becomes less intuitive when a large number of parameters are listed, especially in the parameter auto-complete list, like so: {{noformat}} [helloworld]$ scaffold-setup --facesVersion --container --ejbVersion --cdiVersion --provider --dbType --jpaVersion --configureMetadata --overwrite --target --servletVersion --persistenceUnitName --dataSourceName {{noformat}} It would be beneficial to group related command parameters together. Some ways to group related commands would be to use rows (with each row grouping related command parameters) or separate Shell colors (a separate color for a command parameter group), or a combination of both. > Group or order related command parameters across wizard steps for the Shell UI > ------------------------------------------------------------------------------ > > Key: FORGE-1495 > URL: https://issues.jboss.org/browse/FORGE-1495 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.CR1 > Reporter: Vineet Reynolds > Priority: Minor > > Command parameters from all commands participating in a wizard are coalesced together. This becomes less intuitive when a large number of parameters are listed, especially in the parameter auto-complete list, like so: > {noformat} > [helloworld]$ scaffold-setup > --facesVersion --container --ejbVersion --cdiVersion --provider --dbType --jpaVersion > --configureMetadata --overwrite --target --servletVersion --persistenceUnitName --dataSourceName > {noformat} > It would be beneficial to group related command parameters together. Some ways to group related commands would be to use rows (with each row grouping related command parameters) or separate Shell colors (a separate color for a command parameter group), or a combination of both. -- 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