Hi, For your information, commons-io is also used by the preflight module. However like for the xmpbox, only IOUtils is used. (closeQuietly, copy and copyLarge).
On second thought, I'm not sure if it is really useful to import a 5 Mb dependency for only one class. Regards, Eric -----Message d'origine----- De : Guillaume Bailleul [mailto:[email protected]] Envoyé : mercredi 28 décembre 2011 06:16 À : [email protected] Objet : Re: Merging jempbox and xmpbox 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 Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité d'Atos ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
