Although I don't recompile JSecurity all that often, when I do I am
very grateful for not having to use Maven.
Craig
On Nov 29, 2008, at 2:58 PM, Les Hazlewood wrote:
Hi Alan,
Yep, there's no doubt that we could have a jsecurity-web.jar. It'd be
very easy to do. Since JSecurity was designed from the ground up to
work in any environment, web or not, it would be pretty easy to
extract the web stuff into its own jar.
Aside from Ivy configs being better than maven in expressing
transitive dependencies, the other main reason for staying with
Ivy+Ant was due to 'customizability'. Modifying Maven to do what you
want, e.g. via special plugins, is nasty, especially when Maven
upgrades cause your plugins to fail. Allan can speak more about this,
as it has particularly plagued him at work.
I personally can't stand the suggested maven directory structure. If
you have more than one or two modules, the traversing of directory
trees in your IDE becomes quickly unbearable. I just don't like it.
The current structure we have in place with Ivy however is a lot more
flexible and we can change it any way we like.
At least that's my .02. And just for clarity's sake, and to quell
Joshua's concerns, we don't use the Ivy-generated pom.xml. We
manually edit it to ensure its correctness.
Cheers,
Les
