Henri Yandell wrote:
Provided you can display a yes/no choice to the user so they have to
manually accept each library; possibly needing to show the licence
also;
I don't think the Maven Ant tasks will do the prompting or license
showing themselves, but I suppose we could have an Ant target that
enables the Maven tasks to do any necessary prompting.
> Bear in mind, we need to do this for both LGPL and BCL dependencies.
The DownloadLGPLDependencies page on the wiki only enumerates LGPL jars.
Is there a more complete list of required/optional jars and their
licenses? What are the essential Sun/BCL dependencies?
Anyway, I can make the time to try to integrate the Maven 2 Ant tasks
this weekend, and I can configure them to download Hibernate from the
ibiblio Maven repository, if this would be helpful.
-- Sean
p.s. Doing a quick glance in my subversion tree I see the following Sun
jars:
./tools/hibernate-3.0/lib/jta.jar
./tools/lib/activation.jar
./tools/lib/mail.jar
The latest versions of all three of these SUN packages have different
license agreements (although the activation and jta jars seem to have
the same basic text except the package name). All of which allow
redistribution under a set of restrictions which include the restriction
"only bundled as part of your Programs". This restriction would seem to
prohibit placing any of these jars in a public Maven repository.
I didn't mean to get off on this legal tangent since IANAL and I'm sure
the Apache incubation process is specifically designed to deal with
these issues.
