If that's the case we at least need some confidence that java5 will build. This is where we need to get builds.a.o up and running and notifying the dev list when things fail. On Jul 30, 2012 1:06 PM, "Henry Saputra" <henry.sapu...@gmail.com> wrote:
> Hmm I always though we only build Java6 artifacts on purpose and let > consumers of Java5 profile build their own jars > > - Henry > > On Sun, Jul 29, 2012 at 5:43 PM, Ryan Baxter <rbaxte...@apache.org> wrote: > > It also just occurred to me that we should be building Java 5 artifacts > for > > our releases which we have not been doing :( > > > > On Sun, Jul 29, 2012 at 8:42 PM, Ryan Baxter <rbaxte...@gmail.com> > wrote: > > > >> We had a vote about this a year ago [1] and it looks like at least one > >> consumer said they needed Java 5 support. > >> > >> Mike, does Liferay still have the same requirements? > >> > >> > >> On Sat, Jul 28, 2012 at 10:15 PM, Stanton Sievers <ssiev...@apache.org > >wrote: > >> > >>> Is anyone building or using Shindig in a Java 5 environment? I've > tried > >>> building against Java 5 with the "java5" profile and I've hit a half > dozen > >>> compile issues already that have been around for a while. > >>> > >>> Are we planning on supporting Java 5 for 2.5.0? I'd like to get the > >>> consensus on the dev list and then send a vote out to the users lists > if > >>> necessary to get a feel for the desire to have Java 5 support. > >>> > >>> Thanks, > >>> -Stanton > >>> > >> > >> >
