Re: [VOTE] Release Apache Shindig version 2.5.0-beta2
I discarded the original staging repo, took in the new fixes, and regenerated beta2. The new staging repo is here: https://repository.apache.org/content/repositories/orgapacheshindig-232/ Also here is the new list of issues fixed in the beta: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+SHINDIG+AND+resolved+%3E%3D+2012-03-26 Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 -Ryan From: daviesd To: , Date: 06/07/2012 03:51 PM Subject:Re: [VOTE] Release Apache Shindig version 2.5.0-beta2 -1 until SHINDIG-1794 is fixed (if deemed necessary for release). doug On 6/6/12 9:39 AM, "Ryan J Baxter" wrote: > Hi All, > > I finished the 2.5.0-beta2 release last night, here is all the info. > > We solved 52 issues: > https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId= > 12321079 > > > Staging repo: > https://repository.apache.org/content/repositories/orgapacheshindig-190/ > > Tag: > http://svn.apache.org/repos/asf/shindig/tags/shindig-project-2.5.0-beta2/ > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > -Ryan
Re: URGENT: Shindig snapshots
Interesting. I didn't know that existed. So what is the shindig activity on builds.apache.org? Dead build process? Just curious, since it seems to be running something. Thanks for talking a look at it. Hopefully there will be a snapshot for me tomorrow. On Jun 12, 2012, at 9:38 PM, "Paul Lindner" wrote: > Hmm, looks like the java.net download of the JVM failed on hudson.inuus.com > (my home server). I'll fix it up.. > > On Tue, Jun 12, 2012 at 6:30 PM, Davies,Douglas wrote: > Paul, can you help out here? > > Thanks, > Doug > > On Jun 12, 2012, at 9:01 PM, "Ryan J Baxter" wrote: > > > Doug, I am not really familiar how this all works. Paul is probably your > > best bet. > > > > -Ryan > > > > > > > > > > From: daviesd > > To: shindig , > > Date: 06/12/2012 10:34 AM > > Subject:Re: Shindig snapshots > > > > > > > > I¹m not familiar with the continuous build, assembly, and snapshot process > > for shindig, but it seems like the assemblies are failing (if this is even > > how the snapshots are created). > > > > https://builds.apache.org/job/Shindig%20Assembly/ > > > > I found a thread from back in May where this was being addressed. > > > > http://shindig-dev.markmail.org/thread/6xhhijzcpyguykl3 > > > > Is there anyone besides Paul who can check on why artifacts have not been > > generated since May 4 (if not I might URGENT him)? Is no one else > > dependant > > on snapshots or are you just pulling trunk and creating your own? We use > > to > > rely on the the daily snapshots but have been on beta1 for quite a while, > > so > > I didn¹t even realize no new artifacts were being generated. > > > > doug > > > > > > On 6/11/12 2:34 PM, "daviesd" wrote: > > > >> I¹m having issues again getting the latest maven artifacts (I¹ve been > > using > >> beta1 for a while now). This is the repository I¹m using (for both beta > > and > >> snapshot) > >> > >> https://repository.apache.org/content/groups/public/org/apache/shindig > >> > >> However the snapshots don¹t seem to have been updated since the > > beginning of > >> May. Am I using the wrong location? > >> > >> Doug > > > > > > > > -- > Paul Lindner -- lind...@inuus.com -- profiles.google.com/pmlindner
Re: URGENT: Shindig snapshots
Paul speaking of Hudson, could you give Stanton and myself karma on those machines so we can help out with these types of problems? I sent an email out a while ago, but I am sure you were buried in work. >Yes, please. > >Username: ssievers > >Thanks, >-Stanton > > > >From: Ryan J Baxter/Westford/IBM@Lotus >To: "Paul Lindner" , >Cc: shindig >Date: 05/01/2012 21:43 >Subject:Committer Access To Jenkins Server > > > >Paul, could you grant me committer access to the ASF Jenkins server [1]? I > >think Stanton also needs access. Any other committers need access? > >Username: rbaxter85 > >[1] http://wiki.apache.org/general/Jenkins?action=show&redirect=Hudson#How_do_I_get_an_account > > >-Ryan -Ryan From: Paul Lindner To: "Davies,Douglas" , Cc: dev@shindig.apache.org Date: 06/12/2012 09:36 PM Subject:Re: URGENT: Shindig snapshots Sent by:pmlind...@gmail.com Hmm, looks like the java.net download of the JVM failed on hudson.inuus.com(my home server). I'll fix it up.. On Tue, Jun 12, 2012 at 6:30 PM, Davies,Douglas wrote: > Paul, can you help out here? > > Thanks, > Doug > > On Jun 12, 2012, at 9:01 PM, "Ryan J Baxter" wrote: > > > Doug, I am not really familiar how this all works. Paul is probably your > > best bet. > > > > -Ryan > > > > > > > > > > From: daviesd > > To: shindig , > > Date: 06/12/2012 10:34 AM > > Subject:Re: Shindig snapshots > > > > > > > > I¹m not familiar with the continuous build, assembly, and snapshot > process > > for shindig, but it seems like the assemblies are failing (if this is > even > > how the snapshots are created). > > > > https://builds.apache.org/job/Shindig%20Assembly/ > > > > I found a thread from back in May where this was being addressed. > > > > http://shindig-dev.markmail.org/thread/6xhhijzcpyguykl3 > > > > Is there anyone besides Paul who can check on why artifacts have not been > > generated since May 4 (if not I might URGENT him)? Is no one else > > dependant > > on snapshots or are you just pulling trunk and creating your own? We use > > to > > rely on the the daily snapshots but have been on beta1 for quite a while, > > so > > I didn¹t even realize no new artifacts were being generated. > > > > doug > > > > > > On 6/11/12 2:34 PM, "daviesd" wrote: > > > >> I¹m having issues again getting the latest maven artifacts (I¹ve been > > using > >> beta1 for a while now). This is the repository I¹m using (for both beta > > and > >> snapshot) > >> > >> https://repository.apache.org/content/groups/public/org/apache/shindig > >> > >> However the snapshots don¹t seem to have been updated since the > > beginning of > >> May. Am I using the wrong location? > >> > >> Doug > > > > > -- Paul Lindner -- lind...@inuus.com -- profiles.google.com/pmlindner
Re: URGENT: Shindig snapshots
Hmm, looks like the java.net download of the JVM failed on hudson.inuus.com(my home server). I'll fix it up.. On Tue, Jun 12, 2012 at 6:30 PM, Davies,Douglas wrote: > Paul, can you help out here? > > Thanks, > Doug > > On Jun 12, 2012, at 9:01 PM, "Ryan J Baxter" wrote: > > > Doug, I am not really familiar how this all works. Paul is probably your > > best bet. > > > > -Ryan > > > > > > > > > > From: daviesd > > To: shindig , > > Date: 06/12/2012 10:34 AM > > Subject:Re: Shindig snapshots > > > > > > > > I¹m not familiar with the continuous build, assembly, and snapshot > process > > for shindig, but it seems like the assemblies are failing (if this is > even > > how the snapshots are created). > > > > https://builds.apache.org/job/Shindig%20Assembly/ > > > > I found a thread from back in May where this was being addressed. > > > > http://shindig-dev.markmail.org/thread/6xhhijzcpyguykl3 > > > > Is there anyone besides Paul who can check on why artifacts have not been > > generated since May 4 (if not I might URGENT him)? Is no one else > > dependant > > on snapshots or are you just pulling trunk and creating your own? We use > > to > > rely on the the daily snapshots but have been on beta1 for quite a while, > > so > > I didn¹t even realize no new artifacts were being generated. > > > > doug > > > > > > On 6/11/12 2:34 PM, "daviesd" wrote: > > > >> I¹m having issues again getting the latest maven artifacts (I¹ve been > > using > >> beta1 for a while now). This is the repository I¹m using (for both beta > > and > >> snapshot) > >> > >> https://repository.apache.org/content/groups/public/org/apache/shindig > >> > >> However the snapshots don¹t seem to have been updated since the > > beginning of > >> May. Am I using the wrong location? > >> > >> Doug > > > > > -- Paul Lindner -- lind...@inuus.com -- profiles.google.com/pmlindner
URGENT: Shindig snapshots
Paul, can you help out here? Thanks, Doug On Jun 12, 2012, at 9:01 PM, "Ryan J Baxter" wrote: > Doug, I am not really familiar how this all works. Paul is probably your > best bet. > > -Ryan > > > > > From: daviesd > To: shindig , > Date: 06/12/2012 10:34 AM > Subject:Re: Shindig snapshots > > > > I¹m not familiar with the continuous build, assembly, and snapshot process > for shindig, but it seems like the assemblies are failing (if this is even > how the snapshots are created). > > https://builds.apache.org/job/Shindig%20Assembly/ > > I found a thread from back in May where this was being addressed. > > http://shindig-dev.markmail.org/thread/6xhhijzcpyguykl3 > > Is there anyone besides Paul who can check on why artifacts have not been > generated since May 4 (if not I might URGENT him)? Is no one else > dependant > on snapshots or are you just pulling trunk and creating your own? We use > to > rely on the the daily snapshots but have been on beta1 for quite a while, > so > I didn¹t even realize no new artifacts were being generated. > > doug > > > On 6/11/12 2:34 PM, "daviesd" wrote: > >> I¹m having issues again getting the latest maven artifacts (I¹ve been > using >> beta1 for a while now). This is the repository I¹m using (for both beta > and >> snapshot) >> >> https://repository.apache.org/content/groups/public/org/apache/shindig >> >> However the snapshots don¹t seem to have been updated since the > beginning of >> May. Am I using the wrong location? >> >> Doug > >
Re: Shindig snapshots
Doug, I am not really familiar how this all works. Paul is probably your best bet. -Ryan From: daviesd To: shindig , Date: 06/12/2012 10:34 AM Subject:Re: Shindig snapshots I¹m not familiar with the continuous build, assembly, and snapshot process for shindig, but it seems like the assemblies are failing (if this is even how the snapshots are created). https://builds.apache.org/job/Shindig%20Assembly/ I found a thread from back in May where this was being addressed. http://shindig-dev.markmail.org/thread/6xhhijzcpyguykl3 Is there anyone besides Paul who can check on why artifacts have not been generated since May 4 (if not I might URGENT him)? Is no one else dependant on snapshots or are you just pulling trunk and creating your own? We use to rely on the the daily snapshots but have been on beta1 for quite a while, so I didn¹t even realize no new artifacts were being generated. doug On 6/11/12 2:34 PM, "daviesd" wrote: > I¹m having issues again getting the latest maven artifacts (I¹ve been using > beta1 for a while now). This is the repository I¹m using (for both beta and > snapshot) > > https://repository.apache.org/content/groups/public/org/apache/shindig > > However the snapshots don¹t seem to have been updated since the beginning of > May. Am I using the wrong location? > > Doug
Re: OAuth2 token expiration and issue times broken
OK I checked in the changes to the javadoc. -Ryan From: A Clarke To: dev@shindig.apache.org, Date: 06/12/2012 11:28 AM Subject:Re: OAuth2 token expiration and issue times broken Yes. On Tue, Jun 12, 2012 at 9:36 AM, Ryan J Baxter wrote: > Adam is it just the javadoc for OAuth2Token.getIssueAt and > OAuth2Token.getExpiresAt that needs to be updated? > > -Ryan > > > > > From: A Clarke > To: dev@shindig.apache.org, > Date: 06/12/2012 09:04 AM > Subject:Re: OAuth2 token expiration and issue times broken > > > > Looks like I forgot to update the interface javadoc. > > The intention is to use milliseconds now, this made it easier for other > teams to persist and compare values as timestamps. > > > > On Tue, Jun 12, 2012 at 8:23 AM, Ryan J Baxter > wrote: > > > Doug, this was intentional I believe, although I can't remember the > reason > > exactly. Adam and Brian, can explain the logic behind this decision. > > > > > > > > -Ryan > > > > > > > > > > From: daviesd > > To: shindig , > > Date: 06/11/2012 04:15 PM > > Subject:OAuth2 token expiration and issue times broken > > > > > > > > The fix for SHINDIG-1732 introduces a bug with the oauth2 token expires > > and > > issue times (or at least a documentation change). The time stored in > > OAuth2Token use to be in seconds (and is documented that way). Now it¹s > > storing them in milliseconds in TokenAuthorizationResponseHandler. This > > causes me to blow up later when I persist them, since I was multiplying > by > > 1000 and the converting it to a Date. What is the correct behavior > here? > > > > doug > > > > > >
Re: OAuth2 token expiration and issue times broken
Yes. On Tue, Jun 12, 2012 at 9:36 AM, Ryan J Baxter wrote: > Adam is it just the javadoc for OAuth2Token.getIssueAt and > OAuth2Token.getExpiresAt that needs to be updated? > > -Ryan > > > > > From: A Clarke > To: dev@shindig.apache.org, > Date: 06/12/2012 09:04 AM > Subject:Re: OAuth2 token expiration and issue times broken > > > > Looks like I forgot to update the interface javadoc. > > The intention is to use milliseconds now, this made it easier for other > teams to persist and compare values as timestamps. > > > > On Tue, Jun 12, 2012 at 8:23 AM, Ryan J Baxter > wrote: > > > Doug, this was intentional I believe, although I can't remember the > reason > > exactly. Adam and Brian, can explain the logic behind this decision. > > > > > > > > -Ryan > > > > > > > > > > From: daviesd > > To: shindig , > > Date: 06/11/2012 04:15 PM > > Subject:OAuth2 token expiration and issue times broken > > > > > > > > The fix for SHINDIG-1732 introduces a bug with the oauth2 token expires > > and > > issue times (or at least a documentation change). The time stored in > > OAuth2Token use to be in seconds (and is documented that way). Now it¹s > > storing them in milliseconds in TokenAuthorizationResponseHandler. This > > causes me to blow up later when I persist them, since I was multiplying > by > > 1000 and the converting it to a Date. What is the correct behavior > here? > > > > doug > > > > > >
Re: Using custom @ ids GroupIds throws IllegalArgumentException (issue 6305079)
http://codereview.appspot.com/6305079/diff/6001/java/social-api/src/test/java/org/apache/shindig/social/opensocial/spi/GroupIdTest.java
File
java/social-api/src/test/java/org/apache/shindig/social/opensocial/spi/GroupIdTest.java
(right):
http://codereview.appspot.com/6305079/diff/6001/java/social-api/src/test/java/org/apache/shindig/social/opensocial/spi/GroupIdTest.java#newcode43
java/social-api/src/test/java/org/apache/shindig/social/opensocial/spi/GroupIdTest.java:43:
GroupId unknown = GroupId.fromJson("@foo");
Ahhh! I'd be fine with that.
+1
On 2012/06/12 02:37:55, DouglasLDavies wrote:
http://codereview.appspot.com/6305079/
Re: Shindig snapshots
I¹m not familiar with the continuous build, assembly, and snapshot process for shindig, but it seems like the assemblies are failing (if this is even how the snapshots are created). https://builds.apache.org/job/Shindig%20Assembly/ I found a thread from back in May where this was being addressed. http://shindig-dev.markmail.org/thread/6xhhijzcpyguykl3 Is there anyone besides Paul who can check on why artifacts have not been generated since May 4 (if not I might URGENT him)? Is no one else dependant on snapshots or are you just pulling trunk and creating your own? We use to rely on the the daily snapshots but have been on beta1 for quite a while, so I didn¹t even realize no new artifacts were being generated. doug On 6/11/12 2:34 PM, "daviesd" wrote: > I¹m having issues again getting the latest maven artifacts (I¹ve been using > beta1 for a while now). This is the repository I¹m using (for both beta and > snapshot) > > https://repository.apache.org/content/groups/public/org/apache/shindig > > However the snapshots don¹t seem to have been updated since the beginning of > May. Am I using the wrong location? > > Doug
Re: OAuth2 token expiration and issue times broken
Adam is it just the javadoc for OAuth2Token.getIssueAt and OAuth2Token.getExpiresAt that needs to be updated? -Ryan From: A Clarke To: dev@shindig.apache.org, Date: 06/12/2012 09:04 AM Subject:Re: OAuth2 token expiration and issue times broken Looks like I forgot to update the interface javadoc. The intention is to use milliseconds now, this made it easier for other teams to persist and compare values as timestamps. On Tue, Jun 12, 2012 at 8:23 AM, Ryan J Baxter wrote: > Doug, this was intentional I believe, although I can't remember the reason > exactly. Adam and Brian, can explain the logic behind this decision. > > > > -Ryan > > > > > From: daviesd > To: shindig , > Date: 06/11/2012 04:15 PM > Subject:OAuth2 token expiration and issue times broken > > > > The fix for SHINDIG-1732 introduces a bug with the oauth2 token expires > and > issue times (or at least a documentation change). The time stored in > OAuth2Token use to be in seconds (and is documented that way). Now it¹s > storing them in milliseconds in TokenAuthorizationResponseHandler. This > causes me to blow up later when I persist them, since I was multiplying by > 1000 and the converting it to a Date. What is the correct behavior here? > > doug > >
Re: OAuth2 token expiration and issue times broken
Looks like I forgot to update the interface javadoc. The intention is to use milliseconds now, this made it easier for other teams to persist and compare values as timestamps. On Tue, Jun 12, 2012 at 8:23 AM, Ryan J Baxter wrote: > Doug, this was intentional I believe, although I can't remember the reason > exactly. Adam and Brian, can explain the logic behind this decision. > > > > -Ryan > > > > > From: daviesd > To: shindig , > Date: 06/11/2012 04:15 PM > Subject:OAuth2 token expiration and issue times broken > > > > The fix for SHINDIG-1732 introduces a bug with the oauth2 token expires > and > issue times (or at least a documentation change). The time stored in > OAuth2Token use to be in seconds (and is documented that way). Now it¹s > storing them in milliseconds in TokenAuthorizationResponseHandler. This > causes me to blow up later when I persist them, since I was multiplying by > 1000 and the converting it to a Date. What is the correct behavior here? > > doug > >
Re: OAuth2 token expiration and issue times broken
Doug, this was intentional I believe, although I can't remember the reason exactly. Adam and Brian, can explain the logic behind this decision. -Ryan From: daviesd To: shindig , Date: 06/11/2012 04:15 PM Subject:OAuth2 token expiration and issue times broken The fix for SHINDIG-1732 introduces a bug with the oauth2 token expires and issue times (or at least a documentation change). The time stored in OAuth2Token use to be in seconds (and is documented that way). Now it¹s storing them in milliseconds in TokenAuthorizationResponseHandler. This causes me to blow up later when I persist them, since I was multiplying by 1000 and the converting it to a Date. What is the correct behavior here? doug
