I set it to 1.1.0, but go for 1.1.1-SNAPSHOT if you want. -David
On Mar 30, 2011, at 8:23 PM, Ivan wrote: > If no objection, I will upgrade the OWB to 1.1.1-SNAPSHOT, as I knew there > are still some TCK failures > > 2011/3/30 Shawn Jiang <[email protected]> > >> OWB 1.1.0 vote passed. But I still see OWB 1.1.0-SNAPSHOT in openejb >> trunk >> pom. Could anyone either upgrade it to 1.1.1-SNAPSHOT or use the released >> owb 1.1.0 ? >> >> On Tue, Mar 29, 2011 at 2:55 AM, Jonathan Gallimore < >> [email protected]> wrote: >> >>> I tend to fix any OpenEJB compile errors I get, and commit them. I'm not >>> aware of any issues currently in OpenEJB trunk, but let me know if there >>> are >>> and I'll try and help fix them. I haven't pushed new OpenEJB snapshots, >> but >>> am happy to do that if that's any help. >>> >>> Personally I'd be favour of going with the OWB 1.1.0 release if we can, >> as >>> it can be a bit problematic when new snapshots are published which have >> API >>> changes which break our build. Obviously there may be other reasons to >>> upgrade to the new snapshots - new features, TCK compliance etc, so I >> guess >>> that might influence the decision. >>> >>> Jon >>> >>> On Mon, Mar 28, 2011 at 8:48 AM, Jean-Louis MONTEIRO <[email protected] >>>> wrote: >>> >>>> As far as I know Jon is already working on fixing OWB integration. >>>> Don't know the status nor how different 1.1.0 and 1.1.1 will be. But I >>>> guess >>>> there will be no API changes(i guess no changes because it's only a >> patch >>>> version). >>>> >>>> Jean-Louis >>>> >>>> >>>> 2011/3/28 Shawn Jiang <[email protected]> >>>> >>>>> OWB 1.1.0 is under vote. We need to decide to use the released >> 1.1.0 >>>> or >>>>> coming 1.1.1-SNAPSHOT in openejb and geronimo. >>>>> >>>>> I prefer to keep the OWB to 1.1.0 for a stable TCK env until we have >> to >>>>> change OWB code to fix something. Thoughts ? >>>>> >>>>> -- >>>>> Shawn >>>>> >>>> >>> >> >> >> >> -- >> Shawn >> > > > > -- > Ivan
