August 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGEPLUGINS-126) Rework the AngularJS scaffolding to support the new REST resource representations

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-126?page=com.atlassian.jira.... ] Vineet Reynolds resolved FORGEPLUGINS-126. ------------------------------------------ Resolution: Partially Completed Setting resolution as partially completed. > Rework the AngularJS scaffolding to support the new REST resource representations > --------------------------------------------------------------------------------- > > Key: FORGEPLUGINS-126 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-126 > Project: Forge Plugins > Issue Type: Feature Request > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Critical > > Based on the ongoing work for FORGE-1060, it would be necessary to rework the logic for handling associations (both n-to-many and n-to-one) since only Ids of the associated fields are required now. > Additional fields that are not a part of the associated resource's representation should not be sent to the server, since it is possible that the server may treat such fields in the incoming JSON representation as not ignorable and respond with a HTTP 400 error. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-126) Rework the AngularJS scaffolding to support the new REST resource representations

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-126?page=com.atlassian.jira.... ] Vineet Reynolds reopened FORGEPLUGINS-126: ------------------------------------------ > Rework the AngularJS scaffolding to support the new REST resource representations > --------------------------------------------------------------------------------- > > Key: FORGEPLUGINS-126 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-126 > Project: Forge Plugins > Issue Type: Feature Request > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Critical > > Based on the ongoing work for FORGE-1060, it would be necessary to rework the logic for handling associations (both n-to-many and n-to-one) since only Ids of the associated fields are required now. > Additional fields that are not a part of the associated resource's representation should not be sent to the server, since it is possible that the server may treat such fields in the incoming JSON representation as not ignorable and respond with a HTTP 400 error. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-126) Rework the AngularJS scaffolding to support the new REST resource representations

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-126?page=com.atlassian.jira.... ] Vineet Reynolds resolved FORGEPLUGINS-126. ------------------------------------------ Resolution: Done Pushed upstream into a separate branch: https://github.com/forge/angularjs-scaffoldx-plugin/tree/FORGEPLUGINS-126 This will need to be merged into the master branch after Forge 1.4.0 containing FORGE-1060 is released. > Rework the AngularJS scaffolding to support the new REST resource representations > --------------------------------------------------------------------------------- > > Key: FORGEPLUGINS-126 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-126 > Project: Forge Plugins > Issue Type: Feature Request > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Critical > > Based on the ongoing work for FORGE-1060, it would be necessary to rework the logic for handling associations (both n-to-many and n-to-one) since only Ids of the associated fields are required now. > Additional fields that are not a part of the associated resource's representation should not be sent to the server, since it is possible that the server may treat such fields in the incoming JSON representation as not ignorable and respond with a HTTP 400 error. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1114) Support multi-step UIWizard commands in Shell

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1114?page=com.atlassian.jira.plugin... ] George Gastaldi reassigned FORGE-1114: -------------------------------------- Assignee: George Gastaldi > Support multi-step UIWizard commands in Shell > --------------------------------------------- > > Key: FORGE-1114 > URL: https://issues.jboss.org/browse/FORGE-1114 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Alpha10 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.x Future > > > {code} > $ new-project --named blah > User presses <TAB>: > Options from Step 1 are displayed (Step 1 not yet valid): > --type (required) > --targetDir > --topLevelPackage > $ new-project --named blah --type “Forge Addon” > User presses <TAB>: > Options from Step 1 AND Step 2 are displayed (Step 1 is valid): > --targetDir (Step 1) > --topLevelPackage (Step 1) > --projectLayout (Step 2) > --installAddons (Step 2) > $ new-project --named blah --type “Forge Addon” --projectLayout complex > User presses <TAB>: > Options from Step 2 only are displayed: > --installAddons > $ new-project --named blah --type “Maven” --projectLayout complex > User presses <TAB> > Shell throws error: > “--projectLayout is not a valid input for “MavenProjectStep” > Re-display previous line and let the user fix it. (Completion fails, but command line preserved.) > $ new-project --named blah --type “Maven” --projectLayout complex > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1114) Support multi-step UIWizard commands in Shell

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1114?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1114: ----------------------------------- Fix Version/s: 2.x Future > Support multi-step UIWizard commands in Shell > --------------------------------------------- > > Key: FORGE-1114 > URL: https://issues.jboss.org/browse/FORGE-1114 > Project: Forge > Issue Type: Feature Request > Components: UI - Shell > Affects Versions: 2.0.0.Alpha10 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > {code} > $ new-project --named blah > User presses <TAB>: > Options from Step 1 are displayed (Step 1 not yet valid): > --type (required) > --targetDir > --topLevelPackage > $ new-project --named blah --type “Forge Addon” > User presses <TAB>: > Options from Step 1 AND Step 2 are displayed (Step 1 is valid): > --targetDir (Step 1) > --topLevelPackage (Step 1) > --projectLayout (Step 2) > --installAddons (Step 2) > $ new-project --named blah --type “Forge Addon” --projectLayout complex > User presses <TAB>: > Options from Step 2 only are displayed: > --installAddons > $ new-project --named blah --type “Maven” --projectLayout complex > User presses <TAB> > Shell throws error: > “--projectLayout is not a valid input for “MavenProjectStep” > Re-display previous line and let the user fix it. (Completion fails, but command line preserved.) > $ new-project --named blah --type “Maven” --projectLayout complex > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1114) Support multi-step UIWizard commands in Shell

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1114: ----------------------------------------- Summary: Support multi-step UIWizard commands in Shell Key: FORGE-1114 URL: https://issues.jboss.org/browse/FORGE-1114 Project: Forge Issue Type: Feature Request Components: UI - Shell Affects Versions: 2.0.0.Alpha10 Reporter: Lincoln Baxter III {code} $ new-project --named blah User presses <TAB>: Options from Step 1 are displayed (Step 1 not yet valid): --type (required) --targetDir --topLevelPackage $ new-project --named blah --type “Forge Addon” User presses <TAB>: Options from Step 1 AND Step 2 are displayed (Step 1 is valid): --targetDir (Step 1) --topLevelPackage (Step 1) --projectLayout (Step 2) --installAddons (Step 2) $ new-project --named blah --type “Forge Addon” --projectLayout complex User presses <TAB>: Options from Step 2 only are displayed: --installAddons $ new-project --named blah --type “Maven” --projectLayout complex User presses <TAB> Shell throws error: “--projectLayout is not a valid input for “MavenProjectStep” Re-display previous line and let the user fix it. (Completion fails, but command line preserved.) $ new-project --named blah --type “Maven” --projectLayout complex {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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1112) Support paths with spaces

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1112?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1112. ---------------------------------- Assignee: David Mann Resolution: Done Merged upstream, Thank you! > Support paths with spaces > ------------------------- > > Key: FORGE-1112 > URL: https://issues.jboss.org/browse/FORGE-1112 > Project: Forge > Issue Type: Bug > Components: Forge Build > Affects Versions: 1.3.3.Final > Environment: Windows with a git bash, probably the same issue with cygwin and Installations which have JAVA_HOME=C:\Program Files\Java\etcetc > Reporter: David Mann > Assignee: David Mann > Priority: Minor > Fix For: 1.4.0.Final > > > In bin/forge, you should quote the call to the java binary > So, in v1.3.3Final/bin/forge line 142 should read > JAVAVER=`"$JAVACMD" -version 2>&1` > instead of > JAVAVER=`$JAVACMD -version 2>&1` -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1112) Support paths with spaces

by David Mann (JIRA)

[ https://issues.jboss.org/browse/FORGE-1112?page=com.atlassian.jira.plugin... ] David Mann commented on FORGE-1112: ----------------------------------- Hi George, here you go: https://github.com/forge/core/pull/343 I didn't bother to make a new branch for this, but if you need it I can do it. Best regards, David > Support paths with spaces > ------------------------- > > Key: FORGE-1112 > URL: https://issues.jboss.org/browse/FORGE-1112 > Project: Forge > Issue Type: Bug > Components: Forge Build > Affects Versions: 1.3.3.Final > Environment: Windows with a git bash, probably the same issue with cygwin and Installations which have JAVA_HOME=C:\Program Files\Java\etcetc > Reporter: David Mann > Priority: Minor > Fix For: 1.4.0.Final > > > In bin/forge, you should quote the call to the java binary > So, in v1.3.3Final/bin/forge line 142 should read > JAVAVER=`"$JAVACMD" -version 2>&1` > instead of > JAVAVER=`$JAVACMD -version 2>&1` -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1098) Scaffold setup command does not setup the chosen scaffold

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1098?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1098: ----------------------------------- Status: Closed (was: Pull Request Sent) Assignee: Vineet Reynolds Fix Version/s: 1.4.0.Final Resolution: Done Merged > Scaffold setup command does not setup the chosen scaffold > --------------------------------------------------------- > > Key: FORGE-1098 > URL: https://issues.jboss.org/browse/FORGE-1098 > Project: Forge > Issue Type: Bug > Components: Scaffold > Affects Versions: 1.3.3.Final > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Blocker > Fix For: 1.4.0.Final > > > On running the {{scaffold setup}} or {{scaffold-x setup}} commands, the default Faces scaffolding provider is chosen even though a different provider was to be installed. > As an example, instead of setting up the AngularJS provider the Faces provider is installed: > {noformat} > [ticket-monster] demo $ scaffold-x setup --scaffoldType angularjs > ***INFO*** Using currently installed scaffold [faces] > ? [/home/vineet/git-repos/ticket-monster/demo/src/main/webapp/index.html] File exists, overwrite? [Y/n] > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/favicon.ico > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/scaffold/paginator.xhtml > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/scaffold/pageTemplate.xhtml > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/index.html > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/index.xhtml > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/error.xhtml > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/add.png > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/bootstrap.css > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/false.png > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/favicon.ico > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/forge-logo.png > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/forge-style.css > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/remove.png > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/search.png > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/true.png > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/resources/jboss-community.png > Wrote /home/vineet/git-repos/ticket-monster/demo/src/main/webapp/WEB-INF/web.xml > {noformat} -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1113) Need to be able to listen to Exported service events (Service becomes available/unavailable)

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1113: ----------------------------------------- Summary: Need to be able to listen to Exported service events (Service becomes available/unavailable) Key: FORGE-1113 URL: https://issues.jboss.org/browse/FORGE-1113 Project: Forge Issue Type: Feature Request Components: Furnace (Container) Affects Versions: 2.0.0.Alpha10 Reporter: Lincoln Baxter III 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

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2013