obr/sling.xml

[Stefan Egli <st...@apache.org>]

Hi,

I just tried to follow the release process steps and noticed when updating
the obr/sling.xml, that it hasn't been done so for quite a while (2.5
years). So I'm not sure what the idea with this is, but I guess we should
update it.

Also, when trying to do a 'svn up' on people.apache.org, I got the
following:

stefanegli@minotaur:/x1/www/sling.apache.org/content/obr$ svn up
svn: E155004: Working copy '/x1/www/sling.apache.org/content' locked
svn: E200031: sqlite: attempt to write a readonly database
svn: E200031: sqlite: attempt to write a readonly database
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)

I'm uncertain if doing a 'svn cleanup' there does not have any
side-effects.. :S

Anyone familiar with the setup there?

Cheers,
Stefan

Re: obr/sling.xml

[Carsten Ziegeler <cz...@apache.org>]

The instructions were predating the CMS for our site, I've updated and
verified the instructions - so there is no excuse anymore to update the OBR
:)

Regards
Carsten


2014-07-22 15:32 GMT+02:00 Carsten Ziegeler <cz...@apache.org>:

> Thanks for bringing this up, Stefan - we definitely should invest some
> time and bring the repository xml up to date. A repository is one of the
> key concepts in the OSGi world and we should provide a repo with our Sling
> stuff. That's why this has been listed on the instructions :)
> But - mea culpa - I'm guilty of not following that step as well :( But I'm
> interested in bringing it back on
>
> Carsten
>
>
> 2014-07-22 10:49 GMT+02:00 Bertrand Delacretaz <bd...@apache.org>:
>
> Hi Stefan,
>>
>> On Tue, Jul 22, 2014 at 10:47 AM, Stefan Egli <st...@apache.org>
>> wrote:
>> > ...I just tried to follow the release process steps and noticed when
>> updating
>> > the obr/sling.xml, that it hasn't been done so for quite a while (2.5
>> > years)...
>>
>> This seems to prove that nobody is using that feature - we might as
>> well drop the file to make that clear?
>>
>> > Also, when trying to do a 'svn up' on people.apache.org, I got the
>> > following:
>> ...
>> > svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
>> details)
>> ...
>>
>> That only touches your local sandbox - if you check with svn stat /
>> svn diff what you are about to commit you can see exactly what will
>> happen.
>>
>> -Bertrand
>>
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziegeler@apache.org
>



-- 
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org

Re: obr/sling.xml

[Carsten Ziegeler <cz...@apache.org>]

Thanks for bringing this up, Stefan - we definitely should invest some time
and bring the repository xml up to date. A repository is one of the key
concepts in the OSGi world and we should provide a repo with our Sling
stuff. That's why this has been listed on the instructions :)
But - mea culpa - I'm guilty of not following that step as well :( But I'm
interested in bringing it back on

Carsten


2014-07-22 10:49 GMT+02:00 Bertrand Delacretaz <bd...@apache.org>:

> Hi Stefan,
>
> On Tue, Jul 22, 2014 at 10:47 AM, Stefan Egli <st...@apache.org>
> wrote:
> > ...I just tried to follow the release process steps and noticed when
> updating
> > the obr/sling.xml, that it hasn't been done so for quite a while (2.5
> > years)...
>
> This seems to prove that nobody is using that feature - we might as
> well drop the file to make that clear?
>
> > Also, when trying to do a 'svn up' on people.apache.org, I got the
> > following:
> ...
> > svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
> details)
> ...
>
> That only touches your local sandbox - if you check with svn stat /
> svn diff what you are about to commit you can see exactly what will
> happen.
>
> -Bertrand
>



-- 
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org

Re: obr/sling.xml

[Bertrand Delacretaz <bd...@apache.org>]

Hi Stefan,

On Tue, Jul 22, 2014 at 10:47 AM, Stefan Egli <st...@apache.org> wrote:
> ...I just tried to follow the release process steps and noticed when updating
> the obr/sling.xml, that it hasn't been done so for quite a while (2.5
> years)...

This seems to prove that nobody is using that feature - we might as
well drop the file to make that clear?

> Also, when trying to do a 'svn up' on people.apache.org, I got the
> following:
...
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
...

That only touches your local sandbox - if you check with svn stat /
svn diff what you are about to commit you can see exactly what will
happen.

-Bertrand