Comments for Nim's braindump http://blog.lick-me.org Swords, code and a dirty mind! Thu, 17 Nov 2011 15:57:04 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Maven sucks? by Bram http://blog.lick-me.org/2010/01/maven-sucks/comment-page-1/#comment-85 Bram Thu, 17 Nov 2011 15:57:04 +0000 http://blog.lick-me.org/?p=94#comment-85 Are you implying that non-free projects somehow have "better" documentation? I'm mildly amused by that :-) Dismissing something, or ranting about it, because it's seemingly "hard to use" seems counterproductive to me. Granted, parts of the maven documentation are crap or nonexistent. But the basic use case of maven (building a java project) is very straightforward. It's a powerful tool, so it's only natural that getting the most out of it takes some time and effort. Whoever said that software development was (meant to be) easy? Are you implying that non-free projects somehow have “better” documentation? I’m mildly amused by that :-)

Dismissing something, or ranting about it, because it’s seemingly “hard to use” seems counterproductive to me. Granted, parts of the maven documentation are crap or nonexistent. But the basic use case of maven (building a java project) is very straightforward. It’s a powerful tool, so it’s only natural that getting the most out of it takes some time and effort. Whoever said that software development was (meant to be) easy?

]]> Comment on Maven sucks? by alan http://blog.lick-me.org/2010/01/maven-sucks/comment-page-1/#comment-84 alan Thu, 17 Nov 2011 07:20:30 +0000 http://blog.lick-me.org/?p=94#comment-84 To add my 2 cents: My only real beef with Maven, and most free projects, is its poorly organized and ineffectual documentation. Basic questions have taken me much longer than it should have to find answers. And Maven is hard to use. It suffers from "it easy to use (once you know how to use it and get used to using it)" syndrome, which is not how I define easy to use. Developers should not defensively dismiss rants. Although ranters are ranting and "taking the piss out" they could be making valid points about real weaknesses of said software. To add my 2 cents: My only real beef with Maven, and most free projects, is its poorly organized and ineffectual documentation. Basic questions have taken me much longer than it should have to find answers. And Maven is hard to use. It suffers from “it easy to use (once you know how to use it and get used to using it)” syndrome, which is not how I define easy to use. Developers should not defensively dismiss rants. Although ranters are ranting and “taking the piss out” they could be making valid points about real weaknesses of said software.

]]> Comment on Maven sucks? by David http://blog.lick-me.org/2010/01/maven-sucks/comment-page-1/#comment-78 David Mon, 19 Sep 2011 19:53:09 +0000 http://blog.lick-me.org/?p=94#comment-78 One sign of software that is far too cumbersome and hard-to-use is that all the supporters of it have the broken-record refrain that the whiners are all just incompetent users. Come on, folks, if Maven really was that awesome, it would make things simple and easy to use from the first. But the things it's supposed to make simple - dependency management, multiple sub-projects, automated build - those are exactly the things that users stumble over again and again. I've been using Maven for years now and often experience odd, upsetting difficulties with life-cycle surprises, dependency surprises, and the inability of Maven to understand dependencies of sub-projects in isolation from a huge, monolithic project build. It makes some things better, yes, but at the expense of a great deal of learning curve, random configuration errors, and very poorly-executed documentation and configuration cascade issues. Much is hidden and/or hard to troubleshoot. One sign of software that is far too cumbersome and hard-to-use is that all the supporters of it have the broken-record refrain that the whiners are all just incompetent users. Come on, folks, if Maven really was that awesome, it would make things simple and easy to use from the first. But the things it’s supposed to make simple – dependency management, multiple sub-projects, automated build – those are exactly the things that users stumble over again and again. I’ve been using Maven for years now and often experience odd, upsetting difficulties with life-cycle surprises, dependency surprises, and the inability of Maven to understand dependencies of sub-projects in isolation from a huge, monolithic project build. It makes some things better, yes, but at the expense of a great deal of learning curve, random configuration errors, and very poorly-executed documentation and configuration cascade issues. Much is hidden and/or hard to troubleshoot.

]]> Comment on Maven 3 resource filtering weirdness by christian posta http://blog.lick-me.org/2010/10/maven-3-resource-filtering-weirdness/comment-page-1/#comment-74 christian posta Wed, 24 Aug 2011 16:53:50 +0000 http://blog.lick-me.org/?p=149#comment-74 Thanks so much for posting this. Helped us figure out the exact same resource-filtering issue. This has got to be a bug or something... they should at least spit out a warning message when they see the @ sign and it's not being used as a token delimiter. LOL... and you're right, what kind of language is that for the explanation of the @ sign???? Goodness... their docs suck for that one. Thanks so much for posting this. Helped us figure out the exact same resource-filtering issue. This has got to be a bug or something… they should at least spit out a warning message when they see the @ sign and it’s not being used as a token delimiter. LOL… and you’re right, what kind of language is that for the explanation of the @ sign???? Goodness… their docs suck for that one.

]]> Comment on On naming Interfaces by Michael http://blog.lick-me.org/2011/03/on-naming-interfaces/comment-page-1/#comment-59 Michael Wed, 06 Apr 2011 16:11:35 +0000 http://blog.lick-me.org/?p=195#comment-59 I'd rather do it the other way round: Suffixing the concrete classes with 'Impl'. In my opinion it's more clean (no garbage when you're searching for a Car class) and 'safer' (warning to the developer when they see that 'Impl' word, programming to an interface as its named). I've seen a lot of .NET devs who do that kind of prefixing. Even with local(!) variables lol I’d rather do it the other way round: Suffixing the concrete classes with ‘Impl’. In my opinion it’s more clean (no garbage when you’re searching for a Car class) and ‘safer’ (warning to the developer when they see that ‘Impl’ word, programming to an interface as its named).

I’ve seen a lot of .NET devs who do that kind of prefixing. Even with local(!) variables lol

]]> Comment on The Agile Samurai: Mini book review by Bram http://blog.lick-me.org/2011/02/the-agile-samurai-mini-book-review/comment-page-1/#comment-56 Bram Mon, 21 Feb 2011 20:04:57 +0000 http://blog.lick-me.org/?p=187#comment-56 You're very welcome, of course. Swords and code proved helpful, my dirty mind however was of very little use here. I've yet to find a book that manages to combine all three ;-). But in all seriousness, you did an excellent job on the planning chapter. That one alone makes the book worth buying. You’re very welcome, of course. Swords and code proved helpful, my dirty mind however was of very little use here. I’ve yet to find a book that manages to combine all three ;-) . But in all seriousness, you did an excellent job on the planning chapter. That one alone makes the book worth buying.

]]> Comment on The Agile Samurai: Mini book review by Jonathan Rasmusson http://blog.lick-me.org/2011/02/the-agile-samurai-mini-book-review/comment-page-1/#comment-55 Jonathan Rasmusson Mon, 21 Feb 2011 14:20:49 +0000 http://blog.lick-me.org/?p=187#comment-55 Hi Bram. Thank you for reviewing the agile samurai. Glad you liked the planning chapter. I worked to make people see how planning a software project isn't all that much different than planning for a busy weekend. And I should have known someone with 'swords and code' would have been a good reference for samurai accurate use of the samurai term :) Thanks again. All the best in your projects this year. Sincerely, Jonathan Rasmusson Hi Bram. Thank you for reviewing the agile samurai.

Glad you liked the planning chapter. I worked to make people see how planning a software project isn’t all that much different than planning for a busy weekend.

And I should have known someone with ‘swords and code’ would have been a good reference for samurai accurate use of the samurai term :)

Thanks again. All the best in your projects this year.

Sincerely, Jonathan Rasmusson

]]> Comment on Automating Maven Releases by Automating Maven Releases http://blog.lick-me.org/2011/01/automating-maven-releases/comment-page-1/#comment-51 Automating Maven Releases Wed, 26 Jan 2011 05:09:07 +0000 http://blog.lick-me.org/?p=176#comment-51 [...] time I would provide the release version(s) as command line arguments, the release plugin would... [full post] Bram Bram's braindump englishmaven 0 0 0 0 0 [...] [...] time I would provide the release version(s) as command line arguments, the release plugin would… [full post] Bram Bram's braindump englishmaven 0 0 0 0 0 [...]

]]> Comment on Howto: soapUI integration tests with Maven by Bram http://blog.lick-me.org/2010/02/howto-soapui-integration-tests-with-maven/comment-page-1/#comment-40 Bram Thu, 02 Dec 2010 06:03:26 +0000 http://blog.lick-me.org/?p=118#comment-40 None of my SoapUI tests have a JDBC step, but I suspect that this is a configuration issue. Try executing mvn resources:testResources before running the tests in eclipse, see if that helps. None of my SoapUI tests have a JDBC step, but I suspect that this is a configuration issue. Try executing mvn resources:testResources before running the tests in eclipse, see if that helps.

]]> Comment on Howto: soapUI integration tests with Maven by Lehari http://blog.lick-me.org/2010/02/howto-soapui-integration-tests-with-maven/comment-page-1/#comment-39 Lehari Wed, 01 Dec 2010 23:38:35 +0000 http://blog.lick-me.org/?p=118#comment-39 Thanks for you post. My soapUI tests have JDBC step. and I am using soapUi plug in inside eclipse. When the maven test goal is run , the regular tests run with out issues but th eone with DataSource and JDBC step fails. Do you know if any other settings are need for the JDBC? Thanks for you help Thanks for you post. My soapUI tests have JDBC step. and I am using soapUi plug in inside eclipse. When the maven test goal is run , the regular tests run with out issues but th eone with DataSource and JDBC step fails.
Do you know if any other settings are need for the JDBC? Thanks for you help

]]>