2012/9/5 Romain Manni-Bucau <rmannibu...@gmail.com>: > Last note: i think the plugin you speak about (create a kind of virtual > project) will be a nightmare. Scm are nice but can be broken and when you > dont have a 1:1 with remote repo it is even harder
I would really like some elaboration on this, since I'm not sure I understand what you're trying to say. I work with the maven codebase all the time and I generally find working with layered components that are from different release modules to be a little painful although manageable. Most of this pain does /not/ stem from the fact that they are in different version control systems or different checkouts from the version control system (which they are). I like to think there are a few main use cases for checking out code: A) I want to fix a single problem/issue and when I'm done with that I'm going to submit a patch and get on with my life. B) I'm hooked. I fix things in a limited subset of the code base all the time. So I need to keep it recent, fresh and patched. C) I'm all over the place. I do global updates to dependencies and reformat code like there's no tomorrow. I think these are the three models we need to support well. I think especially A is important, since it's the gateway to entry ;) Kristian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org