Nice!<br><br><div class="gmail_quote">On Tue, Oct 16, 2012 at 5:26 PM, William DeCoste <span dir="ltr"><<a href="mailto:wdecoste@redhat.com" target="_blank">wdecoste@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
This is what the java client used to use, but was removed when we
moved to the new REST api.<div><div class="h5"><br>
<br>
<div>On 10/16/12 2:28 PM, Rafael Benevides
wrote:<br>
</div>
<blockquote type="cite">
Hi guys.<br>
<br>
Tail implemented using Jsch. Thanks #jbosstools guys for the help!<br>
<br>
Em 11-10-2012 16:24, Xavier Coulon escreveu:
<blockquote type="cite">Raphael,
<div><br>
</div>
<div>You probably need to implement your own UserInfo as shown
in this example: <a href="http://www.jcraft.com/jsch/examples/Exec.java.html" target="_blank">http://www.jcraft.com/jsch/examples/Exec.java.html</a></div>
<div>This is also one of the reason our "tail" code is in the
Eclipse plugin and not in the client-library: we can plug into
Eclipse SSH2 Key management infrastructure (eg: SSH2 Key
preferences, passpharse prompt dialog, etc..). Since you're
going towards a full CLI-based approach, you'll certainly need
to look at the user's private key(s) and prompt its
passphrase. The jcraft website has some good example how
UserInfo implementations.</div>
<div><br>
</div>
<div>HTH</div>
<div>Best regards, </div>
<div>
<div> /Xavier<br>
<br>
<br>
</div>
<br>
<div>
<div>On Oct 11, 2012, at 5:49 PM, Rafael Benevides wrote:</div>
<br>
<blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000"> <br>
The first impl was command line based. Now I reopened
<a href="https://issues.jboss.org/browse/FORGEPLUGINS-91" target="_blank">https://issues.jboss.org/browse/FORGEPLUGINS-91</a>
so I'm changing the impl to use jsch.<br>
<br>
I'm facing problems with "auth fail" and public-key
authentication. Do you guys have any clue ?! It's the
first time I'm using jgit/jsch API so I still searching
how to do it.<br>
<br>
Em 11-10-2012 12:31, Max Rydahl Andersen escreveu:
<blockquote type="cite">
<pre>there should be *zero* need to use ssh command lines for this stuff. jsch is sufficient afaik.
/max
On 11 Oct 2012, at 16:00, Rafael Benevides <a href="mailto:rafabene@gmail.com" target="_blank"><rafabene@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre>Lincoln,
Never mind the comment below. ssh.exe comes with the most basic git installation on windows. Anyway I think that there won't be a problem with Windows.
2012/10/10 Rafael Benevides <a href="mailto:rafabene@gmail.com" target="_blank"><rafabene@gmail.com></a>
Lincoln.
I've run git installation on Windows (like suggested on Installing Forge Guide) and now I choose to install Unix tools on Windows
Unix tools comes with ssh and it worked pretty well.
Maybe we can update the forge installation guide (<a href="http://forge.jboss.org/docs/using/" target="_blank">http://forge.jboss.org/docs/using/</a>) to suggest installation of Unix tools when installing Git. It will not only reduce issues with this plugin, but maybe with many others possible issues with other plugins.
2012/10/10 Rafael Benevides <a href="mailto:rafabene@gmail.com" target="_blank"><rafabene@gmail.com></a>
I've just tested plink.exe from <a href="http://www.chiark.greenend.org.uk/%7Esgtatham/putty/download.html" target="_blank">http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html</a> and it worked on Windows environment.
openshift plugin can propose its installation if NativeSystemCall returns an error on Windows Environment. What you think ?
2012/10/10 Rafael Benevides <a href="mailto:rafabene@gmail.com" target="_blank"><rafabene@gmail.com></a>
Good question!
I was just investigating a solution for Windows environment.
2012/10/10 Lincoln Baxter, III <a href="mailto:lincolnbaxter@gmail.com" target="_blank"><lincolnbaxter@gmail.com></a>
Isn't the current JBoss Tools way of doing this OS-specific? E.g. The user would need to have openSSH installed in windows to make this work? Or is that assumed?
~Lincoln
On Wed, Oct 10, 2012 at 12:00 PM, William DeCoste <a href="mailto:wdecoste@redhat.com" target="_blank"><wdecoste@redhat.com></a> wrote:
Unfortunately not yet. The REST API does not expose this feature yet. It's on the roadmap. It will probably be exposed as status.
On 10/10/12 9:01 AM, Rafael Benevides wrote:
</pre>
<blockquote type="cite">
<pre>Bill / Andre / Xavier
I didn't find on openshift-java-client how to tail files.
Does it have this feature ?
Thanks
Em 04-10-2012 10:24, Xavier Coulon escreveu:
</pre>
<blockquote type="cite">
<pre>Hi !
As Max mentioned, you should find all the API you need to implement the features listed below in the Forge plugin in the new openshift-java-client (V2.0), except maybe the 'tail files' feature which we implemented in JBossTools because we use specific Eclipse APIs to display the output in a MessageConsole. Maybe this could be refactored and moved partially into the java-client library, though (we did not need to do that when we worked on it a few months ago).
Also, if you haven't already seen it, André recently wrote an article about the new client library: <a href="https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-openshift-java-client-in-a-nutshell" target="_blank">https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-openshift-java-client-in-a-nutshell</a>
Best regards,
/Xavier
On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre>So I just started working on EAP support. <a href="https://issues.jboss.org/browse/FORGEPLUGINS-88" target="_blank">https://issues.jboss.org/browse/FORGEPLUGINS-88</a> opened!
</pre>
</blockquote>
<pre>Oh I was wondering why EAP wasn't supported.
Didn't realize the forge openshift install was jboss specific.
One item I got is that we check if the projects setup by JBoss Tools, openshift client and OpenShift Forge client are compatible or can be made compatible.
i.e. forge *always* uses "openshift" as the remote afaik - openshift client always create projects where the remote is in "origin" - as a consequence jboss tools
added support for naming the remote used so you could align them.
If openshift could allow naming the remote or pick up the existing remote pointing to openshift these things could be aligned.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre>Pete and Lincoln talked about some of them in JavaOne here are some:
* support for embedding cartridges
* support for eap
* tail files
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre>all of the above is available for use from the new openshift client.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre>I also got those:
* setup when openshift application exists
* snapshot management ?
* key management ?
* alias management
* enable scaling on create app ?
* Use alternate openshift config file
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre>whats this one ?
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre> * config port forward ?
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre>we got this in jbosstools - for forge I guess it requires running a jsch port forward (or launch ssh native in separate process) ?
/max
_______________________________________________
forge-dev mailing list
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a>
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre>--
Bill DeCoste
Principal Software Engineer, Red Hat
<a href="tel:978-204-0920" value="+19782040920" target="_blank">978-204-0920</a>
<a href="mailto:wdecoste@redhat.com" target="_blank">wdecoste@redhat.com</a>
_______________________________________________
forge-dev mailing list
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a>
--
Lincoln Baxter, III
<a href="http://ocpsoft.org/" target="_blank">http://ocpsoft.org</a>
"Simpler is better."
_______________________________________________
forge-dev mailing list
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a>
_______________________________________________
forge-dev mailing list
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a>
</pre>
</blockquote>
</blockquote>
</div>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</blockquote>
<br>
<pre cols="72">--
Bill DeCoste
Principal Software Engineer, Red Hat
<a href="tel:978-204-0920" value="+19782040920" target="_blank">978-204-0920</a>
<a href="mailto:wdecoste@redhat.com" target="_blank">wdecoste@redhat.com</a>
</pre>
</div></div></div>
<br>_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>"Simpler is better."<br>