[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 commented on FORGE-1499:
-------------------------------------------
I think I disagree with this. a "Resource" is the thing you are retrieving. Accessed via a URL (Uniform *Resource* Locator). The Endpoint is what serves the resource at the specified URL. Please re-open if you disagree strongly.
> 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
[JBoss JIRA] (FORGE-1461) "project-new" command fails while a ResourceTransaction is active
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1461?page=com.atlassian.jira.plugin... ]
George Gastaldi reassigned FORGE-1461:
--------------------------------------
Assignee: George Gastaldi
> "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
> Assignee: George Gastaldi
> 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
[JBoss JIRA] (FORGE-1495) Group or order related command parameters across wizard steps for the Shell UI
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1495?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III updated FORGE-1495:
--------------------------------------
Fix Version/s: 2.x Future
> Group or order related command parameters across wizard steps for the Shell UI
> ------------------------------------------------------------------------------
>
> Key: FORGE-1495
> URL: https://issues.jboss.org/browse/FORGE-1495
> Project: Forge
> Issue Type: Feature Request
> Components: UI - Shell
> Affects Versions: 2.0.0.CR1
> Reporter: Vineet Reynolds
> Priority: Minor
> Fix For: 2.x Future
>
>
> Command parameters from all commands participating in a wizard are coalesced together. This becomes less intuitive when a large number of parameters are listed, especially in the parameter auto-complete list, like so:
> {noformat}
> [helloworld]$ scaffold-setup
> --facesVersion --container --ejbVersion --cdiVersion --provider --dbType --jpaVersion
> --configureMetadata --overwrite --target --servletVersion --persistenceUnitName --dataSourceName
> {noformat}
> It would be beneficial to group related command parameters together. Some ways to group related commands would be to use rows (with each row grouping related command parameters) or separate Shell colors (a separate color for a command parameter group), or a combination of both.
--
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
[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 reassigned FORGE-1384:
-----------------------------------------
Assignee: Koen Aers
> 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
> Assignee: Koen Aers
> Priority: Blocker
> 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
[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:
--------------------------------------
Priority: Blocker (was: Major)
> 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
> Priority: Blocker
> 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