Re: Help - falling into 'jar hell' with Mav and JDOM

> Regarding #2, I agree with your code changes. This is exactly what I=20=

> originally had (honest!) but missed the trick with child elements and=20=

> was trying to avoid the potentially unnecessary List creation.

I agree on the List creation, however I don't see a way around it given=20=

the API changes.

> Mike, have you had the chance to test #3 against some of the more=20
> esoteric uses of the mav xml file? My personal usage is fairly=20
> straightforward, so if other users could give some feedback on this to=20=

> ensure we don't break anything...

#3 only effects the use of the maverick config command (command used to=20=

display the mav.xml file; used during development). I see no problems=20
with your code change.

> Obviously, if all is well, I vote for these changes in a new release.

I will let the list know once a release is available.

-- Mike


  :=A0 mike moulton
  :=A0 meltmedia
  :=A0 1429 north 1st street
  :=A0 phoenix=A0 az=A0 85004
  :
  :=A0 [email protected]
  :=A0 mmoulton66    | aim
  :=A0 602.340.9440 | ofc
  :=A0 602.432.2568 | cel
  :=A0 602.340.1003 | fax
  :
  :=A0 meltmedia.com



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
[INVALID FOOTER]