Carsten Ziegeler wrote:
Vadim Gritsenko wrote:
So - as mentioned on the top of email - it is huge pain to assemble such
a tree, but it is absolutely possible to do.
Yes, but the tree is not what you might expect - it might be that we
have a cocoon-core 2.2.2 while we still use cocoon-pipeline-api 2.2.0
with impl 2.2.7.
Yup, no problem. I'd even expect so down the road.
And even worse, you might want to decide to use impl
2.2.5 as you think that it works better than 2.2.7.
If one decides so, yes.
So what one could do, is maintain a list of all modules with their
latest versions, write a three lines script which checks out these
modules and versions, and you get what you want (at least I think this
is what you want).
Yes, can I have this magic three line script, please :) Even better, can we have
it checked in under .../cocoon/tags/ so that *anybody* can get the script, run
it - and voila! - you get a release of cocoon built :)
Vadim
Oh, and we might have this list already in the root
pom in the version depmgmt (although I still think that this is wrong).
Carsten
