----- Original Message ----- > From: "Karl Heinz Marbaise" <[email protected]> > To: [email protected] > Sent: Tuesday, November 13, 2012 10:23:35 AM > Subject: plexus-utils / maven-shared-utils / commons-io > > Hi, > > i have a question concerning the plexus-utils/maven-shared-utils. > During the investigation of a bug in appassembler-plugin > (http://jira.codehaus.org/browse/MAPPASM-187). I have seen that in > plexus-utils (3.0.7) the method FileUtils.copyDirectory() seemed to > be not working. The same as in maven-shared-utils. After checking > maven-shared-utils (0.1) i have detected that the unit tests which > are checking the copyDirectory part a currently set to @Ignore. > > I have found a solution in using commons-io package (2.4) but this > would result in a JDK 1.5+ dependency (Does someone know a version > of commons-io which works with JDK 1.4+? . The other question is why > we don't use commons-io directly (apart of the optional dependency > in maven-shared-utils) instead of rewriting things in > maven-shared-utils or did i misunderstand the intention of > maven-shared-utils?
Isn't it really time to give up on 1.4 ? With 1.6 being EOLed recently jumping on 1.5 seems resonable enough to me. This would open the door for using many things provided by the VM instead of relying on some third party libs and even reduce the "downloads the internet" problem. Reducing the dependencies makes things a lot easier for a number of reasons like: - less legal audit and easier approval - yes, many organizations require audit of every single version referenced (not project). E.g. at Eclipse foundation if your build tool uses 3 maven plugins and they use 3 different plexus-utils versions - all 3 has to be reviewed. - easier to build - if there is a source only builds policy using old libraries complicates things by: * old libs not buildable with newer JVM and need heavy patching for this to happen * build cycles - the lib needs maven to build by maven needs the lib in order to be build I know this might not sound too compelling reasons to many but it's huge time consuming effort which prevents many from doing other improvements to the Java stack (incl. Maven + plugins). Alexander Kurtakov Red Hat Eclipse team > > Are there any particular reasons not to to use commons-io package > directly (as a dependency for a plugin)? > > Can someone enlighten me a little bit? > > Thanks in advance. > > Kind regards > Karl-Heinz Marbaise > -- > SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893 > Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029 > Hauptstrasse 177 USt.IdNr: DE191347579 > 52146 Würselen http://www.soebes.de > > > > -- > -- > SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893 > Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029 > Hauptstrasse 177 USt.IdNr: DE191347579 > 52146 Würselen http://www.soebes.de > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
