As a follow-up to this, we need to discuss how to handle "deprecation"
of now completely unsupported methods.
Lets take org.hibernate.Hibernate#entity as an example. Given that
these types are now explicitly scoped to a SessionFactory and that the
exposed org.hibernate.Hibernate Type methods do not accept a
SessionFactory we need to decide what to do here. We completely cannot
support these methods. So we must decide between:
1) removal
2) deprecation
If we were to opt for deprecation, the method would end up looking
something like:
/**
* DO NOT USE!
* @deprecated Types are now scoped, use {...@link xyz} instead.
*/
public static Type entity(String name) {
throw new HibernateException( "Not supported" );
}
Which I wonder might be worse than removing the method altogether.
On Mon, 2010-05-03 at 13:00 -0500, Steve Ebersole wrote:
> Attached are the notes from today's meeting.
>
> In summary:
> 1) Strong is almost done setting up the new Hudson jobs for Core.
> Yaay!
> 2) Rather than email notifications we will utilize Hudson's RSS
> features.
> 3) We will be switching from HSQLDB to H2 for default testing.
> 4) We agreed to try 4 weeks as the timebox for 3.5 for the time being.
> That puts 3.5.2 on May 12th.
> 5) For the time being bug fixes need to be applied to both trunk and the
> 3.5 branch. Also discussed general backporting guidelines.
> 6) Discussed changes in 3.6 pertaining to Type, TypeFactory, etc. Will
> get http://community.jboss.org/wiki/DesignTypescoping updated and we can
> discuss any concern next week.
> 7) Merging annotation documentation into core is in progress.
> 8) Discussed JIRA issue
> http://opensource.atlassian.com/projects/hibernate/browse/HHH-4135 which
> lead to
> http://opensource.atlassian.com/projects/hibernate/browse/HHH-5187
>
>
--
Steve Ebersole <st...@hibernate.org>
http://hibernate.org
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
