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

2018-03-24 Thread Colin Alworth
"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: Enhancement: DateTimeFormat: Add format/formatYear parameter to guess century on yyyy

2018-03-24 Thread Cy Kilbourn
If you use the "yy" pattern instead, the default behavior will be to guess the year based on the 20 yrs forward, 80 yrs back logic. On Wednesday, December 1, 2010 at 8:46:03 AM UTC-5, HerrB92 wrote: > > Hi, > > I'm sorry, I don't know if there is and this is the right place to > place an

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

2018-03-24 Thread Ahmad Bawaneh
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

2018-03-24 Thread Mincong Huang
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

2018-03-24 Thread Thomas Broyer
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 >

[gwt-contrib] Naming convention for ported GWT modules

2018-03-24 Thread Mincong Huang
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