8:52 p.m.
I believe it goes under Forge plugins. However IMHO, it should be on core.
Lincoln, WDYT ?
Regards.
George Gastaldi
Em 02/05/2012, às 22:49, Keith Babo <kbabo(a)redhat.com> escreveu:
Sure, does it go in Forge or Forge Plugins ?
~ keith
On May 2, 2012, at 9:39 PM, George Gastaldi wrote:
Sounds awesome ! May I kindly ask you to file a Jira about it ?
Forge rocks ! :)
Em 02/05/2012, às 22:25, Keith Babo <kbabo(a)redhat.com> escreveu:
No worries. :-)
I would find a command history to be useful in the following situations:
- I want to know the context when I entered a given command, e.g. I did,
a, b, then c
- Someone asks me for the list of commands I used to get to a certain state
in a project
- Similar to prior use case, but use the history to create a script file
that can be executed
- I entered something 15 commands ago and I don't feel like using up arrow
to go find it :-)
cheers,
keith
On May 2, 2012, at 9:02 PM, Lincoln Baxter, III wrote:
Hmmm, sorry for the late reply.
We don't have a "history" command, but why would you need it? Not that
I'm
against it at all!
~Lincoln
On Wed, Apr 25, 2012 at 7:15 AM, Keith Babo < <kbabo(a)redhat.com>
kbabo(a)redhat.com> wrote:
Oh, snap. That's nice. I can definitely see some interesting
possibilities bubbling out from here.
In terms of how we've done things now, there are still a few things I'l
like to change. First, we package all of our independent plugins into a
single module for installation into Forge. We need to change that for this
release of SwitchYard. Once we have that in place, we can look at how the
plugin could be pulled down directly from a Maven repository instead of
copying directly into ~/.forge/plugins (which is what I think we do today).
BTW, is there a "history" command in Forge right now? I noticed there is
a ~/.forge/cmd_history file, but I didn't see a command which actually
lists the content of that file from within forge itself. You can use the
arrow keys to navigate in command history, so I'm sure this is being read
for that.
cheers,
keith
On Apr 25, 2012, at 10:10 AM, Lincoln Baxter, III wrote:
Hey Keith!
Regarding instaling plugins from Maven - we'd definitely like to support
this. Perhaps we could take what you've done and standardize it as a
supported plugin installation mechanism?
Regarding testing the plugins in a forge release distribution. As of Forge
1.0.3.Final, you can invoke Forge from the command line using:
forge -e "command or script to run"
So hopefully that will be of use :) You can install plugins using this
feature as well, so with the combination of the two, we should have some
good testing options!
--
Lincoln Baxter, III
<http://ocpsoft.org/>http://ocpsoft.org
"Simpler is better."
--
Lincoln Baxter, III
<http://ocpsoft.org/>http://ocpsoft.org
"Simpler is better."
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev