Re:The 10 commandments of good source control management
by CodeMage on Tuesday May 03, 2011 @10:31AM
(#2510056)
What's wrong with Maven? I'm asking this as someone who hasn't used it and who wanted to give it a whirl. Any input would be much appreciated.
Re:The 10 commandments of good source control management
by gchpaco on Tuesday May 03, 2011 @01:34PM
(#2510883)
If you want to do something simple it takes a 60 line pom.xml to express it. If you want to do something a little trickier it takes another 60 lines and three hours minimum of poking around at inadequately written docs. If you want to do something difficult, forget it. Ant, which is a nightmare of usability and continues to make me wake in the middle of the night screaming, is at least as complex to configure, better documented and is not a quarter as constrained as Maven.
That said the Maven dependency model isn't too bad; fortunately you don't have to adopt Maven to get it, you can just use Ivy.
Re:The 10 commandments of good source control management
by efsavage on Wednesday May 04, 2011 @07:31AM
(#2513489)
You've got that backwards. The "90s java mindset" is the lib dir. The 2011 approach is Maven, as evidenced by the fact that 100% of my clients use it, and practically every major open source project uses it as well.
Perfect? No. But standard practice? Yes.
However, yes, checking in dependencies with your code is the way to go.
Deps that can be reliably included with just a meta-descriptor (i.e. Gemfile, pom.xml, etc.) are still exceptionally rare. Thus the natural choice is to put the rest right next to the code that it belongs to. Well, natural choice unless you're stuck in a 90s java mindset...