Michiel Meeuwissen wrote:
Ernst Bunders wrote:
So then I would checkout mmbase at, say, version 1.8.0 and then set the
mmbob related contributions to the version I want to build. The only
problem is of course that there is no way to formalize the relation between
the mmbob version and the mmbase version. You'd have to know. But i suppose
it can be done this way.
That's what I mean.
Formalization is nice, but you can also call it overkill. Just typing in
the README.txt of mmbob that such and so version of mmbob need such and so
version of mmbase would suffice to start with, isn't it? The most important
thing is that it can somehow be known.
We'll probably also will make provisions in the component-framework for
version-dependencies?
Well, isn't that a good reason to go all out in maven?
after all, it was developed exactly for the purpose of managing complicated
cross dependencies (by apache)
Ernst
Michiel
--
Michiel Meeuwissen mihxil'
Peperbus 107 MediaPark H'sum []()
+31 (0)35 6772979 nl_NL eo_XX en_US
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers
