Re: [ease-dev] Introduction

[Utsav Oza <utsavoza96@xxxxxxxxx>]

Hello,

What scripts shoud we test our implementation against in each case i.e for GitHub, Git/Gerrit and SVN repositories ? Since we would have to provide unit tests, we would require to have sample scripts in each of the these repositories. There is currently a Git repository that hosts EASE sample scripts. Are there any EASE repositories on GitHub and SVN that hosts sample scripts in order to provide unit tests for their parsers ?

Thanks

Utsav Oza 

On Thu, Mar 16, 2017 at 11:44 PM, Christian Pontesegger <christian.pontesegger@xxxxxx> wrote:

Have a look at the existing implementations for Script location parsers. We already store timestamps of local files as an indicator when to update them. Storing hashes instead will work with minimal effort. The whole mechanism of persisting that kind of data is already handled, you do not need to care about this.


Christian


On 16.03.2017 15:54, Utsav Oza wrote:

Hi,

Since we are going to need to compare commit hashes of the cached scripts with the remote scripts, we would require a way to persist and maintain previously fetched commit hashes of the scripts locally. Eclipse does provide means of persisting preferences, application models, widget states etc.but I am not sure about how to persist external data (i.e metadata we obtain for the scripts). What ways can we consider for this purpose ?

_______________________________________________
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