If you're suggesting that the --bom CommandCompleter dynamically change its
allowed values based on the selection of --runtime, then I agree. +1
On Fri, Sep 28, 2012 at 9:37 AM, Pete Muir <pmuir(a)redhat.com> wrote:
+1
On 26 Sep 2012, at 18:53, Jason Porter wrote:
> +1
>
> ----- Original Message -----
>> From: "Rafael Benevides" <benevides(a)redhat.com>
>> To: jdf-dev(a)lists.jboss.org, "forge-dev List" <
forge-dev(a)lists.jboss.org>, "Pete Muir" <pmuir(a)redhat.com>,
"George
>> Gastaldi" <gegastaldi(a)gmail.com>, "Lincoln Baxter"
<lbaxter(a)redhat.com>
>> Sent: Wednesday, September 26, 2012 11:30:39 AM
>> Subject: [jdf-dev] JDF Forge plugin
>>
>>
>> Hi guys.
>>
>> Today I was talking with George Gastaldi and we discussed about JDF
>> Forge plugin.
http://www.jboss.org/jdf/stack/plugin-jdf/
>>
>> Forge plugin was planned (
>>
https://issues.jboss.org/browse/FORGEPLUGINS-37 ) prior the JBoss
>> Stacks project (
http://www.jboss.org/jdf/stack/stacks/ ) so I think
>> that we could update the JDF Forge plugin to use the Runtimes and
>> Archetypes information too.
>>
>> Today jdf plugin shows all available boms through command completer:
>> jdf use-stack --stack <TAB>
>> I think we should update jdf plugin to use the Runtime to display
>> only the available BOMs/BomVersions from each Runtime:
>> jdf use-stack --runtime jboss-eap-60 --bom <TAB> (change --stack to
>> --bom)
>> Even the Archetype information can be used also to delegate the
>> creation of a project using the correct archetype to that Runtime.
>> Here I'm not sure if it this kind of overwrite is desirable.
>> jdf new-project --runtime jboss-eap-6- --archetype <TAB>
>> What you forge/jdf guys think ?
>>
>>
>> _______________________________________________
>> jdf-dev mailing list
>> jdf-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jdf-dev
>>
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev