provide module info

as stated in #30 cssfx is not modular.

we should remedy to that by:

• either fixing the automatic module name
• provide real module-info

Also the module name to expose must be defined:

1. cssfx it is the current automatic module name:
   • good for compatibility reasons
   • bad for potential collisions in global namespace
2. org.fxmisc.cssfx
   • avoid collisions by using the current groupId namespace
   • bad because out control, domain is owned by Thomas Mikula
3. fr.brouillard.cssfx
   • avoid collisions by using an owned groupId namespace
   • its a controlled namespace (including for deployment in central)

[FlorianKirmaier]

I don’t think 1 is a good solution. I would either do 3 combined with refactoring the existing classes or 2. Probably 2 because it’s easier and the drawback is relatively small.

[McFoggy]

which probably takes more time because it requires registering the new domain to maven central

No I already own all the rights to fr.brouillard.oss for sonatype/central deployments.

I’ll prepare the move, do a PR and if OK for you & community I will publish later a 11.3 version. I do not want to jump to 12 because I’d like to keep some kind of synch/compatibility with the JVM/javafx version it targets.