Hi,
Mark, Kristian and I have made some good progress on the Maven Shared
Utils.
The project has now 2 compile-scoped dependencies: commons-io-2.2 (final
1.5 compatible version) and jsr305-2.0.1 (for the support of @Nonnull and
@Nullable)
Since we still think that Maven Shared Utils should not have any
dependencies, the commons-io is shaded.
ReaderFactory and WriterFactory now return a Reader or Writer, the method
decides which implementation is used. Right now that is commons-io
CollectionUtils has been removed, since there is a very small usage of it.
With generics this class has become useless.
ExceptionUtils is nominated to be removed, since almost every Exception in
JDK5 can chain exceptions. For the few left we're looking if it is worth
to keep it here or let does project depend on the original plexus-utils
(different
package, so no class-collision)
The whole org.apache.maven.shared.utils.xml package is nominated to be
removed as well, since all its classes are deprecated.
We're making heavy usage of generics, varArgs and other JDK5 specific
features.
My opinion is that we need to remove all deprecated code, solve all TODO
comments before its first release.(the number of todo's is very small,6 in
main and 1 in test, and have either to do with method signatures or with
<=jdk1.4 issues.)
The reason is simple: with a new package this is the best moment to get
rid of some legacy code from the old plexus-utils which had to stay
backwards compatible.
If you think there are other classes/methods which need to be discussed,
please let us know.
thanks,
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
