So what?

Let me summarize: we have some jars that aren't legal to be included in the
same pack with a LGPL license. Sun could say something at the respect. But
they haven't so far. I suppose they are waiting, because, to be fair, JBoss
is miles away from the J2EE server they include in their SDK. I suppose they
are not going to try to kill the only app server that can spread the Java
alternative to .NET in a cost effective way.

I suppose that JBoss makes a lot of good for Sun, spreading the J2EE
standard in the market, and giving an option that can compete with the
commercial app servers where money *is* an issue. So I suppose Sun isn't
going to try to stop this.

As far as I see there are four options:
(a) Sun flexibilizes the license of their code, allowing it to be included
in other packages or giving concrete permission for this OS project.
Something that has already been said in the mailing list to be less than
probable.
(b) Reinvent the wheel and reimplement the offending code.
(c) Not to include those jars in the standard JBoss code, and including a
README with instructions about how to download and where to place them.
(d) Change the License Agreement of JBoss to include this fact. Something
that shouldn't be a good idea, because LGPL is already a proved and
well-known license.

This is where I say that IANAL :) but I don't see this as a problem without
solution anyway.

P.S.: I should say that IMHO Lutris sucks. No flame intention in it, only an
opinion.


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to