Operating System: All
Thanks for considering a release under a license bsides GPLv3, Mark. As you
proposed in your email, LGPL would work just great for my needs.
Here's the reasoning behind the request to release pacProxySelector under the
LGPL v3 license and not the GPLv3 license:
I have authored an Eclipse-based application for internal use at my company. I
wish to include a proxy auto-configuration feature in the application, using the
pacProxySelector code. Although there are currently no plans to distribute the
application outside of the organization, it is possible that we may in future
give the application to certain customers for them to use against our company's
Web services tier.
My company wishes to avoid the burden (which is largely bureaucratic) of
maintaining an accessible source repository for these customers to download the
entire application codebase, as the GPLv3 license would require. Instead, we'd
prefer to use pacProxySelector as a .jar, link it in the application, and abide
by the conditions of LGPL v3: we would not alter the pacProxySelector code; we
would credit the original author; we would include the license documents with
the released object code; we would display copyright notice for original author
at runtime where our own copyright notice is displayed; and we would arrange the
released object code to link to pacProxySelector at runtime so that end users
may substitute a modified version of pacProxySelector at runtime using standard
Java linking practices.
Accepted. Will work on getting a new release out shortly.
Fixed in com.ziesemer.utils.pacProxySelector-2010.09.18.zip .