You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Henning Schmiedehausen <he...@schmiedehausen.org> on 2010/05/26 00:00:44 UTC
shindig-social-api depends on shindig-gadget
Hi,
it seems that the only thing that actually depends on this inside the
shindig-social-api jar is the code in the samples/* package. Can we
either make the dependency on shindig-gadgets optional or (better)
move the sample code out? e.g. in a "sample" package?
-h
Re: shindig-social-api depends on shindig-gadget
Posted by Henning Schmiedehausen <he...@schmiedehausen.org>.
Sure.
-h
On Wed, May 26, 2010 at 07:18, Paul Lindner <pl...@linkedin.com> wrote:
> The SampleContainerHandler can definitely move to the java/server module --
> it's now quite easy due to multibindings. Want to submit a patch for that?
>
>
> On Tue, May 25, 2010 at 3:00 PM, Henning Schmiedehausen <
> henning@schmiedehausen.org> wrote:
>
>> Hi,
>>
>> it seems that the only thing that actually depends on this inside the
>> shindig-social-api jar is the code in the samples/* package. Can we
>> either make the dependency on shindig-gadgets optional or (better)
>> move the sample code out? e.g. in a "sample" package?
>>
>> -h
>>
>
Re: shindig-social-api depends on shindig-gadget
Posted by Paul Lindner <pl...@linkedin.com>.
The SampleContainerHandler can definitely move to the java/server module --
it's now quite easy due to multibindings. Want to submit a patch for that?
On Tue, May 25, 2010 at 3:00 PM, Henning Schmiedehausen <
henning@schmiedehausen.org> wrote:
> Hi,
>
> it seems that the only thing that actually depends on this inside the
> shindig-social-api jar is the code in the samples/* package. Can we
> either make the dependency on shindig-gadgets optional or (better)
> move the sample code out? e.g. in a "sample" package?
>
> -h
>