Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ease-dev] Introduction
Hello,

Since for Gerrit based repositories the preferred way to obtain scripts would be through Gerrit REST API, should we consider two separate parsers implementation for Git (with cgit web interface) and Gerrit based repositories as the part of the project ? 

Thanks

On Sun, Mar 26, 2017 at 4:25 AM, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
You are correct, there is no standardised web interface for SVN[1].
SVN servers may not be served by http:// (or https://) at all. e.g.
repos with svn:// or svn+ssh:// URLs.

I provide the rest in the hope that it is helpful to you:

The web interface that you linked to not the real (aka full featured)
web interface for svn.apache.org. The real one is
http://svn.apache.org/viewvc/.

Compare:
http://svn.apache.org/repos/asf/abdera/abdera2/README
to:
http://svn.apache.org/viewvc/abdera/abdera2/README


[1] nor for Git for that matter... but I haven't followed every detail
of the conversation so apologies if I am repeating something.
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com


On 25 March 2017 at 19:32, Utsav Oza <utsavoza96@xxxxxxxxx> wrote:
> Hello,
>
> Is there any standardised web interface for SVN repositories ? As far as I
> have know, svn repositories tend to have only hyperlinks (consider this
> example) as a way to interact with the repositories i.e. making it a legit
> for browsing purposes only. I wanted to know whether this applies to all svn
> repositories ? If this is the case then in this project we wouldn't require
> the support from Subversive as we could easily extend HttpParser to look for
> raw content url for scripts. However this would also mean that we would need
> a sample svn repository to test our implementation of the parser. If this
> isn't the case then Subversive would be an obvious choice.
>
> Thanks
> Utsav Oza
>
> On Thu, Mar 23, 2017 at 10:34 PM, Christian Pontesegger
> <christian.pontesegger@xxxxxx> wrote:
>>
>> agreed. We should move to some official repo before we commit to the
>> master branch.
>>
>> Christian
>>
>>
>> On 23.03.2017 14:31, Utsav Oza wrote:
>>>
>>> Thanks Jonah and Christian.
>>>
>>> So before you create a repository in eclipse-ease-addons, it would be
>>> helpful if I create my own repository and host few sample scripts to test my
>>> implementation for both GitHub and SVN out and after your confirmation I can
>>> always send a request to push those scripts to the main repository on
>>> eclipse-ease-addons.
>>>
>>> Utsav Oza
>>>
>>
>> _______________________________________________
>> ease-dev mailing list
>> ease-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/ease-dev
>
>
>
> _______________________________________________
> ease-dev mailing list
> ease-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/ease-dev
_______________________________________________
ease-dev mailing list
ease-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ease-dev

Back to the top