January 2014 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1501) Combine the scaffold setup and generate commands

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1501?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1501: -------------------------------------- Fix Version/s: 2.x Future > Combine the scaffold setup and generate commands > ------------------------------------------------ > > Key: FORGE-1501 > URL: https://issues.jboss.org/browse/FORGE-1501 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.0.0.CR1 > Reporter: Vineet Reynolds > Fix For: 2.x Future > > > Having separate commands to setup the scaffolding prerequisites and later generate the scaffold from some resource(s) doesn't look intuitive considering the wizard based model available in Forge 2. We should therefore combine the two. -- 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-1384) forge2: add description text & example panels to "Forge Run Command" dialog

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1384?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1384: -------------------------------------- Fix Version/s: 2.x Future > forge2: add description text & example panels to "Forge Run Command" dialog > --------------------------------------------------------------------------- > > Key: FORGE-1384 > URL: https://issues.jboss.org/browse/FORGE-1384 > Project: Forge > Issue Type: Feature Request > Components: UI - Eclipse > Affects Versions: 2.0.0.Beta3 > Environment: Linux > Reporter: Gavin Flower > Fix For: 2.x Future > > > There is currently a tooltip, but it does not add really add much to what could be gained from the command name! > It might be a good idea to have a variable sized scrollable text panel in the bottom half to give a more detailed explanation. As a suitable explanation might range from a single sentence to several paragraphs (in the later case, the first para should be short summary that might be enough to more experienced people). It is important to explain why & when you would want to use the command, as well as what it does. Probably a good idea to say what files it creates and/or modifies... > Plus a second panel for examples, the examples may be in a tree structure, when there is more than one available. Each example would have: > (1) short descriptive name > (2) brief description of what it sets out to achieve and how > (3) the example code itself, along with appropriate comments > An unexpanded leaf will have (1) & as much of (2) as can fit on the rest of the line. When a leaf is expanded then the full detail will be available. In rare cases you might need several levels to group related examples together. > The target audience will consist of people who are totally new to Forge and to JEE, to those people with considerable related experience, as well as experienced developers from other areas (For example I started with FORTRAN & COBOL over 40 years ago, and have been doing Java for over 10 years, but relatively inexperienced in JEE). -- 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-957) Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-957?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-957: ---------------------------------- Fix Version/s: 2.x Future (was: 2.0.0.Final) > Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs > ------------------------------------------------------------------------------------------------------ > > Key: FORGE-957 > URL: https://issues.jboss.org/browse/FORGE-957 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha5 > Reporter: Lincoln Baxter III > Priority: Critical > Fix For: 2.x Future > > > This will allow things like, detecting that the user is on Wildfly AS, and subsequently selecting appropriate versions of specifications, libraries, and other setup configurations. -- 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-957) Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-957?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-957: ---------------------------------- Priority: Major (was: Critical) > Create "Stacks" addon, that allows providing stack implementations to supply default values in dialogs > ------------------------------------------------------------------------------------------------------ > > Key: FORGE-957 > URL: https://issues.jboss.org/browse/FORGE-957 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha5 > Reporter: Lincoln Baxter III > Fix For: 2.x Future > > > This will allow things like, detecting that the user is on Wildfly AS, and subsequently selecting appropriate versions of specifications, libraries, and other setup configurations. -- 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-1501) Combine the scaffold setup and generate commands

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1501?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1501: ------------------------------------------- As part of this rename, the "--target" or "--webRoot" option should be made available specifically by each scaffold provider as required, since this is not necessarily a universal option. E.g. It is used in Faces Scaffold, but wouldn't be in an Android or Cordova scaffold. > Combine the scaffold setup and generate commands > ------------------------------------------------ > > Key: FORGE-1501 > URL: https://issues.jboss.org/browse/FORGE-1501 > Project: Forge > Issue Type: Feature Request > Components: Scaffold > Affects Versions: 2.0.0.CR1 > Reporter: Vineet Reynolds > > Having separate commands to setup the scaffolding prerequisites and later generate the scaffold from some resource(s) doesn't look intuitive considering the wizard based model available in Forge 2. We should therefore combine the two. -- 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-1499) Rename endpoint to resource in the context of REST commands

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1499?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1499: -------------------------------------- Fix Version/s: 2.x Future > Rename endpoint to resource in the context of REST commands > ----------------------------------------------------------- > > Key: FORGE-1499 > URL: https://issues.jboss.org/browse/FORGE-1499 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 2.0.0.CR1 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > The word "endpoint" is a remnant of SOAP and makes less sense in REST discussions. We should instead reword it as "resource". -- 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-1387) Perform a UX review of the Shell experience in Forge 2.Beta4

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1387?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1387: -------------------------------------- Fix Version/s: 2.x Future > Perform a UX review of the Shell experience in Forge 2.Beta4 > ------------------------------------------------------------ > > Key: FORGE-1387 > URL: https://issues.jboss.org/browse/FORGE-1387 > Project: Forge > Issue Type: Task > Components: UI - Shell > Affects Versions: 2.0.0.Beta4 > 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

[JBoss JIRA] (FORGE-1489) Remove addon removes incorrect addon

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1489?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1489: -------------------------------------- Priority: Critical (was: Blocker) > Remove addon removes incorrect addon > ------------------------------------ > > Key: FORGE-1489 > URL: https://issues.jboss.org/browse/FORGE-1489 > Project: Forge > Issue Type: Feature Request > Components: Plugin Repository > Affects Versions: 2.0.0.CR1 > Reporter: Tom Cunningham > Priority: Critical > Fix For: 2.x Future > > Attachments: Graphic1.jpg, Graphic2.jpg > > > I've been installing two addons off and on and noticed that when I choose "Remove Addon" in the forge menu, one of my addons is selected for removal by default (see Graphic1). I unselect it, select my other addon (see Graphic2), but the first addon that was selected by default is removed and the addon that I selected is kept. -- 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-1461) "project-new" command fails while a ResourceTransaction is active

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1461?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1461: -------------------------------------- Priority: Critical (was: Major) > "project-new" command fails while a ResourceTransaction is active > ----------------------------------------------------------------- > > Key: FORGE-1461 > URL: https://issues.jboss.org/browse/FORGE-1461 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Resources API > Affects Versions: 2.0.0.CR1 > Reporter: Lincoln Baxter III > Priority: Critical > Fix For: 2.x Future > > > {code}[Desktop]$ transaction-start > ***SUCCESS*** Resource Transaction started > [Desktop]$ project-new > --named --topLevelPackage --targetLocation --version > --finalName --buildSystem --type > [Desktop]$ project-new --named example > ***SUCCESS*** Project named 'example' has been created. > Exception when parsing/running: project-new --named example, Current working directory must be a directory > [Desktop]$ > [Desktop]$ > [Desktop]$ ls > pom.xml src > [Desktop]$ cd .. > [Desktop]$ ls > example > [Desktop]$ transaction-commit > [Desktop]$ > {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-1489) Remove addon removes incorrect addon

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1489?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1489: -------------------------------------- Priority: Blocker (was: Major) > Remove addon removes incorrect addon > ------------------------------------ > > Key: FORGE-1489 > URL: https://issues.jboss.org/browse/FORGE-1489 > Project: Forge > Issue Type: Feature Request > Components: Plugin Repository > Affects Versions: 2.0.0.CR1 > Reporter: Tom Cunningham > Priority: Blocker > Fix For: 2.x Future > > Attachments: Graphic1.jpg, Graphic2.jpg > > > I've been installing two addons off and on and noticed that when I choose "Remove Addon" in the forge menu, one of my addons is selected for removal by default (see Graphic1). I unselect it, select my other addon (see Graphic2), but the first addon that was selected by default is removed and the addon that I selected is kept. -- 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