[hibernate-dev] [OGM] Package structure in OGM modules

[Gunnar Morling]

2013/7/3 Emmanuel Bernard <emmanuel at hibernate.org>

> I have created https://hibernate.atlassian.net/browse/OGM-292 to capture
> this.
>

Cool, thanks.

As you say, a proper api/spi/impl split is even more important in order to
avoid breaking changes for clients later on.


> On Wed 2013-07-03 14:17, Emmanuel Bernard wrote:
> > It grew with a similar package structure han ORM but that can be
> > revisited. In fact there are many package changes we need to do (api /
> > spi / impl split etc) but these are not important for now.
> >
> > On Wed 2013-07-03 11:34, Gunnar Morling wrote:
> > > Hi,
> > >
> > > I'm wondering about the package structure in the provider-specific OGM
> > > modules (hibernate-ogm-mongodb etc.). Why is it e.g.:
> > >
> > >     org.hibernate.ogm.{datastore|dialect|type|...}.mongodb
> > >
> > > instead of
> > >
> > >     org.hibernate.ogm.mongodb.{datastore|dialect|type|...}
> > >
> > > ?
> > >
> > > Intuitively I'd have expected the latter, as I'd consider the provider
> as
> > > the more global concept and the different sub-structures of a given
> > > provider as a more specific (sub)-concept.
> > >
> > > It surely works both ways, I'm just wondering what the rationale was
> to go
> > > for the current approach.
> > >
> > > Thanks,
> > >
> > > --Gunnar
> > > _______________________________________________
> > > hibernate-dev mailing list
> > > hibernate-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>