+1 for moving to git from me as well. We. use Maven in about 1000 inhouse projects (95% still using SVN) and Maven adding artifactId out of the blue at free will in inheriting projects is a pain in the neck for SVN as well, while trying out releases completely locally with git is really helpful IMO. Making vendor-releases before a real release is available is another place where git shines.
Regards Mirko -- Sent from my mobile On Jul 24, 2013 7:16 PM, "Fred Cooke" <fred.co...@gmail.com> wrote: > Totally fair! :-) > > I don't have the time or wrist-strength to go through JIRA and dig out all > of the examples, however anyone can do that. I don't use SCM except during > release, either. > > I'd argue that it's not good enough for m-rel-p use, however it may well > be good enough for MOJO use cases of that. Just not for the general case, > or majority of general cases, perhaps. > > 1. Absolutely, there's no competition at all, I hate SVN with all of my > heart, as do 2 of the original authors of SVN! LOL <makes note to do a > video compilation of their comments> > 2. See above, I don't think so, but perhaps for MOJO it's fine. > 3. Same, I don't use it. > > IMO the SVN-ness is in more than just the SCM sections of Maven, though. > The way m-site-p works, and (actually) the way the core of Maven which it's > based on works, is SVN-infected too. As any Git user knows, Git repos are > standalone, whereas the norm for SVN is to have a big shared repo and some > type of hierarchy. This changes the natural way to deal with some things > and some parts of Maven are hard-coded to do it in the SVN way. I've put > some solid use on the pair for MY use cases, and come up with various > issues. Some things I have (ugly) work arounds for, others I just put up > with. It works, and beats using SVN (having your hands cut off with a rusty > teaspoon beats that IMO), but it really needs some work to generalise it > and expunge the SVN-ness, even if that means going to a Maven 3.2 from 3.1 > and breaking a traditional behaviour and providing an alternative to > configure it, or some such drastic thing. To not make changes is to > stagnate. Git _IS_ the future and SVN _IS_ slowly dying, the sooner the > Maven community step up and swallow the pill of properly fixing that, the > better IMO. If the release-madness is cleaned up, I'd even be willing to > get stuck in and help! :-p > > I guess I withdraw my -1 and replace it with a "+1, and suffer" vote :-) > It'd be good to see the wrinkles ironed out and to get first-class support > throughout the Maven build infrastructure. Bring it on! > > Fred. > > On Wed, Jul 24, 2013 at 6:56 PM, Lennart Jörelid < > lennart.jore...@gmail.com> wrote: > >> I do get the feeling that you refer to the general Git functionality as >> implemented by the Maven SCM for Git. >> In that case, I agree completely with your statement. >> >> Do you feel that the (relatively limited) SCM feature set used within the >> normal operation of the maven-release-plugin is also inferior to what is >> required for the Git integration? >> Basically, I feel that: >> >> >> 1. While doing normal development work (particularly >> branching/merging) external to Maven, I perso feel that Git >> Svn >> 2. The Maven-release-plugin uses a relatively limited feature set of >> all VCSs. While the SCM/Git integration may be inferiour for general use, >> is it good enough for use by the m-r-p? >> 3. I perso only uses the maven-scm integration for work with m-r-p. >> In most/all other cases, I simply use the VCS client itself - and the VCS >> client >> maven-scm integration for a particular VCS. >> >> I agree that stuff that works poorly (the Maven SCM/Git integration, if I >> interpret your view correctly) should be fixed - but I'm essentially asking >> if you (all devs, that is) use the mvn scm for other jobs than the >> Maven-release-plugin. >> If not, I think we can move to Git to get the boons for everyday >> development and deal with the pains of Maven/Scm integration as we go. >> Fair? >> >> >> >> 2013/7/24 Fred Cooke <fred.co...@gmail.com> >> >>> No, it was a contraction. The full form was "Git functionality in Maven >>> doesn't work "well" at all.". Both Maven and Git work wonderfully, while >>> not in the same terminal :-p >>> >>> >>> On Wed, Jul 24, 2013 at 5:12 AM, Lee Thompson <bm...@yahoo.com> wrote: >>> >>>> Think you have it backwards. Didn't you reverse "git" and "maven" in >>>> this statement? >>>> >>>> On Jul 23, 2013, at 9:45 AM, Fred Cooke <fred.co...@gmail.com> wrote: >>>> >>>> > Git doesn't work "well" at all. You can't set env vars and have them >>>> > be respected, it does expensive operations unnecessarily, you're >>>> > unable to enter meaningful tag data, and many other broken things, >>>> > quite a few of which are down to SVN-ness that's built into Maven. It >>>> > does work, if you bend over for it. I'm not fond of bending over. >>>> > >>>> > On Tue, Jul 23, 2013 at 4:32 PM, Lennart Jörelid >>>> > <lennart.jore...@gmail.com> wrote: >>>> >> +1 >>>> >> >>>> >> DVCS works well with the maven-release-plugin. >>>> >> >>>> >> ... but the Maven Docs indicating how sites/URLs/VCSs should be >>>> sculpted for >>>> >> multi-mode projects could do with a profound overhaul. >>>> >> >>>> >> >>>> >> 2013/7/23 Tony Chemit <che...@codelutin.com> >>>> >>> >>>> >>> On Tue, 23 Jul 2013 15:19:50 +0200 >>>> >>> Baptiste Mathus <bapti...@codehaus.org> wrote: >>>> >>> >>>> >>> +0, works fine to me on svn. >>>> >>> >>>> >>>> Hi, >>>> >>>> >>>> >>>> The following vote is a first (baby) step to keep us moving after >>>> our >>>> >>>> recent discussion about this. >>>> >>>> >>>> >>>> *Just checking here nobody is against moving mojo to git, whatever >>>> be >>>> >>>> the >>>> >>>> path.* >>>> >>>> >>>> >>>> (So, this *vote is NOT* about dirty details like how many >>>> repositories, >>>> >>>> when, how, github or not, and so on. There'll be other votes and >>>> >>>> discussions if this one succeeds). >>>> >>>> >>>> >>>> [ ] +1: yes, I'd like to be able to use pure git at mojo@codehaus >>>> >>>> (without >>>> >>>> having to resort to git-svn and the likes) and ok with the idea of >>>> a >>>> >>>> migration away from svn. >>>> >>>> [ ] 0: prrrt. Don't care. >>>> >>>> [ ] -1: bad idea, keep it as-is. >>>> >>>> >>>> >>>> This vote is open for 72 hours. >>>> >>>> >>>> >>>> Thanks >>>> >>>> >>>> >>>> -- Baptiste >>>> >>> >>>> >>> >>>> >>> >>>> >>> -- >>>> >>> Tony Chemit >>>> >>> -------------------- >>>> >>> tél: +33 (0) 2 40 50 29 28 >>>> >>> email: che...@codelutin.com >>>> >>> http://www.codelutin.com >>>> >>> >>>> >>> >>>> --------------------------------------------------------------------- >>>> >>> To unsubscribe from this list, please visit: >>>> >>> >>>> >>> http://xircles.codehaus.org/manage_email >>>> >>> >>>> >>> >>>> >> >>>> >> >>>> >> >>>> >> -- >>>> >> >>>> >> -- >>>> >> +==============================+ >>>> >> | Bästa hälsningar, >>>> >> | [sw. "Best regards"] >>>> >> | >>>> >> | Lennart Jörelid >>>> >> | EAI Architect & Integrator >>>> >> | >>>> >> | jGuru Europe AB >>>> >> | Mölnlycke - Kista >>>> >> | >>>> >> | Email: l...@jguru.se >>>> >> | URL: www.jguru.se >>>> >> | Phone >>>> >> | (skype): jgurueurope >>>> >> | (intl): +46 708 507 603 >>>> >> | (domestic): 0708 - 507 603 >>>> >> +==============================+ >>>> > >>>> > --------------------------------------------------------------------- >>>> > To unsubscribe from this list, please visit: >>>> > >>>> > http://xircles.codehaus.org/manage_email >>>> > >>>> > >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>>> >>> >> >> >> -- >> >> -- >> +==============================+ >> | Bästa hälsningar, >> | [sw. "Best regards"] >> | >> | Lennart Jörelid >> | EAI Architect & Integrator >> | >> | jGuru Europe AB >> | Mölnlycke - Kista >> | >> | Email: l...@jguru.se >> | URL: www.jguru.se >> | Phone >> | (skype): jgurueurope >> | (intl): +46 708 507 603 >> | (domestic): 0708 - 507 603 >> +==============================+ >> >> >
