Re: V2.x not usable next to V1.x

+1 to both paragraphs!

On Fri, May 18, 2012 at 4:13 PM, Michael Kay <[email protected]> wrote:

> >All in all, I think it is fair to blame maven here.
>
> I have a great deal of sympathy with both sides of this debate.
>
> Maven is a pig to use. We've given up trying several times. The
> documentation is awful, the process is awful, there is no way of testing
> your artefacts, and when you get them wrong (as we have done) there is no
> way of putting it right.
>
> On the other hand, Maven is quite rightly focused on meeting the needs of
> its users rather than package developers. Those users do have complex
> requirements, and individual components like JDOM or Saxon are tiny parts
> of their overall systems; they don't want to tailor their working methods
> to the idiosyncracies of individual packages. (And they certainly don't
> want to have upgrades foisted on them: when something isn't broken, they
> don't want to fix it). So as developers, I think it's reasonable that we
> should make some effort to fit into the process the way it has been
> designed. But it *is* an extremely frustrating experience, and I'm not
> convinced it needs to be.
>
> Michael Kay
> Saxonica
>
> ______________________________**_________________
> To control your jdom-interest membership:
> http://www.jdom.org/mailman/**options/jdom-interest/**
> [email protected]<http://www.jdom.org/mailman/options/jdom-interest/[email protected]>
>



-- 
Cell: 703-594-1883
Blog: http://bradjcox.blogspot.com
Web: http://virtualschool.edu
Manassas VA 20111

_______________________________________________
To control your jdom-interest membership:
http://www.jdom.org/mailman/options/jdom-interest/[email protected]