"gwt.org" is not available - it refers to a hiking trail. My suggestion is org.gwtproject.$module:gwt-$module.
Cons: - Redundant appearance of $module, and of "gwt" Pros: - Multi-module maven projects all have the same groupid, instead of requiring that the gwt-event project all be under org.gwtproject, or inconsistently using org.gwtproject.$module for multi-module projects or org.gwtproject for single-module projects. Very reasonably we might have projects switch between these states (adding examples, etc), so we should be consistent between types of projects - The "gwt-" prefix makes it clear by looking at just the jar's name (in your IDE's maven dependency jar list, etc) where an artifact comes from - Room is left at the top for more modules, without assuming that all org.gwtproject:* modules are for the client (org.gwtproject.tools, etc) While that's my preferred option, my only strong opinion here is that we plan for future maintainability - the need to change structure and add additional modules to any one project (ideally maintaining coordinates of a dependency that is in use), and consistency across modules. On Saturday, March 24, 2018 at 3:27:01 PM UTC-5, Ahmad Bawaneh wrote: > > OK then, this means that gwt-timer should use *org.gtwproject* as group > id and *gwt-timer* as artifact id. > > On Saturday, March 24, 2018 at 11:30:10 AM UTC+2, Mincong Huang wrote: >> >> Hi, >> >> I'd like to have a clarification about the naming convention for ported >> GWT modules. Because I'm porting the module `gwt-safecss` and >> `gwt-animation`. When I go to Vertispan repository [1], the available >> modules do not use the same rule for the group ID and artifact ID. This is >> a pain when you reference them as dependencies. Here're 5 rules that I >> found. >> >> *Rule 1:* >> Use "org.gwtproject" + module name as group id; module name with "gwt-" >> prefix as artifact id. This rule is used by `gwt-http`: >> >> GROUP_ID: org.gwtproject.$MODULE >> ARTIFACT_ID: gwt-$MODULE >> >> *Rule 2:* >> Use "org.gwtproject" + module name as group id; module name without >> "gwt-" prefix as artifact id. This rule is used by `gwt-event`, >> `gwt-place`, `gwt-safehtml`, `gwt-storage`, `gwt-timer`: >> >> GROUP_ID: org.gwtproject.$MODULE >> ARTIFACT_ID: $MODULE >> >> *Rule 3:* >> Use "org.gwtproject" as group id; module name with "gwt-" prefix as >> artifact id. This rule is used by `gwt-xhr`: >> >> GROUP_ID: org.gwtproject >> ARTIFACT_ID: gwt-$MODULE >> >> *Rule 4:* >> Use "org.gwtproject" as group id; module name without "gwt-" prefix as >> artifact id. This rule is used by `gwt-json`, `gwt-typedarrays`, `gwt-xml`, >> `gwt-xhr`: >> >> GROUP_ID: org.gwtproject >> ARTIFACT_ID: $MODULE >> >> *Rule 5:* >> Other rules: `gwt-window`, `gwt-history`. >> >> I suggest we apply rule 4 to all the modules. It means always using >> "org.gwtproject` as group id, and use `gwt-` + module name as artifact id. >> There're several benefits. It helps people to find all the artifacts via >> the same group id. It also keeps consistency for the generated JAR files: >> each of them contains a "gwt-" prefix, thus they are GWT artifacts. >> >> Cheers, >> Mincong Huang >> >> [1]: https://repo.vertispan.com/gwt-snapshot/ >> > -- 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/7532d726-df51-457c-a29c-70d773d0bb25%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
