The first impl was command line based. Now I reopened
so I'm changing the impl
to use jsch.
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.
Em 11-10-2012 12:31, Max Rydahl Andersen escreveu:
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<rafabene(a)gmail.com> wrote:
> 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<rafabene(a)gmail.com>
> 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 (
http://forge.jboss.org/docs/using/)
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<rafabene(a)gmail.com>
> I've just tested plink.exe from
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html 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<rafabene(a)gmail.com>
> Good question!
>
> I was just investigating a solution for Windows environment.
>
> 2012/10/10 Lincoln Baxter, III<lincolnbaxter(a)gmail.com>
>
> 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<wdecoste(a)redhat.com> 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:
>> 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:
>>> 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:
https://community.jboss.org/en/tools/blog/2012/08/24/show-domain-info-ope...
>>>
>>> Best regards,
>>> /Xavier
>>>
>>>
>>>
>>> On Oct 4, 2012, at 1:39 PM, Max Rydahl Andersen wrote:
>>>
>>>>> So I just started working on EAP support.
https://issues.jboss.org/browse/FORGEPLUGINS-88 opened!
>>>> 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.
>>>>
>>>>>>> Pete and Lincoln talked about some of them in JavaOne here
are some:
>>>>>>> * support for embedding cartridges
>>>>>>> * support for eap
>>>>>>> * tail files
>>>> all of the above is available for use from the new openshift client.
>>>>
>>>>>>> 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
>>>> whats this one ?
>>>>
>>>>>>> * config port forward ?
>>>> 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
>>>> forge-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/forge-dev
> --
> Bill DeCoste
> Principal Software Engineer, Red Hat
>
> 978-204-0920
> wdecoste(a)redhat.com
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
>
> --
> Lincoln Baxter, III
>
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