Ideally we should try to match the tag with the version in the POM. So if the POM says "1.0" as it does now, so should the tag. If you prefer an extra "0" right awaw, not for subsequent versions, could we add it to the final POM version, too?
Not sure about extra artifactId for e.g. the "data" repo like "devicemap-data"? The current artifactId for "classifier" as "devicemap-java" is a bit misleading, after all the "devicemap-parent" is actually on top of the "java" sub-tree. If the .NET clients use something completely different than Maven then maybe the term "parent" could be kept there, the descriptive title is nevertheless "Java Parent". P.s.: What about the "test-data"? So far only "device-data" (with artifactId "devicemap-data") is a 1.0 candidate. Do we no longer need those test-data? If not needed, then following a tag (I tagged them at least with all the ODDR sync-ups) it could be purged, otherwise it should also be versioned like the other repos. Werner On Tue, Jul 8, 2014 at 12:13 AM, Reza Yahoo <[email protected]> wrote: > When everyone signs off on the build, I was thinking that would be 1.0 and > I will make a tag. I didn't want to create tags or anything right now cause > we have a bit of back and forth. > > As for 1.0 or 1.0.0, either works. 1.0.0 is better, allows more version > flexibility. > > Something to think about is how we version data vs code... > >
