December 2013 - forge-issues - Jboss List Archives

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1389?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1389. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Final Resolution: Won't Fix [~agoncal], You need to use the {{-r}} flag: eg: {{rm -rf agoncal-application-petstore-ee7}} > 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1403) Pressing TAB twice while completing should print a description of the current option being completed

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1403: ----------------------------------------- Summary: Pressing TAB twice while completing should print a description of the current option being completed Key: FORGE-1403 URL: https://issues.jboss.org/browse/FORGE-1403 Project: Forge Issue Type: Sub-task Components: UI - Shell Affects Versions: 2.0.0.Beta4 Reporter: Lincoln Baxter III Forge 1 is very good about helping the user figure out what various command options are for. Forge 2 lacks this helpful information, and it would be useful to display. -- 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

10 years, 4 months

1
0
0 / 0

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1396?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1396: ------------------------------------------- Good question. Can I get the opinion of [~crobson] again? What do you think Catherine? Should we go singular or plural, or both, and in what situations? > 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1388) set command missing

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1388?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1388. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Final Resolution: Done set was replaced by export, so the line above should read: {code} export ACCEPT_DEFAULTS=true {code} ps: this flag is not used anywhere in Forge 2 atm. > set command missing > ------------------- > > Key: FORGE-1388 > URL: https://issues.jboss.org/browse/FORGE-1388 > 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 > > > I'm migrating a Forge 1.x script to 2.x. One of the first command I usually write is : > {code} > set ACCEPT_DEFAULTS true ; > {code} > The {{set}} command hasn't been implemented yet. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1390) Cannot set the --finalName on a new project

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1390?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1390. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Final Resolution: Done > Cannot set the --finalName on a new project > ------------------------------------------- > > Key: FORGE-1390 > URL: https://issues.jboss.org/browse/FORGE-1390 > 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 > > > In Forge 1.x I could set a different {{--finalName}} to a project : > {code} > new-project --named agoncal-application-petstore-ee7 --topLevelPackage org.agoncal.application.petstore --type war --finalName applicationPetstore ; > {code} > I cannot do the same in Forge 2.x because there is no {{--finalName}} attribute to the {{project-new}} command : > {code} > project-new --named agoncal-application-petstore-ee7 --topLevelPackage org.agoncal.application.petstore --type war > {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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1395) Rename register-as-serviceloader-service command

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1395?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1395. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Final Resolution: Done > Rename register-as-serviceloader-service command > ------------------------------------------------ > > Key: FORGE-1395 > URL: https://issues.jboss.org/browse/FORGE-1395 > 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 > > > I don't know what this command does, but if we follow the new naming convention, it should be > {code} > service-register-as-serviceloader > {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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1401) What does --primitive do ?

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1401?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1401: ---------------------------------------- This is supposed to be used when the typeName is a wrapper class but you intend to use the primitive version of it. Eg: {{jpa-new-field --typeName Integer --named someNumber --primitive --entity Customer}} will create a private int someNumber; with its getters and setters. > What does --primitive do ? > -------------------------- > > Key: FORGE-1401 > URL: https://issues.jboss.org/browse/FORGE-1401 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > Reporter: Antonio Goncalves > > The {{jpa-new-field}} has a {{--primitive}} attribute but I don't know its usage. First I thought it was the primitive datatype (int, float...) but this is the {{--typeName}}. > {code} > [PurchaseOrder.java]$ jpa-new-field > --typeName --named --lob --relationshipType --entity --length --primitive > {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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1402) Angularjs plugin does not create supporting beans

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1402?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1402: ------------------------------------------- Hey Robb, This is actually by design. To create the supporting beans, you need to run the 'rest' generation commands on the same entities. [~vineet.reynolds] would have to explain why he did it this way. ~Lincoln > Angularjs plugin does not create supporting beans > -------------------------------------------------- > > Key: FORGE-1402 > URL: https://issues.jboss.org/browse/FORGE-1402 > Project: Forge > Issue Type: Feature Request > Components: Plugin Repository > Affects Versions: 1.4.1.Final > Environment: Mac Maverick with JBDS 7.1 > Reporter: Robb Greathouse > > When using the Angularjs plugin it creates the html pages; but does not create the backing beans to support the functionality of the page. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1402) Angularjs plugin does not create supporting beans

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1402?page=com.atlassian.jira.plugin... ] Lincoln Baxter III closed FORGE-1402. ------------------------------------- Resolution: Rejected > Angularjs plugin does not create supporting beans > -------------------------------------------------- > > Key: FORGE-1402 > URL: https://issues.jboss.org/browse/FORGE-1402 > Project: Forge > Issue Type: Feature Request > Components: Plugin Repository > Affects Versions: 1.4.1.Final > Environment: Mac Maverick with JBDS 7.1 > Reporter: Robb Greathouse > > When using the Angularjs plugin it creates the html pages; but does not create the backing beans to support the functionality of the page. -- 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

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1402) Angularjs plugin does not create supporting beans

by Robb Greathouse (JIRA)

Robb Greathouse created FORGE-1402: -------------------------------------- Summary: Angularjs plugin does not create supporting beans Key: FORGE-1402 URL: https://issues.jboss.org/browse/FORGE-1402 Project: Forge Issue Type: Feature Request Components: Plugin Repository Affects Versions: 1.4.1.Final Environment: Mac Maverick with JBDS 7.1 Reporter: Robb Greathouse When using the Angularjs plugin it creates the html pages; but does not create the backing beans to support the functionality of the page. -- 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

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues December 2013