On Tue, Dec 20, 2011 at 6:55 PM, Jukka Zitting <[email protected]> wrote: > Hi, > > On Wed, Nov 30, 2011 at 8:49 PM, Guillaume Bailleul > <[email protected]> wrote: >> If some of you could read through the source codes and give some idea >> on the methodology it would help. > > One big concern I have are the many dependencies that XmpBox has. > JempBox has none, which makes it much easier for downstream > deployments.
That's right. I checked xmpbox dependencies and : * stax and activation are present for compatibility with java 5, they can be removed for java 6 or java 7 environment. * commons-io is present for only one class : IOUtils. It could be removed with a short refactoing The only real dependency is xstream (plus xmlpull and xpp3). So I have 2 questions : * Is there a way to specify in pom that dependency are mandatory in a java environment and not in an other ? * Is it a good idea to create an IOUtils class in Xmpbox to cut dependency to commons-io ? There are no license problem, the choice is between "duplicate code" and "create a dependency for next to nothing" BR, Guillaume
