On Mon, Mar 19, 2012 at 2:54 PM, Fabian Christ <[email protected] > wrote:
> Hi, > > Am 19. März 2012 14:36 schrieb Daniel Spicar <[email protected]>: > > But how do you handle maven version numbers? In order for this to make > > sense I think you handle versions manually per module. That means after a > > release you do not make the module depend on the latest SNAPSHOT versions > > of all its dependencies but rather you stick with the oldest release > I tink you mean newest release > > version you depended on and only increment to the next SNAPSHOT when you > > require new features or some other reason may require an update (e.g. > major > > version change). > > I think this is the way to go. Currently, we have the same issue in > Stanbol and I am thinking about doing it exactly this way. > Why not release a fresh parent whenever a set of modules is released? All modules in trunk should then be updated to use the new parent. The effect is the same: a module depends only on relased components unless there is reason to depend on snapshot in which case the modules will be released together. I think the maven versions plugin comes in very handy here. I don't think there's currently a need to work with different versions at runtime, so I don't think we have to care about OSGi versions right now. Cheers, Reto > Best, > - Fabian > > -- > Fabian > http://twitter.com/fctwitt >
