January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1448) Cannot cd an Entity with TAB completion

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1448?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1448: ------------------------------------- Affects Version/s: 2.0.0.CR2 (was: 2.0.0.Beta4) > Cannot cd an Entity with TAB completion > --------------------------------------- > > Key: FORGE-1448 > URL: https://issues.jboss.org/browse/FORGE-1448 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > When I create 2 entities, I can {{cd}} from on to another if I specify the class, but it doesn't work with TAB completion : > {code} > [Speaker.java]$ cd ../Talk.java > [Talk.java]$ cd ../Speaker.java > [Speaker.java]$ cd ../T TAB > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1448) Cannot cd an Entity with TAB completion

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1448?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1448: ------------------------------------- Parent Issue: FORGE-1505 (was: FORGE-1387) > Cannot cd an Entity with TAB completion > --------------------------------------- > > Key: FORGE-1448 > URL: https://issues.jboss.org/browse/FORGE-1448 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > When I create 2 entities, I can {{cd}} from on to another if I specify the class, but it doesn't work with TAB completion : > {code} > [Speaker.java]$ cd ../Talk.java > [Talk.java]$ cd ../Speaker.java > [Speaker.java]$ cd ../T TAB > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1506) Cannot create a field on a Mapped Superclass

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1506?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1506: -------------------------------------- Assignee: George Gastaldi > Cannot create a field on a Mapped Superclass > -------------------------------------------- > > Key: FORGE-1506 > URL: https://issues.jboss.org/browse/FORGE-1506 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.x Future > > > I create a Mapped Superclass, try to add a field, and get a {{Entity must be specified}} : > {code} > [pluralsight-persistence]$ jpa-new-mapped-superclass --named Person > Modified /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/java > Created /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/java/com > Created /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/java/com/pluralsight > Created /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/java/com/pluralsight/persistence > Created /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/java/com/pluralsight/persistence/module07 > Created /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/java/com/pluralsight/persistence/module07/Person.java > ***SUCCESS*** Mapped Superclass com.pluralsight.persistence.module07.Person was created > [Person.java]$ jpa-new-field --named firstname --length 50 > Entity must be specified. > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1507) Mapped super classes are not generated under the model package

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1507: ---------------------------------------- Summary: Mapped super classes are not generated under the model package Key: FORGE-1507 URL: https://issues.jboss.org/browse/FORGE-1507 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.CR2 Reporter: Antonio Goncalves Fix For: 2.x Future When creating a Mapped Superclass, it goes to the root package instead of the {{model}} subpackage (like any entity) : {code} jpa-new-mapped-superclass --named Person {code} Gives {code} package com.pluralsight.persistence.module07; import javax.persistence.MappedSuperclass; @MappedSuperclass public class Person { } {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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1479) Explicitly setup in Bean Validation, not in JPA

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1479?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1479: ------------------------------------- Parent Issue: FORGE-1505 (was: FORGE-1387) > Explicitly setup in Bean Validation, not in JPA > ----------------------------------------------- > > Key: FORGE-1479 > URL: https://issues.jboss.org/browse/FORGE-1479 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR1 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Just after a creating a project, a create a new entity without setting up the persistence ({{jpa-setup}}) : > {code} > ***SUCCESS*** Project named 'test' has been created. > [test]$ jpa-new-entity --named Author > [Author.java]$ jpa-new-field --named firstname --length 50 > ***SUCCESS*** Field firstname created > {code} > This hasn't created a {{persistence.xml}} file. But on the other hand, if I want to add a constraint on the entity, I need to explicitelly setup Bean Validation : > {code} > [Author.java]$ con > connection-profile-create connection-profile-remove constraint-setup > [Author.java]$ constraint-setup > ***SUCCESS*** Bean Validation is installed. > [Author.java]$ con > connection-profile-create connection-profile-remove constraint-add constraint-setup > [Author.java]$ constraint-add --constraint NotNull --onProperty firstname > ***SUCCESS*** Constraint NotNull successfully configured > {code} > if most of the information is giving at project creation, do we still need to explicitly setup Java EE components ? At the moment we have the following : > {code} > servlet-setup > ejb-setup > soap-setup > cdi-setup > jms-setup > rest-setup > jpa-setup > faces-setup > jstl-setup > jta-setup > constraint-setup > {code} > Most of these commands do not have parameters (except for persistence, rest, validation). So why not activate them by default (or only if {{export ACCEPT_DEFAULTS=true}} ) ? Something like : "if the command {{constraint-add}} is entered, Forge would go {{if constraint is not setup, then I invoke constraint-setup}}", "if the command {{ejb-new}} is entered, Forge would go {{if ejb is not setup, then I invoke ejb-setup}}" > That would save some bugs (developers forgetting to setup things), less typing and shorter scripts. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1479) Explicitly setup in Bean Validation, not in JPA

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1479?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1479: ------------------------------------- Affects Version/s: 2.0.0.CR2 (was: 2.0.0.CR1) > Explicitly setup in Bean Validation, not in JPA > ----------------------------------------------- > > Key: FORGE-1479 > URL: https://issues.jboss.org/browse/FORGE-1479 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > Just after a creating a project, a create a new entity without setting up the persistence ({{jpa-setup}}) : > {code} > ***SUCCESS*** Project named 'test' has been created. > [test]$ jpa-new-entity --named Author > [Author.java]$ jpa-new-field --named firstname --length 50 > ***SUCCESS*** Field firstname created > {code} > This hasn't created a {{persistence.xml}} file. But on the other hand, if I want to add a constraint on the entity, I need to explicitelly setup Bean Validation : > {code} > [Author.java]$ con > connection-profile-create connection-profile-remove constraint-setup > [Author.java]$ constraint-setup > ***SUCCESS*** Bean Validation is installed. > [Author.java]$ con > connection-profile-create connection-profile-remove constraint-add constraint-setup > [Author.java]$ constraint-add --constraint NotNull --onProperty firstname > ***SUCCESS*** Constraint NotNull successfully configured > {code} > if most of the information is giving at project creation, do we still need to explicitly setup Java EE components ? At the moment we have the following : > {code} > servlet-setup > ejb-setup > soap-setup > cdi-setup > jms-setup > rest-setup > jpa-setup > faces-setup > jstl-setup > jta-setup > constraint-setup > {code} > Most of these commands do not have parameters (except for persistence, rest, validation). So why not activate them by default (or only if {{export ACCEPT_DEFAULTS=true}} ) ? Something like : "if the command {{constraint-add}} is entered, Forge would go {{if constraint is not setup, then I invoke constraint-setup}}", "if the command {{ejb-new}} is entered, Forge would go {{if ejb is not setup, then I invoke ejb-setup}}" > That would save some bugs (developers forgetting to setup things), less typing and shorter scripts. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1506) Cannot create a field on a Mapped Superclass

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1506: ---------------------------------------- Summary: Cannot create a field on a Mapped Superclass Key: FORGE-1506 URL: https://issues.jboss.org/browse/FORGE-1506 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.CR2 Reporter: Antonio Goncalves Fix For: 2.x Future I create a Mapped Superclass, try to add a field, and get a {{Entity must be specified}} : {code} [pluralsight-persistence]$ jpa-new-mapped-superclass --named Person Modified /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/java Created /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/java/com Created /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/java/com/pluralsight Created /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/java/com/pluralsight/persistence Created /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/java/com/pluralsight/persistence/module07 Created /Users/antoniombp/Documents/Code/temp/Forge/pluralsight-persistence/src/main/java/com/pluralsight/persistence/module07/Person.java ***SUCCESS*** Mapped Superclass com.pluralsight.persistence.module07.Person was created [Person.java]$ jpa-new-field --named firstname --length 50 Entity must be specified. {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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1437) project-new --type jar-resources is confusing

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1437?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1437: ------------------------------------- Affects Version/s: 2.0.0.CR2 (was: 2.0.0.Beta4) > project-new --type jar-resources is confusing > --------------------------------------------- > > Key: FORGE-1437 > URL: https://issues.jboss.org/browse/FORGE-1437 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.CR2 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I was used to {{jar}} so {{jar-resources}} is confusing. Is it a different thing ? > {code} > [Forge]$ project-new --named forge2 --topLevelPackage org.forge2.test --type > jar war addon jar-resources > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1437) project-new --type jar-resources is confusing

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1437?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-1437: ------------------------------------- Parent Issue: FORGE-1505 (was: FORGE-1387) > project-new --type jar-resources is confusing > --------------------------------------------- > > Key: FORGE-1437 > URL: https://issues.jboss.org/browse/FORGE-1437 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I was used to {{jar}} so {{jar-resources}} is confusing. Is it a different thing ? > {code} > [Forge]$ project-new --named forge2 --topLevelPackage org.forge2.test --type > jar war addon jar-resources > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1505) Perform a UX review of the Shell experience in Forge 2.CR

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1505: ---------------------------------------- Summary: Perform a UX review of the Shell experience in Forge 2.CR Key: FORGE-1505 URL: https://issues.jboss.org/browse/FORGE-1505 Project: Forge Issue Type: Feature Request Components: UI - Shell Affects Versions: 2.0.0.CR2 Reporter: Antonio Goncalves Fix For: 2.x Future -- 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, 2 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