[JBoss JIRA] (FORGE-1394) Rename bean-validation-setup command
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1394?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1394:
-------------------------------------
Fix Version/s: 2.x Future
> Rename bean-validation-setup command
> ------------------------------------
>
> Key: FORGE-1394
> URL: https://issues.jboss.org/browse/FORGE-1394
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> At the moment, {{setup}} commands are related to the core technology :
> {code}
> faces-new-converter faces-new-validator faces-new-validator-method faces-setup
> jpa-new-entity jpa-new-field jpa-setup
> {code}
> For Bean Validation, there is a {{bean-validation-setup}} command. But, shouldn't it be {{constraint-setup}} ? Also see [FORGE-1393].
--
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
11 years, 9 months
[JBoss JIRA] (FORGE-1393) constraint commands are missing
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1393?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1393:
-------------------------------------
Fix Version/s: 2.x Future
> constraint commands are missing
> -------------------------------
>
> Key: FORGE-1393
> URL: https://issues.jboss.org/browse/FORGE-1393
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> On Forge 1.x you could add constraints to a specific field with
> {code}
> constraint NotNull --onProperty login ;
> {code}
> The {{constraint}} commands are missing. If we follow the new naming convention, we should have, at least, one command to create new custom constraints (that could go into a default {{constraint}} package for example :
> {code}
> constraint-new MyOwnConstraint ;
> {code}
> And a command to add a constraint to a property :
> {code}
> constraint-add NotNull --onProperty login ;
> constraint-add MyOwnConstraint --onProperty lastname ;
> {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
11 years, 9 months
[JBoss JIRA] (FORGE-1392) more command does not always work
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1392?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1392:
-------------------------------------
Fix Version/s: 2.x Future
> more command does not always work
> ---------------------------------
>
> Key: FORGE-1392
> URL: https://issues.jboss.org/browse/FORGE-1392
> 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 a project, I can do a {{more}} on the {{pom.xml}}. But then, after creating a few entities, I cannot do a {{more}} on the entity I've created.
> {code}
> [model]$ more Country.java
> /Users/antoniombp/Documents/Code/temp/Country.java: No such file or directory
> [model]$ pwd
> /Users/antoniombp/Documents/Code/temp/agoncal-application-petstore-ee7/src/main/java/org/agoncal/application/petstore/model
> {code}
> In this example I am on the {{model}} subdirectory, when I type {{more}} and hit TAB, the completion works for my entity {{Country}}, but then, the directory is not right :
> {code}
> /Users/antoniombp/Documents/Code/temp/Country.java
> {code}
> Instead of
> {code}
> /Users/antoniombp/Documents/Code/temp/agoncal-application-petstore-ee7/src/main/java/org/agoncal/application/petstore/model/Country.java
> {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
11 years, 9 months
[JBoss JIRA] (FORGE-1333) Forge "man" pages are missing for most UI Commands
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1333?page=com.atlassian.jira.plugin... ]
Antonio Goncalves updated FORGE-1333:
-------------------------------------
Affects Version/s: 2.0.0.Beta4
> Forge "man" pages are missing for most UI Commands
> --------------------------------------------------
>
> Key: FORGE-1333
> URL: https://issues.jboss.org/browse/FORGE-1333
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> This is more a question because I don't know what {{man}} is suppose to do. This is what I get :
> {code}
> [Test.java]$ man grep
> No manual entry for grep
> [Test.java]$ man echo
> No manual entry for echo
> {code}
> I would expect to have a manual for each Forge command and also to get completion (e.g. {{man jpa}} TAB and it will give all the JPA commands available in the manual
--
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
11 years, 9 months
[JBoss JIRA] (FORGE-1389) rm doesn't remove a none empty directory
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1389?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1389:
-------------------------------------------
Working on Man right now :)
> rm doesn't remove a none empty directory
> ----------------------------------------
>
> Key: FORGE-1389
> URL: https://issues.jboss.org/browse/FORGE-1389
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Assignee: George Gastaldi
> Fix For: 2.0.0.Final
>
>
> When I try to remove a none empty directory, even with the {{--force}} argument, it doesn't work :
> {code}
> [temp]$ rm agoncal-application-petstore-ee7
> ***ERROR*** rm: directory not empty and cannot be removed without '--force' '-f' option.
> [temp]$ rm -f agoncal-application-petstore-ee7
> ***ERROR*** directory not empty
> [temp]$ rm --force agoncal-application-petstore-ee7
> ***ERROR*** directory not empty
> {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
11 years, 9 months
[JBoss JIRA] (FORGE-1397) How to create a jpa-new-field of type Date ?
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1397?page=com.atlassian.jira.plugin... ]
George Gastaldi edited comment on FORGE-1397 at 1/3/14 10:17 AM:
-----------------------------------------------------------------
This would be the equivalent for jpa-new-field:
{code}
jpa-new-field --named dateOfBirth --typeName java.util.Date --temporalType DATE
{code}
was (Author: gastaldi):
This would be the equivalent for jpa-new-field:
{{jpa-new-field --named dateOfBirth --typeName java.util.Date --temporalType DATE}}
> How to create a jpa-new-field of type Date ?
> --------------------------------------------
>
> Key: FORGE-1397
> URL: https://issues.jboss.org/browse/FORGE-1397
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
>
> To create a Date in Forge 1.x we would type :
> {code}
> field temporal --named dateOfBirth --type DATE ;
> {code}
> I cannot find an equivalent for the command {{jpa-new-field}}
--
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
11 years, 9 months