Hi,
So, apparently, people didn't like internal in the groupId so we ended up
with org.hibernate.infra which was one of the groupIds suggested by
Emmanuel.
The Asciidoctor theme is here:
https://github.com/hibernate/hibernate-asciidoctor-theme .
I just pushed the first version to our Nexus so I will start pushing the PR
to all the NoORM projects.
--
Guillaume
On Tue, Feb 7, 2017 at 12:03 PM, Guillaume Smet <guillaume.smet(a)gmail.com>
wrote:
Hi,
On Mon, Feb 6, 2017 at 4:21 PM, Emmanuel Bernard <emmanuel(a)hibernate.org>
wrote:
> On the license, I think ASL 2.0 is the best for such project.
>
As we discussed it in Lisbon, we might "copy" (using Maven) sources from
an internal utility project to the NoORM projects, as we want to avoid
dependency hell with different versions of the utilities. In this case,
they might be included in the source jar. Thus, I think the best is to dual
license everything from the start.
I'll go do that.
> On the group id, am I right that this project is some utilities used by
> us internally? And would not be imported by a user?
>
> If true then I’d avoid common as it feels like something that a user
> would import. internal could work. Some other proposal (to be combined or
> not):
> - utilities
> - infra
> - toolbox
>
OK, if internal works for you, let's settle on it. It's widely used in the
Java world to name internal packages. It makes perfect sense here.
> On the theme, I don't have a definitive opinion but I think like
> Guillaume I’d prefer a lighter customized version of the default Asciidoc
> theme rather than the heavyweight one.
>
OK, let's start with this to unblock the situation with OGM and Search.
ORM can still use part of the theme (the PDF goodies) and keep their CSS if
they prefer. And once they moved to use part of it, we can revisit and
adjust so that everyone is happy. It's not as if the changes were breaking
changes for the users, it won't be an issue to adjust one way or the other.
--
Guillaume