[JBoss JIRA] (FORGE-2297) Support newer versions of Gradle
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2297?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2297:
-----------------------------------
Component/s: Build Tools - Gradle
> Support newer versions of Gradle
> --------------------------------
>
> Key: FORGE-2297
> URL: https://issues.jboss.org/browse/FORGE-2297
> Project: Forge
> Issue Type: Bug
> Components: Addon Development, Build Tools - Gradle
> Reporter: Rick Suggs
>
> Hello,
> I've found some great potential with this tool, but I am wondering if there is any plan to support newer versions of Gradle?
> On MacOSX I set my GRADLE_HOME env variable to an installation of gradle 2.3, and after following the sequence to create a new project, several exceptions were thrown. The same exceptions did not occur with the default installation of Gradle that comes with Forge.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (FORGE-2297) Support newer versions of Gradle
by Rick Suggs (JIRA)
Rick Suggs created FORGE-2297:
---------------------------------
Summary: Support newer versions of Gradle
Key: FORGE-2297
URL: https://issues.jboss.org/browse/FORGE-2297
Project: Forge
Issue Type: Bug
Components: Addon Development
Reporter: Rick Suggs
Hello,
I've found some great potential with this tool, but I am wondering if there is any plan to support newer versions of Gradle?
On MacOSX I set my GRADLE_HOME env variable to an installation of gradle 2.3, and after following the sequence to create a new project, several exceptions were thrown. The same exceptions did not occur with the default installation of Gradle that comes with Forge.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (FORGE-2268) allow wizards in the CLI to let the user configure non-required inputs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2268?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2268.
----------------------------------
Resolution: Done
> allow wizards in the CLI to let the user configure non-required inputs
> ----------------------------------------------------------------------
>
> Key: FORGE-2268
> URL: https://issues.jboss.org/browse/FORGE-2268
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.15.2.Final
> Reporter: James Strachan
> Assignee: George Gastaldi
> Fix For: 2.15.3.Final
>
>
> we're creating wizards for creating new camel components and endpoints. Pretty much all of these have a large number of possible input properties. However most of them are not required.
> I've hacked a multi-page wizard; the 2nd page adds all the non-required inputs to the builder. The CLI then ignores them all and accepts the default values ;)
> It would be nice if there a way prompt the user with something like...
> {code}
> Would you like to change any of the 12 inputs [Yn]:
> Y
> [1] foo
> [2] bar
> ...
> [12] thingy...
> 2
> enter the value for property bar with default value [123] :
> 456
> property bar set to 456
> Would you like to change any of the 12 inputs [Yn]:
> (repeat until n)
> {code}
> i.e. folks can just hit an extra enter to not bother entering any values, or they can keep hitting 'y' then picking the number of the input to change, then the value and enter
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (FORGE-2268) allow wizards in the CLI to let the user configure non-required inputs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2268?page=com.atlassian.jira.plugin... ]
George Gastaldi edited comment on FORGE-2268 at 3/26/15 12:31 PM:
------------------------------------------------------------------
Fixed in the master branch·
The solution is to explicitly set the {{setPromptInInteractiveMode}} for the {{InputComponent}} in the associated {{HintsFacet}} as in the example below:
{code:java}
UIInput<String> input = ...;
// This will always prompt, regardless if there is a value set
input.getFacet(HintsFacet.class).setPromptInInteractiveMode(true);
{code}
was (Author: gastaldi):
Fixed in the master branch·
The solution is to explicitly set the {{setPromptInInteractiveMode}} for the {{InputComponent}} in the associated {{HintsFacet}} as in the example below:
{code:java}
UIInput<String> input = ...;
// This will always prompt, regardless if there is a value set input.getFacet(HintsFacet.class).setPromptInInteractiveMode(true);
{code}
> allow wizards in the CLI to let the user configure non-required inputs
> ----------------------------------------------------------------------
>
> Key: FORGE-2268
> URL: https://issues.jboss.org/browse/FORGE-2268
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.15.2.Final
> Reporter: James Strachan
> Assignee: George Gastaldi
> Fix For: 2.15.3.Final
>
>
> we're creating wizards for creating new camel components and endpoints. Pretty much all of these have a large number of possible input properties. However most of them are not required.
> I've hacked a multi-page wizard; the 2nd page adds all the non-required inputs to the builder. The CLI then ignores them all and accepts the default values ;)
> It would be nice if there a way prompt the user with something like...
> {code}
> Would you like to change any of the 12 inputs [Yn]:
> Y
> [1] foo
> [2] bar
> ...
> [12] thingy...
> 2
> enter the value for property bar with default value [123] :
> 456
> property bar set to 456
> Would you like to change any of the 12 inputs [Yn]:
> (repeat until n)
> {code}
> i.e. folks can just hit an extra enter to not bother entering any values, or they can keep hitting 'y' then picking the number of the input to change, then the value and enter
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (FORGE-2268) allow wizards in the CLI to let the user configure non-required inputs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2268?page=com.atlassian.jira.plugin... ]
George Gastaldi reopened FORGE-2268:
------------------------------------
> allow wizards in the CLI to let the user configure non-required inputs
> ----------------------------------------------------------------------
>
> Key: FORGE-2268
> URL: https://issues.jboss.org/browse/FORGE-2268
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.15.2.Final
> Reporter: James Strachan
> Assignee: George Gastaldi
> Fix For: 2.15.3.Final
>
>
> we're creating wizards for creating new camel components and endpoints. Pretty much all of these have a large number of possible input properties. However most of them are not required.
> I've hacked a multi-page wizard; the 2nd page adds all the non-required inputs to the builder. The CLI then ignores them all and accepts the default values ;)
> It would be nice if there a way prompt the user with something like...
> {code}
> Would you like to change any of the 12 inputs [Yn]:
> Y
> [1] foo
> [2] bar
> ...
> [12] thingy...
> 2
> enter the value for property bar with default value [123] :
> 456
> property bar set to 456
> Would you like to change any of the 12 inputs [Yn]:
> (repeat until n)
> {code}
> i.e. folks can just hit an extra enter to not bother entering any values, or they can keep hitting 'y' then picking the number of the input to change, then the value and enter
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (FORGE-2268) allow wizards in the CLI to let the user configure non-required inputs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2268?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2268.
----------------------------------
Resolution: Done
Fixed in the master branch·
The solution is to explicitly set the {{setPromptInInteractiveMode}} for the {{InputComponent}} in the associated {{HintsFacet}} as in the example below:
{code:java}
UIInput<String> input = ...;
// This will always prompt, regardless if there is a value set input.getFacet(HintsFacet.class).setPromptInInteractiveMode(true);
{code}
> allow wizards in the CLI to let the user configure non-required inputs
> ----------------------------------------------------------------------
>
> Key: FORGE-2268
> URL: https://issues.jboss.org/browse/FORGE-2268
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.15.2.Final
> Reporter: James Strachan
> Assignee: George Gastaldi
> Fix For: 2.15.3.Final
>
>
> we're creating wizards for creating new camel components and endpoints. Pretty much all of these have a large number of possible input properties. However most of them are not required.
> I've hacked a multi-page wizard; the 2nd page adds all the non-required inputs to the builder. The CLI then ignores them all and accepts the default values ;)
> It would be nice if there a way prompt the user with something like...
> {code}
> Would you like to change any of the 12 inputs [Yn]:
> Y
> [1] foo
> [2] bar
> ...
> [12] thingy...
> 2
> enter the value for property bar with default value [123] :
> 456
> property bar set to 456
> Would you like to change any of the 12 inputs [Yn]:
> (repeat until n)
> {code}
> i.e. folks can just hit an extra enter to not bother entering any values, or they can keep hitting 'y' then picking the number of the input to change, then the value and enter
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (FORGE-2268) allow wizards in the CLI to let the user configure non-required inputs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2268?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2268:
-----------------------------------
Affects Version/s: 2.15.2.Final
> allow wizards in the CLI to let the user configure non-required inputs
> ----------------------------------------------------------------------
>
> Key: FORGE-2268
> URL: https://issues.jboss.org/browse/FORGE-2268
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.15.2.Final
> Reporter: James Strachan
> Assignee: George Gastaldi
> Fix For: 2.15.3.Final
>
>
> we're creating wizards for creating new camel components and endpoints. Pretty much all of these have a large number of possible input properties. However most of them are not required.
> I've hacked a multi-page wizard; the 2nd page adds all the non-required inputs to the builder. The CLI then ignores them all and accepts the default values ;)
> It would be nice if there a way prompt the user with something like...
> {code}
> Would you like to change any of the 12 inputs [Yn]:
> Y
> [1] foo
> [2] bar
> ...
> [12] thingy...
> 2
> enter the value for property bar with default value [123] :
> 456
> property bar set to 456
> Would you like to change any of the 12 inputs [Yn]:
> (repeat until n)
> {code}
> i.e. folks can just hit an extra enter to not bother entering any values, or they can keep hitting 'y' then picking the number of the input to change, then the value and enter
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (FORGE-2268) allow wizards in the CLI to let the user configure non-required inputs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2268?page=com.atlassian.jira.plugin... ]
George Gastaldi updated FORGE-2268:
-----------------------------------
Fix Version/s: 2.15.3.Final
> allow wizards in the CLI to let the user configure non-required inputs
> ----------------------------------------------------------------------
>
> Key: FORGE-2268
> URL: https://issues.jboss.org/browse/FORGE-2268
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.15.2.Final
> Reporter: James Strachan
> Assignee: George Gastaldi
> Fix For: 2.15.3.Final
>
>
> we're creating wizards for creating new camel components and endpoints. Pretty much all of these have a large number of possible input properties. However most of them are not required.
> I've hacked a multi-page wizard; the 2nd page adds all the non-required inputs to the builder. The CLI then ignores them all and accepts the default values ;)
> It would be nice if there a way prompt the user with something like...
> {code}
> Would you like to change any of the 12 inputs [Yn]:
> Y
> [1] foo
> [2] bar
> ...
> [12] thingy...
> 2
> enter the value for property bar with default value [123] :
> 456
> property bar set to 456
> Would you like to change any of the 12 inputs [Yn]:
> (repeat until n)
> {code}
> i.e. folks can just hit an extra enter to not bother entering any values, or they can keep hitting 'y' then picking the number of the input to change, then the value and enter
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months
[JBoss JIRA] (FORGE-2268) allow wizards in the CLI to let the user configure non-required inputs
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2268?page=com.atlassian.jira.plugin... ]
Work on FORGE-2268 started by George Gastaldi.
----------------------------------------------
> allow wizards in the CLI to let the user configure non-required inputs
> ----------------------------------------------------------------------
>
> Key: FORGE-2268
> URL: https://issues.jboss.org/browse/FORGE-2268
> Project: Forge
> Issue Type: Feature Request
> Affects Versions: 2.15.2.Final
> Reporter: James Strachan
> Assignee: George Gastaldi
> Fix For: 2.15.3.Final
>
>
> we're creating wizards for creating new camel components and endpoints. Pretty much all of these have a large number of possible input properties. However most of them are not required.
> I've hacked a multi-page wizard; the 2nd page adds all the non-required inputs to the builder. The CLI then ignores them all and accepts the default values ;)
> It would be nice if there a way prompt the user with something like...
> {code}
> Would you like to change any of the 12 inputs [Yn]:
> Y
> [1] foo
> [2] bar
> ...
> [12] thingy...
> 2
> enter the value for property bar with default value [123] :
> 456
> property bar set to 456
> Would you like to change any of the 12 inputs [Yn]:
> (repeat until n)
> {code}
> i.e. folks can just hit an extra enter to not bother entering any values, or they can keep hitting 'y' then picking the number of the input to change, then the value and enter
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 9 months