[JBoss JIRA] (FORGE-1441) new-project --createMain is missing
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1441:
----------------------------------------
Summary: new-project --createMain is missing
Key: FORGE-1441
URL: https://issues.jboss.org/browse/FORGE-1441
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.x Future
Reporter: Antonio Goncalves
I got used to be able to quickly create a project with a {{Main}} class. The {{--createMain}} parameter is a must have
--
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, 3 months
[JBoss JIRA] (FORGE-1440) TAB on export repeats ACCEPT_DEFAULTS
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1440:
----------------------------------------
Summary: TAB on export repeats ACCEPT_DEFAULTS
Key: FORGE-1440
URL: https://issues.jboss.org/browse/FORGE-1440
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.0.0.Beta4
Reporter: Antonio Goncalves
Fix For: 2.x Future
When I hit TAB continuously on the {{export}} command, it just adds {{ACCEPT_DEFAULTS}} indefinitely :
{code}
[forge2s]$ ex
export exit
[forge2s]$ export DEFAULTS= ACCEPT_DEFAULTS ACCEPT_DEFAULTS ACCEPT_DEFAULTS ACCEPT_DEFAULTS ACCEPT_DEFAULTS
{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, 3 months
[JBoss JIRA] (FORGE-1436) help command is missing
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1436?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1436.
----------------------------------
Fix Version/s: (was: 2.x Future)
Resolution: Won't Fix
help was replaced by man
> help command is missing
> -----------------------
>
> Key: FORGE-1436
> URL: https://issues.jboss.org/browse/FORGE-1436
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
>
> I find this one usefull and it could even add more content (such as mentioning the {{man}} command...
> {code}
> [no project] Forge $ help
> Welcome to JBoss Forge, a next-generation interactive Shell and project-generation tool. If you find yourself lost, or uncertain how to complete an operation, you may press the <TAB> key for command-completion, or <TAB><TAB> for hints while typing a command.
> Type 'list-commands' for a list of available commands in the current Resource context.
> You are not working on a project. Type 'help new-project' to get started.
> {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, 3 months
[JBoss JIRA] (FORGE-1422) REST addon should support generation of exception mappers for validation errors
by Emmanuel Bernard (JIRA)
[ https://issues.jboss.org/browse/FORGE-1422?page=com.atlassian.jira.plugin... ]
Emmanuel Bernard commented on FORGE-1422:
-----------------------------------------
This work has already been done in RESTEasy by [~ron_sigal].
Let's at least align on the way we report error. Something I don't understand is that you have a REST service but don't sue RESTEasy?
> REST addon should support generation of exception mappers for validation errors
> -------------------------------------------------------------------------------
>
> Key: FORGE-1422
> URL: https://issues.jboss.org/browse/FORGE-1422
> Project: Forge
> Issue Type: Feature Request
> Components: Builtin Plugins
> Affects Versions: 2.0.0.Beta4
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
>
> Currently a HTTP 500 response is generated for validation errors encountered during processing of POST/PUT requests that create or update JPA entities. The 500 response contains a stacktrace that cannot be parsed by clients to evaluate what failed.
> We should generate exception mappers that can map Bean validation errors to help generate parseable responses (for the REST clients).
--
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, 3 months
[JBoss JIRA] (FORGE-1439) Verbose output is missing
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1439:
----------------------------------------
Summary: Verbose output is missing
Key: FORGE-1439
URL: https://issues.jboss.org/browse/FORGE-1439
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.0.0.Beta4
Reporter: Antonio Goncalves
Fix For: 2.x Future
This might have a different setting in Forge 2.x, but I really miss having a verbose output of my commands. In Forge 1.x I have the following :
{code}
[no project] Forge $ new-project --named forge1 --topLevelPackage org.forge1.test --type war --finalName toto
***SUCCESS*** Created project [forge1] in new working directory [/Users/antoniombp/Documents/Code/temp/Forge/forge1]
Wrote /Users/antoniombp/Documents/Code/temp/Forge/forge1
Wrote /Users/antoniombp/Documents/Code/temp/Forge/forge1/pom.xml
Wrote /Users/antoniombp/Documents/Code/temp/Forge/forge1/src/main/webapp
Wrote /Users/antoniombp/Documents/Code/temp/Forge/forge1/src/main/java
Wrote /Users/antoniombp/Documents/Code/temp/Forge/forge1/src/test/java
Wrote /Users/antoniombp/Documents/Code/temp/Forge/forge1/src/main/resources
Wrote /Users/antoniombp/Documents/Code/temp/Forge/forge1/src/test/resources
Wrote /Users/antoniombp/Documents/Code/temp/Forge/forge1/src/main/java/org/forge1/test
{code}
And in Forge 2.Beta I only have
{code}
[Forge]$ project-new --named forge2 --topLevelPackage org.forge2.test --type war
***SUCCESS*** Project named 'forge2' has been created.
{code}
As a geek (and Forge is made for geeks), it really helps to see what's happening. Again, that might be a new setting in Forge 2.Beta that I'm not aware off.
--
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, 3 months
[JBoss JIRA] (FORGE-1438) new-project --finalName is missing
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1438:
----------------------------------------
Summary: new-project --finalName is missing
Key: FORGE-1438
URL: https://issues.jboss.org/browse/FORGE-1438
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.0.0.Beta4
Reporter: Antonio Goncalves
Fix For: 2.x Future
{{--finalName}} is very handy because it changes the {{<finalName>}} element in Maven
--
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, 3 months
[JBoss JIRA] (FORGE-1437) project-new --type jar-resources is confusing
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1437:
----------------------------------------
Summary: project-new --type jar-resources is confusing
Key: FORGE-1437
URL: https://issues.jboss.org/browse/FORGE-1437
Project: Forge
Issue Type: Sub-task
Components: UI - Shell
Affects Versions: 2.0.0.Beta4
Reporter: Antonio Goncalves
Fix For: 2.x Future
I was used to {{jar}} so {{jar-resources}} is confusing. Is it a different thing ?
{code}
[Forge]$ project-new --named forge2 --topLevelPackage org.forge2.test --type
jar war addon jar-resources
{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, 3 months
[JBoss JIRA] (FORGE-1435) about command is missing
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1435?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1435.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.0.0.Final
(was: 2.x Future)
Resolution: Done
> about command is missing
> ------------------------
>
> Key: FORGE-1435
> URL: https://issues.jboss.org/browse/FORGE-1435
> 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
>
>
> Never really make the difference between {{version}} and {{about}} but I got used to it :
> {code}
> [no project] Forge $ about
> _____
> | ___|__ _ __ __ _ ___
> | |_ / _ \| `__/ _` |/ _ \ \\
> | _| (_) | | | (_| | __/ //
> |_| \___/|_| \__, |\___|
> |___/
> JBoss Forge, version [ 1.4.3.Final ] - JBoss, by Red Hat, Inc. [ http://forge.jboss.org ]
> {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, 3 months