[gwt-contrib] Re: Naming convention for ported GWT modules

On Saturday, April 7, 2018 at 6:48:53 PM UTC+2, Jens wrote: > > > Fwiw, I can see zero reason why examples would be published to a Maven >> repo. > > > Well right, although quite a lot projects do so. But maybe just because > examples are part of a multi module project and they just deploy

[gwt-contrib] Re: Naming convention for ported GWT modules

> Fwiw, I can see zero reason why examples would be published to a Maven > repo. Well right, although quite a lot projects do so. But maybe just because examples are part of a multi module project and they just deploy everything to maven central. That would even be a stronger argument to

[gwt-contrib] Re: Naming convention for ported GWT modules

Yes, you are right, now both the importer and the cldr repository are available on github The importer : https://github.com/vegegoku/gwt-cldr-importer The gwt-cldr https://github.com/vegegoku/gwt-i18n-cldr the cldr uses the *org.gwtproject.i18n *groupId and *gwt-cldr *as artifactId Your

[gwt-contrib] Re: Naming convention for ported GWT modules

On Friday, April 6, 2018 at 6:16:50 PM UTC+2, Ahmad Bawaneh wrote: > > Hi > i am working on date pickers for domino-ui, mean while i found that in > order to support different locales in the date picker i need the > DateTimeFormat information for each locale, gwt in the other hand has a >

[gwt-contrib] Re: Naming convention for ported GWT modules

Hi i am working on date pickers for domino-ui, mean while i found that in order to support different locales in the date picker i need the DateTimeFormat information for each locale, gwt in the other hand has a decent support for datetime format informtion, so instead of adding my own

[gwt-contrib] Re: Naming convention for ported GWT modules

Fwiw, I can see zero reason why examples would be published to a Maven repo. Wrt events, each corresponds to a different GWT module: c.g.g.event+c.g.w.b.event, c.g.g.event.logical, and some adapters for when you need to mix org.gwtproject.event with c.g.g.event or c.g.w.b.event. We could also

[gwt-contrib] Re: Naming convention for ported GWT modules

What about org.gwtproject.sdk:gwt-$module and org.gwtproject.sdk:gwt-$module-processor (keep the optionally APT module flat within org.gwtproject.sdk group Id) org.gwtproject.examples:$lots-of-example-apps-using-any-gwt-module-combinations org.gwtproject.site:... org.gwtproject.tools:...

[gwt-contrib] Re: Naming convention for ported GWT modules

"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

[gwt-contrib] Re: Naming convention for ported GWT modules

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

Re: [gwt-contrib] Re: Naming convention for ported GWT modules

On Sat, Mar 24, 2018 at 12:27 PM, Thomas Broyer wrote: > > > On Saturday, March 24, 2018 at 10:30:10 AM UTC+1, 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-contrib] Re: Naming convention for ported GWT modules

On Saturday, March 24, 2018 at 10:30:10 AM UTC+1, 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 >