January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1404) Option names with default values are not displayed when <TAB> is pressed

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1404?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1404. ---------------------------------- Fix Version/s: (was: 2.x Future) Resolution: Duplicate Issue Duplicate of FORGE-1407 > Option names with default values are not displayed when <TAB> is pressed > ------------------------------------------------------------------------ > > Key: FORGE-1404 > URL: https://issues.jboss.org/browse/FORGE-1404 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: George Gastaldi > Priority: Critical > > Eg: {{jpa-setup --container <TAB>}} > shows a list of containers, > however {{jpa-setup <TAB>}} doesn't display the {{container}} option -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1408) Forge 1.x and Forge 2.x coexisting

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1408?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1408. ---------------------------------- Assignee: George Gastaldi Resolution: Won't Fix Marking as "Won't Fix" as described above > Forge 1.x and Forge 2.x coexisting > ---------------------------------- > > Key: FORGE-1408 > URL: https://issues.jboss.org/browse/FORGE-1408 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > Assignee: George Gastaldi > > I'm using Forge 1.x to generate some code but I'm also trying Forge 2.x. Unfortunately it's impossible to use both at the same time. I usually have to remove the {{.forge}} folder (I needed to do it from Beta3 to Beta4). > Why not having a {{.forge1}} and {{.forge2}} folder, or {{.forge/1.x}} and {{.forge/2.x}}. That would be a first start (I'm not sure what else would Forge need) -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1389) rm doesn't remove a none empty directory

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1389?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1389: ------------------------------------------ BTW, there is a {{--recursive}} attribute in Forge 1.x > 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1396) Singular or Plural ?

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1396?page=com.atlassian.jira.plugin... ] Antonio Goncalves edited comment on FORGE-1396 at 1/2/14 5:56 AM: ------------------------------------------------------------------ In Forge 1.x to get all the commands we have {{list-commands}} with an 's', which will be {{commands-list}} in Forge 2.x.... but with or without 's' ? was (Author: agoncal): In Forge 1.x to get all the commands we have {{list-command}} with no 's', which will be {{command-list}} in Forge 2.x.... but with or without 's' ? > Singular or Plural ? > -------------------- > > Key: FORGE-1396 > URL: https://issues.jboss.org/browse/FORGE-1396 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > > For listing all the services we use the {{services-list}} command. Here, {{services}} is in plural. But if we have several commands related to services, we might end-up with a mixture of singular and plural : > {code} > services-list > service-register-as-serviceloader > {code} > Same thing could happen if we list all add-ons (here I'm supposing that the command {{addons-list}} exits) : > {code} > addons-list > addon-build-and-install > addon-install > addon-new-command > addon-remove > {code} > Is the mixture or plural and singular ok ? Shouldn't it all be in singular : > {code} > addon-list > service-list > {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

1
0
0 / 0

[JBoss JIRA] (FORGE-1408) Forge 1.x and Forge 2.x coexisting

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1408?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1408: ------------------------------------------ Makes sense > Forge 1.x and Forge 2.x coexisting > ---------------------------------- > > Key: FORGE-1408 > URL: https://issues.jboss.org/browse/FORGE-1408 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > > I'm using Forge 1.x to generate some code but I'm also trying Forge 2.x. Unfortunately it's impossible to use both at the same time. I usually have to remove the {{.forge}} folder (I needed to do it from Beta3 to Beta4). > Why not having a {{.forge1}} and {{.forge2}} folder, or {{.forge/1.x}} and {{.forge/2.x}}. That would be a first start (I'm not sure what else would Forge need) -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1408) Forge 1.x and Forge 2.x coexisting

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1408?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1408: ---------------------------------------- Not sure this is really needed, given that there is already a separation with "addons/" and "plugins/" subfolders inside ~/.forge. > Forge 1.x and Forge 2.x coexisting > ---------------------------------- > > Key: FORGE-1408 > URL: https://issues.jboss.org/browse/FORGE-1408 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > > I'm using Forge 1.x to generate some code but I'm also trying Forge 2.x. Unfortunately it's impossible to use both at the same time. I usually have to remove the {{.forge}} folder (I needed to do it from Beta3 to Beta4). > Why not having a {{.forge1}} and {{.forge2}} folder, or {{.forge/1.x}} and {{.forge/2.x}}. That would be a first start (I'm not sure what else would Forge need) -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1406) Support customization of Forge generated artifacts in Faces scaffolding

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1406?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1406: ------------------------------------------ That would be a great plus. Most big companies have their coding and architectural guides. This way they could change the templates to conform to their conventions. Something else to take into account is to be able to change global defaults, for example default package names. E.g entities are in the {{model}} package by default, but some companies would like to change it. This way, when you create a new entity ({{jpa-new-entity}}) it goes straight to their package name. > Support customization of Forge generated artifacts in Faces scaffolding > ----------------------------------------------------------------------- > > Key: FORGE-1406 > URL: https://issues.jboss.org/browse/FORGE-1406 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.0.0.Beta4 > Reporter: Vineet Reynolds > > Currently, the customization of the generated scaffold is limited to the Faces template used for the page. Aspects of the generated scaffold like the managed beans, the CSS files etc. cannot be customized during generation; they have to modified after generation. > This feature request is to track the ability to customize any necessary aspects of the generated scaffold. -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1408) Forge 1.x and Forge 2.x coexisting

by Antonio Goncalves (JIRA)

Antonio Goncalves created FORGE-1408: ---------------------------------------- Summary: Forge 1.x and Forge 2.x coexisting Key: FORGE-1408 URL: https://issues.jboss.org/browse/FORGE-1408 Project: Forge Issue Type: Feature Request Components: Brainstorming Affects Versions: 2.0.0.Beta4 Reporter: Antonio Goncalves I'm using Forge 1.x to generate some code but I'm also trying Forge 2.x. Unfortunately it's impossible to use both at the same time. I usually have to remove the {{.forge}} folder (I needed to do it from Beta3 to Beta4). Why not having a {{.forge1}} and {{.forge2}} folder, or {{.forge/1.x}} and {{.forge/2.x}}. That would be a first start (I'm not sure what else would Forge need) -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1389) rm doesn't remove a none empty directory

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1389?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1389: ------------------------------------------ Hum.... {{man}} would have helped in this case ;o) > 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1396) Singular or Plural ?

by Antonio Goncalves (JIRA)

[ https://issues.jboss.org/browse/FORGE-1396?page=com.atlassian.jira.plugin... ] Antonio Goncalves commented on FORGE-1396: ------------------------------------------ In Forge 1.x to get all the commands we have {{list-command}} with no 's', which will be {{command-list}} in Forge 2.x.... but with or without 's' ? > Singular or Plural ? > -------------------- > > Key: FORGE-1396 > URL: https://issues.jboss.org/browse/FORGE-1396 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > > For listing all the services we use the {{services-list}} command. Here, {{services}} is in plural. But if we have several commands related to services, we might end-up with a mixture of singular and plural : > {code} > services-list > service-register-as-serviceloader > {code} > Same thing could happen if we list all add-ons (here I'm supposing that the command {{addons-list}} exits) : > {code} > addons-list > addon-build-and-install > addon-install > addon-new-command > addon-remove > {code} > Is the mixture or plural and singular ok ? Shouldn't it all be in singular : > {code} > addon-list > service-list > {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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2014