Re: getModuleId

2012-01-26 Thread Henry Saputra
Dan, In the Shindig code, who is responsible to set "osapi.container.RenderParam.MODULE_ID" in the render params for services's getGadgetMetadata() function? - Henry On Mon, Jan 23, 2012 at 10:44 AM, Dan Dumont wrote: > Not a problem. > > mid is for the moduleId.  (maybe it wasn't always so...

Re: Aligning the next Shindig release number with OpenSocial spec version to use 2.5.0 instead of 3.0.0

2012-01-26 Thread Henry Saputra
Hi Paul, Will this change impact released 3.0.0 snapshot artifacts in the maven repo https://repository.apache.org/content/repositories/snapshots/org/apache/shindig? - Henry On Thu, Jan 26, 2012 at 6:36 PM, Paul Lindner wrote: > okay, I'll submit a change to 2.5.0-SNAPSHOT and change the Jira

Re: Aligning the next Shindig release number with OpenSocial spec version to use 2.5.0 instead of 3.0.0

2012-01-26 Thread Paul Lindner
okay, I'll submit a change to 2.5.0-SNAPSHOT and change the Jira issues to reflect the new numbering. Rave folks you'll want to update your deps... On Thu, Jan 26, 2012 at 1:23 PM, Ryan J Baxter wrote: > +1 > > > Regards, > > *RYAN J. BAXTER* > Software Engineer - OpenSocial > IBM Collaboratio

Re: NOTICE and LICENSE files

2012-01-26 Thread Ryan J Baxter
Ate, these seem like valid concerns, but I am not a lawyer so not sure I understand all the implications :) What does the rest of the community think? What is the best way to address these? I assume we want to start by creating JIRAs -Ryan From: Ate Douma To: dev@shindig.apach

Re: Aligning the next Shindig release number with OpenSocial spec version to use 2.5.0 instead of 3.0.0

2012-01-26 Thread Ryan J Baxter
+1 Regards, RYAN J. BAXTER Software Engineer - OpenSocial IBM Collaboration Solutions Phone: 1-978-899-3041 E-mail: rjbax...@us.ibm.com Blog: ryanjbaxter.com Chat: rbaxter85 ryanjasonbaxter Find me on: and within IBM on: 550 King St Littleton, MA 01460-1250 United States From:

Re: Aligning the next Shindig release number with OpenSocial spec version to use 2.5.0 instead of 3.0.0

2012-01-26 Thread Ate Douma
+1 On 01/26/2012 08:42 PM, Henry Saputra wrote: Dear Apache Shindig community, As Apache Shindig is reference implementation for the OpenSocial specs, it would be better if the release version is aligned with the OS spec number to make it easier to find out what is the implemented spec version.

RE: Aligning the next Shindig release number with OpenSocial spec version to use 2.5.0 instead of 3.0.0

2012-01-26 Thread Franklin, Matthew B.
+1 >-Original Message- >From: Dan Dumont [mailto:ddum...@us.ibm.com] >Sent: Thursday, January 26, 2012 2:51 PM >To: dev@shindig.apache.org >Subject: Re: Aligning the next Shindig release number with OpenSocial spec >version to use 2.5.0 instead of 3.0.0 > >+1 > >Or the other way around.

Re: Aligning the next Shindig release number with OpenSocial spec version to use 2.5.0 instead of 3.0.0

2012-01-26 Thread Dan Dumont
+1 Or the other way around. Move the spec to 3.0 :) From: Evgeny Bogdanov To: dev@shindig.apache.org, Date: 01/26/2012 02:49 PM Subject:Re: Aligning the next Shindig release number with OpenSocial spec version to use 2.5.0 instead of 3.0.0 +1, it'd be easier On 26/1/

Re: Aligning the next Shindig release number with OpenSocial spec version to use 2.5.0 instead of 3.0.0

2012-01-26 Thread Evgeny Bogdanov
+1, it'd be easier On 26/1/12 20:42, Henry Saputra wrote: Dear Apache Shindig community, As Apache Shindig is reference implementation for the OpenSocial specs, it would be better if the release version is aligned with the OS spec number to make it easier to find out what is the implemented sp

Aligning the next Shindig release number with OpenSocial spec version to use 2.5.0 instead of 3.0.0

2012-01-26 Thread Henry Saputra
Dear Apache Shindig community, As Apache Shindig is reference implementation for the OpenSocial specs, it would be better if the release version is aligned with the OS spec number to make it easier to find out what is the implemented spec version. One proposal is to change the current Shindig rel

Re: Bad deploy of 3.0 snapshots

2012-01-26 Thread Michael Matthews
Disregard. Since I sent this, the 1/26 snapshots became available and everything is working fine. Thanks Mike On 1/26/12 11:21 AM, "Michael Matthews" wrote: > Hello all. > > It appears there was a problem with the latest deploy of the 3.0.0 snapshot > artifacts to the maven repo > https://re

Bad deploy of 3.0 snapshots

2012-01-26 Thread Michael Matthews
Hello all. It appears there was a problem with the latest deploy of the 3.0.0 snapshot artifacts to the maven repo https://repository.apache.org/content/repositories/snapshots/org/apache/shin dig. Some of the artifacts (shindig-common) have an artifact for 1/25 and others do not (latest shindig-g