Getting…Angry…
Here's my angry issue of the day. I'm working on a project that uses a software development kit (SDK) from a third party. The third party provides some Maven plugins to help construct the necessary files for deployment into their framework. So far, so good. The problem I ran into that made me want to scream in someone's face is that their plugin for building their specific archive has several paths hard coded in their plugin.jelly using the "jelly:set" tag. This means I can't override them in my project.properties. This means that I have to have the exact directory structure they "recommend."
The part that makes me slightly mad is that there's no reason to do this unless you 1) are dealing with dynamic properties that are changing in your script, 2) specifically don't want to give people the ability to override your property, or 3) don't know any better. Unfortunately, I'm pretty certain we're dealing with #3. Of course, I can open a bug and get it fixed, but I would have to do any number of slightly painful things to make it work for me like wait for another release / patch then get the change then restructure my projects the way I like (moving my stuff around in source control). If it's a patch each developer will have to remove their old copy from their special local repository then we'll have to put the new version on an internal Maven proxy.
Or I can just write a post complaining about it and live with a directory structure I don't particularly like and get on with my life. Venting complete, anger…subsiding…
Leave a Reply