[hibernate-dev] MongoDB work in progress branch
Hi all, you can now find the "mongodb" branch in the reference repository ( git://github.com/hibernate/hibernate-ogm.git ) This is now: - rebased on latest master - includes Guillaume Scheibel's initial pull - includes Oliver Carr's patch for Calendar I'll be off for afternoon, back to help in the evening and tomorrow. Cheers, Sanne ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Hibernate Search 4.1.0.Final - conditional indexing and more
The Hibernate Search team is really proud to announce version 4.1. What's in there? - conditional indexing - faster, lighter, more targeted indexing - better JGroups-based clustering - support for Hibernate ORM 4.1 and JBoss AS 7.1 - and more things than you imagine More info at http://goo.gl/qVjvu ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Hibernate Search 4.1.0.Final - conditional indexing and more
Great ! Gratz ! Nicolas 2012/4/4 Emmanuel Bernard > The Hibernate Search team is really proud to announce version 4.1. What's > in there? > > - conditional indexing > - faster, lighter, more targeted indexing > - better JGroups-based clustering > - support for Hibernate ORM 4.1 and JBoss AS 7.1 > - and more things than you imagine > > More info at http://goo.gl/qVjvu > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] starting release
I am starting the release process for ORM 4.1.2. Please do not push changes to master for the time being. Thanks. -- st...@hibernate.org http://hibernate.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] starting release
Done. You can push again. Thanks On Wed 04 Apr 2012 11:17:57 AM CDT, Steve Ebersole wrote: > I am starting the release process for ORM 4.1.2. Please do not push > changes to master for the time being. Thanks. > -- st...@hibernate.org http://hibernate.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Hibernate ORM 4.1.2 Release
http://in.relation.to/Bloggers/HibernateORM412Release -- st...@hibernate.org http://hibernate.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] starting release
Just wondering - did you consider tagging and then using a specific commit id for the release ? So you wouldn't need to worry about this, you personally pick the commit and don't care for subsequent commits. Cheers, Sanne On 4 April 2012 18:13, Steve Ebersole wrote: > Done. You can push again. Thanks > > On Wed 04 Apr 2012 11:17:57 AM CDT, Steve Ebersole wrote: >> I am starting the release process for ORM 4.1.2. Please do not push >> changes to master for the time being. Thanks. >> > > -- > st...@hibernate.org > http://hibernate.org > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Hibernate Validator 4.3.0.Beta1
Hi, following in the wake of ORM and Search and completing todays release hat-trick, here comes Hibernate Validator 4.3.0.Beta1 - http://in.relation.to/23077.lace Enjoy, Hardy ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] starting release
I have discussed this a few times now with individual folks. Can't remember if we ever discussed it or not. I should add this to the "releasing" wiki page... Sure I have thought about it. In fact this is how I used to do releases. It comes down to the fact that things often go wrong during the actual releasing (Nexus validations fail, Nexus becomes unavailable, etc). My approach is really about dealing with these possibilities. To be honest, most of those problems have gone away now that I use Gradle. Using the "old approach", in those cases one has to make the appropriate changes, commit and retag. But you are in a bad position there is someone has pushed since your original tag. Actually this is what I used to use that stable branch for. Basically I would release and tag from stable and commit/push any changes needed to "fix the release" only to stable initially; that essentially was the isolation. But its a complex and largely unnecessary step I decided considering in the 10 or so releases I did using that approach not once ever did someone push changes after I had started a release. Far easier IMO to just announce that you are starting a release and ask for folks to hold off pushing. Essentially your approach does the tag first, making an assumption that releasing from that tag will work. You run into probems if the release process breaks down in anyway that requires commitable changes. On the otherhand, I tag from a commit I *know* will work. On Wed 04 Apr 2012 02:21:40 PM CDT, Sanne Grinovero wrote: > Just wondering - did you consider tagging and then using a specific > commit id for the release ? > > So you wouldn't need to worry about this, you personally pick the > commit and don't care for subsequent commits. > > Cheers, > Sanne > > On 4 April 2012 18:13, Steve Ebersole wrote: >> Done. You can push again. Thanks >> >> On Wed 04 Apr 2012 11:17:57 AM CDT, Steve Ebersole wrote: >>> I am starting the release process for ORM 4.1.2. Please do not push >>> changes to master for the time being. Thanks. >>> >> >> -- >> st...@hibernate.org >> http://hibernate.org >> ___ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev -- st...@hibernate.org http://hibernate.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] multi-tenancy in Hibernate and JPA 2.1
> I am not sure how the PaaS multi-tenant config will look like exactly but if > we can > automatically prefix the 2LC regions without adding an explicit mandatory > property > that would be nice. Sure. The problem is that in the JPA-supported PaaS model, there is only really a need to know the tenant identifier when using SHARED_TABLE approach. There is a part of the proposal about making the tenant identifier available via ENC/JNDI. However, given that only the SHARED_TABLE approach (what we call DISCRIMINATED btw) in JPA needs access to it, I was not clear if that would be available to all approaches. But even there, I am not sure the ENC entry would be available when the EMF is getting built. This ties into THE critical difference between the multi-tenancy support I did already and what JPA is proposing: namely, Hibernate multi-tenancy supports a single SF/EMF instance serving multiple tenants, whereas the JPA model would constrain one EMF to serve a single tenant. So short answer.. I don't know either. But if it the tenant identifier is know when building EMF/SF, then yes, the plan was to use region prefixes. > There is also a case to be made to not allow different tenants to see each > other data. Obviously ;) > so unless we can catch all malicious SQL queries, it's better disabled by > default. > though I could see an app developer knowing his environment and enabling the > option if needed. I guess the question is more about whether people had ideas for "catch(ing) [and properly morphing] all malicious SQL queries". In my opinion, thats a pretty tall task. Essentially we would need database-specific SQL parsers -- st...@hibernate.org http://hibernate.org ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
