[hibernate-dev] Hibernate Shards 3.0.0.Beta2 released

[Max Ross]

Hibernate Shards 3.0.0.Beta2 released

The Hibernate Shards team is pleased to announce the availability of
Hibernate Shards 3.0.0.Beta2. The most significant improvements in
this release are:
* Support for Hibernate Annotations
* Fewer gaps in the sharded implementations of Session and Criteria
(Session is almost completely supported in fact)
* More flexible configuration (no longer necessary to construct a
prototype Configuration object)

Please visit http://shards.hibernate.org for more information.

Max (on behalf of the Hibernate Shards team)
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Migration to Hibernate Core 3.3

[Max Ross]

I forgive you.

On Thu, May 1, 2008 at 4:38 PM, Emmanuel Bernard <[EMAIL PROTECTED]>
wrote:

> I have been working in the past two days to make the build system, and the
> projects compatible with the migration to Core 3.3:
>  - Hibernate Commons Annotations
>  - Hibernate Annotations
>  - Hibernate Validator
>  - Hibernate Search
>  - Hibernate EntityManager
>
> Sorry I forgot Hibernate Shards, but I will look at it after JavaOne
>
> I did:
>  - remove the dependency to the hibernate core build structure (both the
> documentation and the build system)
>  - moved almost all dependencies to ivy
>  - added a pom for each project
>  - added a 'ant deploy' task that deploys artifacts to a local maven repo
>
> Still on the todo list before a release:
>  - migrate to slf4j instead of commons-logging for all projects
>  - make use of the new enhanced id generators if it makes sense
>
> It means the developments of trunk are all based on Core 3.3 (trunk)
>
> I would appreciate feedback on the build, the POMs and the rest. Let me
> know if there are any issues.
> ___
> 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

Re: [hibernate-dev] CGLIB

[Max Ross]

jarjar  can be a good option when you're
looking to avoid version conflicts.  Guice uses this to depend on a specific
version of cglib.

On Mon, May 19, 2008 at 1:29 PM, Steve Ebersole <[EMAIL PROTECTED]> wrote:

> Our (default) dependency on CGLIB is starting to cause problems due to
> other libraries using newer versions of ASM (3.x) then the released versions
> of CGLIB use (2.x).  We have now been waiting about a year for a new CGLIB
> release to use these newer ASM APIs.  With 3.3 being eminent, we need to
> rectify this situation.
>
> First, I am going to make javassist the default bytecode provider starting
> with Hibernate 3.3 (
> http://opensource.atlassian.com/projects/hibernate/browse/HHH-2506).
>
> Next, we need to decide what to do with CGLIB moving forward.  This seems
> to be a dead project at this point.  From my recollection, the source
> control for CGLIB does in fact have support for ASM 3.x; so one option would
> be to do a build of it from HEAD.  However, none of us are really bytecode
> gurus, so thats probably not the best option.  The only other option I see
> is to simply deprecate the integration for CGLIB and recommend against its
> use.  Any other options we should explore here?
>
> -
> Steve Ebersole
>
> Project Lead
> http://hibernate.org
> [EMAIL PROTECTED]
>
>
>
>
> ___
> 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