I finally also succeeded pushing a set of binaries on Nexus. Closed my repo
and I will delete it as yours are up and ready.
Anyway, if the baby still does not want to join us, I'll try to work on the
And also run rat and all that stuff to prepare the final release, let's say
within the next week or two week.
For whatever it's worth, my application works fine with the
"staging-108" version. I am using Eclipselink so I wouldn't
notice any OpenJPA build issues. Been running 1.5.2-plus for
the past seven months and redeployed in 1.6.0-jaxrs without
any issues since 5 days now.
> For whatever it's worth, my application works fine with the
> "staging-108" version. I am using Eclipselink so I wouldn't
> notice any OpenJPA build issues. Been running 1.5.2-plus for
> the past seven months and redeployed in 1.6.0-jaxrs without
> any issues since 5 days now.
> Bjorn Danielsson
> Cuspy Code AB
> David Blevins <[hidden email]> wrote:
> > Had 12 TCK failures in this build I think due to my OpenJPA build. Mark
> is now publishing OpenJPA 2.3.0 binaries to Nexus for an vote. I'll try
> rerolling with that version.
> > If that works and TCK is clear, I'll put the vote.
> > -David
> > On Nov 9, 2013, at 6:38 AM, David Blevins <[hidden email]>
> >> The release tools need work, but this build is good and running the TCK
> >> Maven Repository:
> >> -
> https://repository.apache.org/content/repositories/orgapachetomee-108/ > >>
> >> Staged Binaries:
> >> - https://dist.apache.org/repos/dist/dev/tomee/staging-108/tomee-1.6.0/ > >>
> >> Source Branch:
> >> - https://svn.apache.org/repos/asf/tomee/tomee/branches/tomee-1.6.0/ > >>
> >> The Legal tool I wrote appears to not be working, so we'll have to do
> this on manually on that. I did check and there appeared to be no
> significant binary changes between 1.5.2 and 1.6.0.
> >> Give these binaries a swift kicking, so when we vote we know things are
> good. The goal is to close the vote on the 72 hours mark once it starts.
> That will hopefully be very soon.
> >> -David