Re: V2.x not usable next to V1.x
Rolf Lear <[email protected]> Fri, 18 May 2012 14:21:31 -0400
| Newsgroups | gmane.comp.java.jdom.general |
|---|---|
| Message-ID | <[email protected]> |
You never answered any of the 4 questions ;-) A few months ago I was begging for maven-experienced people to 'do it right'.... There was some help putting together a POM, but by far the biggest challenge is getting all the 'protocols' in place to actually deliver projects to maven-central. And that makes things difficult. Especially difficult because there is no easy way to do a 'sand-box' test-like process, and it is not available for 'anyone' to do.... it took me weeks just to understand, submit, and process the 'paperwork'. Then, once you are on, you have *no* second-chances.... get one little-bitsy-teeny thing wrong, and you're screwed. If I do something simple like have a piece of uncommitted code when I build the JDOM Build, then that is unrecoverable.... So, in essence, based on the information available 'back then', I have done everything *right*, and JDOM 2.x is correctly installed in maven. What's not working is the condition where someone wants to use two different versions of JDOM at one time.... Rolf Paul Libbrecht appears to have anticipated this problem On Fri, 18 May 2012 14:06:44 -0400, Brad Cox <[email protected]> wrote: > The maven dox are clear about its adherence to "convention over > configuration", which is the very thing I found compelling after my own > bout of grumbling over its noncompliance with *my* conventions > (src/main/java indeed when src should be enough, sez' I). That said, it > provide way to override almost anything, although that's usually painful > enough that its best avoided. > > Think of it this way. For the problems I work on, JDOM is a very small tree > in a very large forest of jars that must work together. I need it to fit > in to that forest and "just work" without having to think about your > reasons for wanting (or needing) your own set of conventions. Regardless of > its (many) flaws, maven projects generally more or less deliver on that > promise. Outlier conventions create problems for me and I avoid packages > that create problems. > > On Fri, May 18, 2012 at 1:30 PM, Rolf Lear <[email protected]> wrote: > _______________________________________________ To control your jdom-interest membership: http://www.jdom.org/mailman/options/jdom-interest/[email protected]