Jilles van Gurp - Latest Comments

Re: maven: good ideas gone wrong

pik — Mon, 05 Nov 2012 20:28:56 -0000

pom pom pom ... i resisted to you..still using ANT, I make a complex ant file from little xml (package name + names of jars + optional extra ant xml) with xslt. My Xslt contains the model of a quite complex ant build file, that makes build, bin, src, zip, test, testzip etc.. 1 time a year perhaps i change something, but not recently. Yes, it does not download the files. But try to install JAI (other craziness) with Maven.. I liked so much RESIN because I was doing with it TextPad in app folder + F5, like the scripts languages that you mention...for classes, not for jsp ;-)

Re: Server side development sucks

Thomas — Tue, 09 Oct 2012 09:23:44 -0000

+1 for James on the Wicket stuff. For dev, run Jetty from the workspace and you even get hot code replacement :-) Spring is a (non-)solution looking for a problem anyway!

Re: Leaving Nokia

Jilles van Gurp — Tue, 28 Aug 2012 01:55:32 -0000

I'm definitely not worried and actually rather optimistic and excited about leaving Nokia. Fun is definitely high on the agenda.

Re: Leaving Nokia

Jilles van Gurp — Tue, 28 Aug 2012 01:54:13 -0000

Sure, of course I remember you. GX was a fun place to be and it is good to know I'd be welcomed back. As you guessed, I'm indeed going to try to find something in Berlin, though I'm not excluding the possibility of moving elsewhere.

Re: Leaving Nokia

Agathe Battestini — Tue, 28 Aug 2012 00:43:52 -0000

I'm not worried for you:) There are plenty of projects out there that would be lucky to have you. Good luck, and have a lot more fun!

Re: Leaving Nokia

Magnus Ekvall — Tue, 21 Aug 2012 03:42:00 -0000

Hi Jilles, Why not go back a few steps towards your roots and join <gx> again? You'd be more than welcome! Otherwise success finding a fitting challenge in Berlin. Greetz, // Magnus (de Zweed @ GX, if you remember...)

Re: Leaving Nokia

Jilles van Gurp — Thu, 16 Aug 2012 09:28:59 -0000

The pleasure was mutual. How are you enjoying life outside Nokia?

Re: Leaving Nokia

JohnK — Thu, 16 Aug 2012 09:20:44 -0000

Good luck for future endeavors Jilles - it was a pleasure arguing with you about OpenID ;)

Re: Dutch beer

site — Tue, 07 Aug 2012 23:21:33 -0000

I have heard Dutch beer are the best. I have tried several too...

Re: Scrum: Agile madness

Dave Nicolette — Tue, 24 Jul 2012 10:00:39 -0000

"You can't substitute experience with process."

That's the problem in a nutshell. Well said.

Re: X-Plane 9 review

Guest — Sat, 14 Jul 2012 23:23:07 -0000

For me I know nothing about planes and when I got it for $30 it was a big waste of money, I finally found out how to fly a plane but it still sucks. I want a FULL refund

Re: maven: good ideas gone wrong

SeeD419 — Sat, 30 Jun 2012 22:54:13 -0000

Yeah, I've been dealing with maven all day. I kept thinking to myself that this was vastly over-complicated and a huge waste of time, but I was trying to entertain new technologies. I couldn't agree more with your post. Fuck Maven.

Re: git-svn flow

Jilles van Gurp — Tue, 19 Jun 2012 13:25:38 -0000

Thanks!

I haven't run into that particular issue yet, though there is a small risk for this. In any case, the risk is all client side, git svn simply uses svn underneath so it can't do any more damage than a normal svn user. The way svn works, a mid dcommit collision with other commits would result in some commits making it into svn until a commit fails. Each svn commit is transactional and svn won't allow you to commit unless you are up to date. So, that would leave you in a state where some of your commits made it in and some didn't. Basically a git svn rebase followed by another dcommit will fix this. You may have some conflicts in the remaining commits, which you'd have to fix.

Re: git-svn flow

Jan Tietjens — Mon, 18 Jun 2012 05:32:25 -0000

Thank you for this great article about the git svn workflow for teams. You describe exactly the same problems which we are facing at our company: Very large trunk, large refactorings at the horizon, instable builds. And we are also thinking about such a git svn workflow.

A question about git svn dcommit: Did you also get commit errors if someone else checks into the central svn repository during a git svn dcommit? How do you handle these? This is IMO a major drawback of the git svn solution.

Re: maven: good ideas gone wrong

Yotam Madem — Sun, 03 Jun 2012 09:04:51 -0000

"Every tool sucks if you use it wrongly" - not agree with this sentence.
The best tools should be designed in a way that it will be very difficult to use them wrongly. The basic things I put in my goals of writing a new software/tool is: how to prevent the user from using it wrongly.

Re: Scrum: Agile madness

Rfrank — Sun, 03 Jun 2012 07:18:17 -0000

Yes, the Scrum Master has no clothes, it's time to end the cult of agile and get on with common sense.

Re: maven: good ideas gone wrong

Nikola Petrov — Thu, 31 May 2012 05:27:53 -0000

Actually some of the ideas you are describing about the application server loading code directly is maybe the strongest point for using the play framework(google it).

It is good that after all we are not the only people that hate building code externally. I had some fun reading your post, thanks for that :)

Re: simple note encrypt/decrypt with AES in javascript

Beatagray10 — Wed, 02 May 2012 15:44:22 -0000

Have you found the issue of why it doesn't work with IE7? I can tell that it works with Firefox just fine

Re: Generic event code

TashiaMBurton — Sun, 15 Apr 2012 22:09:38 -0000

This is a great solution to the Java problem.

Re: Lumia 800

Jilles van Gurp — Fri, 30 Mar 2012 14:26:10 -0000

It's 20:22, the next day and I'm down to 15%. So I got a good solid two working days out of this. During that two working days I did about 45 minutes of internet radio listening (my morning routine of half consciously absorbing bbc world); I installed creative studio and played with it for about 30 minutes, I had email syncing on to gmail and outlook as well as the MS weather app updating it self, I did some email reading during the day, a few minutes of browsing, and I installed the firmware referred above yesterday morning. Technically it was on the usb cable charging while I did the update and it came out 96% full of juice around 10am yesterday morning after about 20 minutes on the cable. Not bad. It's way past the moment where it would normally have died before I applied the latest firmware, which in my experience would have been somewhere during last night, and will probably last me until I plug it in around bed time (around midnight usually).

I'm impressed.

Re: maven: good ideas gone wrong

Pasanivea — Tue, 27 Mar 2012 03:26:53 -0000

Great! Thanks for sharing...MAVEN IS CRAP! :)

Re: maven: good ideas gone wrong

Mavenhater — Thu, 22 Mar 2012 20:28:45 -0000

The maven (and JPA - but that is another blog matter) fans are all slaves to marketing. A project comprehension tool? How does a directory structure and a huge xml file make me comprehend a project? All maven ever did to me was to make me confused. Why is the build failing when it built OK the last time (and I haven't changed anything)? And why does it take 15 minutes to run (ant takes 3.5). Use maven at your own peril.

Re: log4j, maven, surefire, jetty and how to make it work

Richard — Sun, 11 Mar 2012 10:18:14 -0000

The title mentions a servlet container and other maven plugins which you only briefly mention in your article. It would be better to remove these keywords from the title otherwise more people will be redirected to your article when looking for such things.

Re: maven: good ideas gone wrong

Jimmy14 — Tue, 06 Mar 2012 19:05:01 -0000

I tried to tell the clowns where I work that maven is breaking Eclipse's incremental compiler, but no one seemed to care.
The kinds of people who really, really hate maven are the power users. These are incidentally the same people who have to debug the system when maven screws it up (not the incompetent fanboys who were pushing the crap in the first place).

Re: maven: good ideas gone wrong

Matt — Sun, 19 Feb 2012 11:52:01 -0000

Totally agree with you. It has been retro fitted to a legacy app where I am. This is unbelievablely bad!!!