Hi Again, After sending I thought I would read through my comments again... I think I need to clarify here.
On Thu, Mar 8, 2012 at 10:29 AM, Lewis John Mcgibbney < [email protected]> wrote: > I simply don't know enough about it. There was (and is) a rather > interesting thread going on elsewhere just now regarding namespaces... > maybe we could rename packages to our own namespace and ship with them > until we can refactor these libraries out for the next incubating release, > or alternatively wait until they are available elsewhere e.g. > respotitory.apache.org or maven central repos? > >> >> By 'renaming the packages' I refer solely to ASLv2.0 licensed e.g. >From Any23googlecode repos - org.apache.commons.commons-csv rename to org.apache.any23.commons.commons-csv -net.xeoh.jspf appears to be BSD licensed so we obviously can't muck around with namespaces and pacxkages here. Apache James seems to have some kind of jspf implementation though. [1] I've just noticed halfway though writing this email that we actually maintain our own svn repo-ext with both of the above libraries included. Can we not simply change the dependency resolution to point to this repos? [1] http://search.maven.org/#search|ga|1|jspf
