Re: [Exist-open] External extensions repository?

[James F. <jam...@gm...>]

On Tue, Mar 16, 2010 at 6:11 PM, Wolfgang Meier <wol...@ex...> wrote:
>> I) create a new optional directory somewhere in source control ...
>> which may require a little tooling to split off build, config to
>> separate required and optional extensions
>
> I agree.
>
>> II) integrate FlorentG expath installer thingy he has already built in
>> java as an extension (I would make it required)
>>
>> III) then we can create a small web app under admin area to handle
>> uploading a jar and deploying said app via expath packaging
>
> I had similar plans. We actually had quite a few discussions about
> packaging and auto-deployment in Prague. Florent's specification would
> be the first step, though we will need a few extensions on top of it
> to handle more complex scenarios. For those, Thomas' EXE framework
> will be another reference.
>
> Well, it might indeed be best if we proceed with your steps II and
> III, and then extend them as required (ideally while remaining
> compatible with the expath packaging).

I think this is a pragmatic approach ... we can influence the expath
packaging spec now as its young ... also its improbable that we will
get this right the first time around but the first step is always the
hardest.

I am in contact with FlorentG re if he intends to open source what he
has done with respect to the eXist implementation of his expath
packager ... will report back.

J