Thanks everybody for input.
As @Colin already mentioned I was talking about option 4 of Thomas list. I
have moved gwt-safecss as separate modules into gwt-safehtml. (Need to add
a note at the existing GitHub repo of gwt-safecss that the modules have
moved after the PR is merged). I made a PR:
https://github.com/Vertispan/gwt-safehtml/pull/6. Everybody is welcome to
discuss the PR.
There is one thing that needs to be discussed:
Atm the name of the module is the last part of the groupid. For example
gwt-editor: 'org.gwtproject.editor'. So, we have an easy rule how the
groupid and artifatid is created.
Moving gwt-safecss into gwt-safehtml, we will have the first time two
modules in one repo. Both modules share the same parent Maven module. If
we do nothing, the rule mentioned above will work for gwt-safehtml but not
for gwt-safecss. gwt-safecss has the groupid 'org.gwtproject.safehtml'
cause of the parent pom. I changed that, so that the groupid of gwt-safecss
is 'org.gwtproject.safecss'. But doing this is very unusual for a Maven
multi module project.
Personally I would go with 'org.gwtproject.gwt-safecss' as groupid. It will
make it much easier for gwt users to work with the module.
What do you think?
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit-contributors/fea3fafb-9c7a-4d30-8cc8-aca898cd5c53o%40googlegroups.com.
