Has anyone stopped to ask any other projects (both apache and non-apache) who have done what is being proposed here:
- How they found it? - What did they do well? - What did they do poorly? - What pain points did they have? - What would they do differently, if they had to do it again? - What benefits did they receive? - Did the expected benfits match the results? (just to name a few questions off of the top of my head, I'm sure that there are others). Effectively, a PIR of a project that has already gone this route. The fact that a lot of people have said +1 and there are still discussions around how to best set up a repo, means to me, that there is lots more room for dissussion. -Chris On Thu, Sep 6, 2012 at 3:30 PM, David Jencks <david_jen...@yahoo.com> wrote: > > On Sep 5, 2012, at 10:08 PM, Kristian Rosenvold wrote: > > > 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 think from my experience that your proposed plugin is sort of essential > for working with maven code. I usually give up quickly because I can't > find all the dependencies that some plugin I want to improve uses in a > finite amount of time. > > However, I wonder how useful it will be on projects with more separation > between interface and implementation, as in some osgi projects. If you > have a module AIntf with interfaces and then the implementations in AImpl > and project B uses AIntf how do you know to check out AImpl? (or the > several AImpls). I'd love to see this work.... > > > > > 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 ;) > > I like this division. > > And BTW as a very occasional maven patcher and git user elsewhere I think > git would be an improvement over svn. > > thanks! > david jencks > > > > > Kristian > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
