[hibernate-dev] New parser bugs reported: HQLPARSER vs HHH ?

[Steve Ebersole]

I think duplication is better too, since at the moment these jira 
projects cover completely separate code bases.

On 01/22/2014 02:32 AM, Sanne Grinovero wrote:
> A forum user had some trouble with the current HQL parser:
>
>   https://forum.hibernate.org/viewtopic.php?f=1&t=1030515
>
> And since I've been slow to react, he went ahead and created a JIRA; I
> think he's right about this, still then - as you can see from his
> latest post - he felt unsure on where to open it, and it became
> HQLPARSER-35.
>
> Since this is about the current parser, he's probably in the wrong
> place, and there is a risk that the ORM team won't notice timely? but
> I don't think I can blame him as it's probably confusing.
>
> My first impulse was to jump on JIRA and see if I could enable some
> big fat warning on HQLPARSER to explain the difference, but actually
> maybe it's better if the ORM team could start looking at new issues in
> there as _actual_ issues?
>
> I'm thinking that while HQLPARSER matures, it should also incorporate
> fixes/tests happening on the mainline parser: if there was a single
> place to track defects of both I could "catch up" on ORM improvements
> when working on it.
>
> So... should I move HQLPARSER-35 to HHH, or shall we leave it there ?
> Maybe better to duplicate the issues?
>
> I'm voting for duplication, as they require either a fix or at least a
> test applied to both projects, and we probably want to keep lifecycle
> independent for a while longer.
>
> Sanne
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev