Hi Joakim, On 19/06/07, Joakim Erdfelt <[EMAIL PROTECTED]> wrote:
I want to see maven 2.1 fixed in regards to project model resolution. The current mess in maven/components is completely unusable within archiva. If that occurs, then the rest of the dependency graph resolution bits will fall into line easily. (It did for archiva.)
I think this is the key issue here. I appreciate the problems you experienced in archiva and why you were forced to do your own thing. This really needs to be addressed in 2.1 to bring the new dependency graph code and archiva into line to avoid duplicating efforts. I have no doubt that the archiva graph is theoretically more accurate than the dependencies resolved by maven core, but I'm currently interested in reflecting what is actually happening within maven core -- bugs and all. I'll continue to focus on these diagnostic tools for 2.0.x since they will be a big time saver for us, but hopefully 2.1 and archiva can combine forces and make this trivial in future. Cheers, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
