2014-07-24 8:49 GMT+06:00 Olivier Lamy <ol...@apache.org>: > On 24 July 2014 05:43, Stephan Classen <st.clas...@gmx.ch> wrote: > > My first version of onami persist was (and still is) hosted on github. > > because your module is in a single git repo. > So here all the scm tree http://svn.apache.org/repos/asf/onami/trunk/ > will be moved to a single git repo. > Usually you release only one module > AFAIK maven release plugin doesn't support this very well (at least > for the moment) because there is no support of sparse checkout in svn. > I believe we already discuss of this when starting onami. > Again I have nothing against moving to git but you guys must take care > if all the tooling chain is supporting that. > > Maybe we should just use a single version for all modules and release them all at once? We have sandbox (do we need it with git?), branches, local copies of repository to experiment. Maybe we should have "release-ready" code in all modules in master? Also it will help with releasing ALL modules - we still have some modules we didn't release at all or released a long time ago.
It will also help with dependency/plugin management inheritance from parent pom. To update a plugin/dependency one now have to set it's version in the parent (so it will be inculded in the next release) and also in the module pom. When the parent of the next version is released, module pom can reference the new version and omit the explicitly specifiied plugin/dependency version. That is complicated and we can get rid of it. When building the whole tree maven complains about wrong parent relative path and/or wrong paret version (do not remember exactly). That will be fixed too. Probably there are some drawbacks I'm not aware of. WDYT?
