Thanks, then while the DDR Simple module will wait for "data" to contain the necessary fixes, but target it separately like other modules. Most likely a 1.0.0 the POM currently is at 1.0.0-SNAPSHOT.
For any (already released) artifacts, at least of "java" or "resource" type, how can we get it at the very least here? http://repository.apache.org/content/groups/snapshots/ DeltaSpike http://repository.apache.org/content/groups/snapshots/org/apache/deltaspike/ is a good example for a rather heterogenous build concept, as different modules have very different maturity levels and version numbers, so while there are others with strict version number consistency, we may use one of those as an example. More importantly, even some of the parts inside DeltaSpike still incubating like https://repository.apache.org/content/groups/public/org/apache/deltaspike/cdise/cdise-project/ are also found in the public repo, not just Snapshot. What does DeltaSpike do we're missing? IMHO each of those which can be delivered via Maven/Gradle/Ivy type build systems tagged here: http://svn.apache.org/viewvc/incubator/devicemap/tags/releases/ should ideally also be on a Maven repository. If DeltaSpike meets all Apache constraints regarding which artifacts go where, then I see no reason not to publish data and API that is out there by now. Thanks to Maven users can decide if they want a 1.0.0 or 1.0.1 version of the data files, and matching API projects refer to each of them, but to find them without having to build the entire DeviceMap repo from source all the time, some binaries should be in a Maven repository, too. Werner On Tue, Aug 5, 2014 at 5:18 PM, Bertrand Delacretaz <[email protected]> wrote: > On Tue, Aug 5, 2014 at 4:04 PM, Werner Keil <[email protected]> wrote: > > > > ...@Bertrand/all, what is your general preference about an "umbrella" > delivery vs. doing them > > independently, at least at some point when more of them have relevant > changes?... > > Not sure what "them" is but in general I'd say the DeviceMap modules > are sufficiently small and independent to be released separately as > needed. Just mention any relevant dependencies on specific versions > in the release notes. > > Also, I wouldn't care about keeping version numbers in sync between > modules, that doesn't bring much IMO. > > -Bertrand >
