Martin von Gagern wrote:
On the whole, I spent way too much time tweaking Maven, time I'd rather spend working on my project code.
One of the most fundamental things about maven that you need to do to have a pleasant user experience, is to submit to maven.
In other words, you shouldn't spend time tweaking maven, you should rather spend time tweaking your project to work using the standard way maven works.
This is a big ask for many people I know, people come to maven going "but I want it to work like this, and maven won't let me".
Standardisation means that if you follow the standards, there is a whole class of problems that are already solved. If your code is in a standard place, you no longer need to tell anybody, whether a computer or a human, where your code is, they already know. If your release procedures are standardised, you no longer need to tell anybody, whether a computer or a human, how to release your code or where it lives, they already know.
Standardisation however doesn't help you if you want to invent your own standard. If you invent your own standard, you have to write the code yourself, and for me personally, rewriting your own standard is a waste of time and money.
> I now decided to abandon maven, at > least for my end user applications. I'm not sure what I'll be using > instead. Maybe some form of ant, with or without ivy, with or without > build files generated from xslt.So you replace an exercise in messing around with maven with an exercise in messing around with ant.
I don't see how that will help you focus on development. Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
