You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Rupert Westenthaler <ru...@gmail.com> on 2011/07/27 09:28:37 UTC

Updating Stanbol Version without deleting /sling folder (was: EntityHub and DBpedia)

Hi all

> On Wed, Jul 27, 2011 at 7:54 AM, David Riccitelli
> <da...@interact.it> wrote:
>> Hi Rupert,
>> One question, I can't find this bundle:
>>
>>   - "Apache Stanbol Data: DBpedia.org defaultdata version
>>   (org.apache.stanbol.data.sites.dbpedia.default)"
>>
>>
>> But I see this one:
>>
>>   - "Apache Stanbol Default Data (org.apache.stanbol.defaultdata)"
>>
>> Are you referring to the latter?
>
>No definitely not. This bundle was removed and should no longer be around.
>
> Typically this happens if you update the launcher jar without deleting
> the the /sling folder.
> because within the /sling folder there is a cache with the config and
> the current versions of the bundles.
> If only the launcher jar is replaced, than sling will still startup by
> using this caches and will NOT use the updated bundles and
> configuration from the launcher jar.

We had this several times over the last month and it was also a common
problem during the hackaton in Paris.

I would be really interested if there are more elegant solutions how
to update to an newer Stanbol version than replacing the launcher JAR
and deleting the "/sling" folder.

This is espacially a bad thing if you have already a lot of
configurations (e.g. Referenced Sites, local caches ...).

Any Ideas?

best
Rupert

-- 
| Rupert Westenthaler             rupert.westenthaler@gmail.com
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

Re: Updating Stanbol Version without deleting /sling folder (was: EntityHub and DBpedia)

Posted by Bertrand Delacretaz <bd...@apache.org>.
On Wed, Jul 27, 2011 at 9:37 AM, David Riccitelli
<da...@interact.it> wrote:
> In my recent case, the sling folder was new. But I had to make a clean
> check-out from svn instead of svn up.
>
> I don't know if that makes sense...

Having an extra bundle after svn up, delete ./sling working folder and
full rebuild probably means you had extra code in your local svn
sandbox, that's not in the stanbol svn anymore. "svn stat" would tell
you if that's the case.

-Bertrand

Re: Updating Stanbol Version without deleting /sling folder (was: EntityHub and DBpedia)

Posted by David Riccitelli <da...@interact.it>.
In my recent case, the sling folder was new. But I had to make a clean
check-out from svn instead of svn up.

I don't know if that makes sense...

BR
David

On Wed, Jul 27, 2011 at 10:35 AM, Bertrand Delacretaz <
bdelacretaz@apache.org> wrote:

> Hi,
>
> On Wed, Jul 27, 2011 at 9:28 AM, Rupert Westenthaler
> <ru...@gmail.com> wrote:
> > ...I would be really interested if there are more elegant solutions how
> > to update to an newer Stanbol version than replacing the launcher JAR
> > and deleting the "/sling" folder.
> >
> > This is espacially a bad thing if you have already a lot of
> > configurations (e.g. Referenced Sites, local caches ...)....
>
> IIUC those configurations come from .cfg files found in a folder under
> ./sling?
>
> If yes, you could try moving that folder elsewhere, delete ./sling and
> move it back.
>
> We might also define a second folder for user configurations (and user
> data), outside of the ./sling folder.
>
> -Bertrand
>



-- 
David Riccitelli
-----
Skype: ziodave
Twitter: @ziodave
LinkedIn: http://it.linkedin.com/in/riccitelli
-----
Interact SpA
Via A. Bargoni 78 (scala F)
00153 Roma

T +39 06 58318 301
F +39 06 58318 303

Re: Updating Stanbol Version without deleting /sling folder (was: EntityHub and DBpedia)

Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,

On Wed, Jul 27, 2011 at 9:28 AM, Rupert Westenthaler
<ru...@gmail.com> wrote:
> ...I would be really interested if there are more elegant solutions how
> to update to an newer Stanbol version than replacing the launcher JAR
> and deleting the "/sling" folder.
>
> This is espacially a bad thing if you have already a lot of
> configurations (e.g. Referenced Sites, local caches ...)....

IIUC those configurations come from .cfg files found in a folder under ./sling?

If yes, you could try moving that folder elsewhere, delete ./sling and
move it back.

We might also define a second folder for user configurations (and user
data), outside of the ./sling folder.

-Bertrand