2012/9/14 Olivier Lamy <[email protected]>: > As far I can see most git beginners use git as they use svn. (hey do > you remember when you started git and fully break your local clone > trying to merge some local branches: don't say to me it never happened > :-) )
I crashed and burned. Badly. Multiple times. > So our maven tooling must be accessible for the mass (sure extra > options for geek/nerds is always welcome :-) ) and be operational for > basic/daily stuff of majority of dev folks. >> >> As can be seen from the wiki, I am somewhat at loss for a good >> branchless solution. I think the best solution is probably to support >> "trunk only" when running branchless, effectively >> just move all the checked out dependencies to SNAPSHOT and use trunk >> for everything. I think we can call it svn mode ;) > Yup again we must try to build the most generic plugin for most used > scm (sure better to concentrate efforts on most populars: svn and > git). I think it's really ok to default to "trunk" mode (maybe unless you're checking out a tag of the main project) it's the one feature I remember very clearly I would've enjoyed the first time I (ever) tried to change something in maven. I remember the first time I checked out maven source code quite clearly, I was checking out repositories like crazy and building just more and more dependencies until I finally managed to find the one thing I was interested in. At the time it felt like I had built half the known universe of components before I reached my goal ;) (And they all have similar-sounding names; hey; didn't I check out archiver-archiver just 10 minutes ago ???) Of course, workspace-plugin would keep the pom changes in the top-level project as a separate commit, so it doesn't mess up the actual changeset in the end. (We could support a "patch" command too) Just my 50 Øre (0.5 Norwegian kroner, recently deprecated). Kristian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
