I just finished a massive license audit for some internal things. It
is an enormous pain. GPL is incompatible with ASL because of the
redistribution portions of the licenses. ASL lets you redistribute
without any restrictions. This allows commercial software to ship ASL
Jar files inside the software. GPL doesn't allow this unless it has an
exception. GPL states that if you want to redistribute a piece of GPL
software, it can only be redistributed inside another GPL piece of
software.
This means that if you ship Struts with anything GPL inside it, it
auto-magically becomes GPL and then no one developing a commercial
software product would use Struts anymore. In most cases with Java,
GPL should be avoided like the plague. I personally think this is one
of the reasons people are switching to Postgres from MySQL (among
other reasons as well).
-bp
On Oct 14, 2009, at 9:52 AM, Martin Cooper wrote:
On Wed, Oct 14, 2009 at 3:07 AM, Alex Siman
<aleksandr.si...@gmail.com> wrote:
What is the problem with that GPL?
From http://www.apache.org/licenses/GPL-compatibility.html
"GPLv3 software cannot be included in Apache projects. The licenses
are incompatible in one direction only, and it is a result of ASF's
licensing philosophy and the GPLv3 authors' interpretation of
copyright law."
--
Martin Cooper
Maybe we can ask the j18n author to add
Apache kind license?
BTW I used to think that "open source is really open". I am bored
w/ all
those licenses. IMHO it's like native2ascii to me.
Philip Luppens wrote:
On Wed, Oct 14, 2009 at 11:09 AM, Alex Siman <aleksandr.si...@gmail.com
>
wrote:
I hacked class [com.opensymphony.xwork2.util.LocalizedTextUtil]
and now
it
uses [http://sourceforge.net/projects/j18n/] to load resource
bundles.
J18n
allows *.properties files to be in UTF-8 encoding and contain not
escaped
UTF-8 characters. This is very usable in comparison with Java's
native2ascii. native2ascii is a very big mess!
I fully agree - the native2ascii approach is a mess and even with
IntelliJ's transparent support, I still find myself encountering
issues. I never understood why the XML properties are read by
default
in UTF-8 and the line based properties use latin-1. But I
digress ...
All that needs to be replaced in LocalizedTextUtils is:
ResourceBundle.getBundle -> J18n.getBundle
I know that there were some plans on UTF-8 in XWork, but I do not
how the
current status of them.
Contacting issues aside, the problem here is the GPL license.
Cheers,
Phil
--
View this message in context:
http://www.nabble.com/XWork%3A-Real-UTF-8-in-*.properties-tp25887706p25887706.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
--
"We cannot change the cards we are dealt, just how we play the
hand."
- Randy Pausch
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
--
View this message in context:
http://www.nabble.com/XWork%3A-Real-UTF-8-in-*.properties-tp25887706p25888384.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org