You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Rainer Hermanns <he...@aixcept.de> on 2006/03/25 09:37:48 UTC

WebWork and LGPL dependencies

Some of the LGPL dependencies were already moved out of the main  
build process.
As far as I could see the hibernate dep can completely be removed,  
cause there is no hibernate
specific code in the codebase, just within the wikidocs.

Next I just walked through the UI components of webworks tag library.
There are some components with LGPL code, that need to be replaced or  
separated:

* JSCalendar for the DatePicker tag
* FCKEditor for the Richtexteditor tag
* Walter Zorns tooltip library for all UI Tags
* tabbedpane.vm Archived UI template

How should those be "refactored"? Is there a guideline available for  
removing the "bad" deps?

tia,
Rainer

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: WebWork and LGPL dependencies

Posted by Don Brown <mr...@twdata.org>.
We don't need to replace the Java code that depends on LGPL deps, as long as we:
  1. Don't download the LGPL dep jars in the normal build
  2. Don't ship the LGPL jars in our release

Therefore, I've split the build so that the classes that depend on LGPL jars won't be compiled in the standard build. 
You have to execute 'compile-optional' to pull down those LGPL jars and compile the related code.

The question is how this applies to unit tests.  If you interpret "default build" to be the one that runs when you just 
type "ant", then typing 'ant test' could pull down LGPL jars, compile the code and its unit tests without problems.  I'm 
pulling for this interpretation :)

Don

Rainer Hermanns wrote:
> Ted,
> thanks for clearifying this...
> Just removed the hibernate dep from ivy/pom. Hibernate was not used
> within the codebase, only in the docs.
> Do the docs need to be cleared as well from those deps (just the written
> docs, not code samples)?
> 
> Has anyone yet talked to the JasperReports guy?
> This would be a dependency really hard to replace...
> 
> cheers,
> Rainer
> 
>> On 3/25/06, Rainer Hermanns <he...@aixcept.de> wrote:
>>> How should those be "refactored"? Is there a guideline available for
>>> removing the "bad" deps?
>> First, we should contact the authors and make sure they do want to put
>> the code under the LGPL. Sometimes people use that as a default and
>> don't actually care.
>>
>> If the author does care, then we have to find or create comparable
>> technology under a license that we can bundle with the Apache License,
>> without trespassing on anyone's IP.
>>
>> -Ted.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: WebWork and LGPL dependencies

Posted by Alexandru Popescu <th...@gmail.com>.
Great! I will ping Theodor to take a look at the current thread and I will
have a chat with him. However, IMO, JasperSoft should be contacted too.

BR,

./alex
--
.w( the_mindstorm )p.


On 3/28/06, Martin Cooper <ma...@apache.org> wrote:
>
> On 3/27/06, Alexandru Popescu <th...@gmail.com> wrote:
> >
> > I know Theodor, he is a good friend of mine. Though, I think this
> > decission
> > is more now on JaspectSoft than on Theodor. I will try to ping him and
> ask
> > about this. Are these threads available directly from the web, so that I
> > can
> > point him to this discussion?
>
>
> Yes, they are. There are several mailing list archive sites, and you can
> also see mail to this list on gmane or nabble. For example:
>
> http://thread.gmane.org/gmane.comp.jakarta.struts.devel/37916
>
> --
> Martin Cooper
>
>
> cheers,
> >
> > ./alex
> > --
> > .w( the_mindstorm )p.
> >
> >
> > On 3/28/06, Ted Husted <te...@gmail.com> wrote:
> > >
> > > I'm sure that we would want to talk to JasperSoft first, Martin.
> > >
> > > -Ted.
> > >
> > > On 3/27/06, Martin Cooper <ma...@apache.org> wrote:
> > > > If we want to do that, I'm willing to talk to them. I know the CTO
> of
> > > > JasperSoft and some other people there, although not the
> JasperReports
> > > guy
> > > > specifically. Let me know.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > > For additional commands, e-mail: dev-help@struts.apache.org
> > >
> > >
> >
> >
>
>

Re: WebWork and LGPL dependencies

Posted by Martin Cooper <ma...@apache.org>.
On 3/27/06, Alexandru Popescu <th...@gmail.com> wrote:
>
> I know Theodor, he is a good friend of mine. Though, I think this
> decission
> is more now on JaspectSoft than on Theodor. I will try to ping him and ask
> about this. Are these threads available directly from the web, so that I
> can
> point him to this discussion?


Yes, they are. There are several mailing list archive sites, and you can
also see mail to this list on gmane or nabble. For example:

http://thread.gmane.org/gmane.comp.jakarta.struts.devel/37916

--
Martin Cooper


cheers,
>
> ./alex
> --
> .w( the_mindstorm )p.
>
>
> On 3/28/06, Ted Husted <te...@gmail.com> wrote:
> >
> > I'm sure that we would want to talk to JasperSoft first, Martin.
> >
> > -Ted.
> >
> > On 3/27/06, Martin Cooper <ma...@apache.org> wrote:
> > > If we want to do that, I'm willing to talk to them. I know the CTO of
> > > JasperSoft and some other people there, although not the JasperReports
> > guy
> > > specifically. Let me know.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>

Re: WebWork and LGPL dependencies

Posted by Alexandru Popescu <th...@gmail.com>.
I know Theodor, he is a good friend of mine. Though, I think this decission
is more now on JaspectSoft than on Theodor. I will try to ping him and ask
about this. Are these threads available directly from the web, so that I can
point him to this discussion?

cheers,

./alex
--
.w( the_mindstorm )p.


On 3/28/06, Ted Husted <te...@gmail.com> wrote:
>
> I'm sure that we would want to talk to JasperSoft first, Martin.
>
> -Ted.
>
> On 3/27/06, Martin Cooper <ma...@apache.org> wrote:
> > If we want to do that, I'm willing to talk to them. I know the CTO of
> > JasperSoft and some other people there, although not the JasperReports
> guy
> > specifically. Let me know.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

Re: WebWork and LGPL dependencies

Posted by Ted Husted <te...@gmail.com>.
I'm sure that we would want to talk to JasperSoft first, Martin.

-Ted.

On 3/27/06, Martin Cooper <ma...@apache.org> wrote:
> If we want to do that, I'm willing to talk to them. I know the CTO of
> JasperSoft and some other people there, although not the JasperReports guy
> specifically. Let me know.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: WebWork and LGPL dependencies

Posted by Martin Cooper <ma...@apache.org>.
On 3/27/06, Rainer Hermanns <he...@aixcept.de> wrote:
>
> Ted,
> thanks for clearifying this...
> Just removed the hibernate dep from ivy/pom. Hibernate was not used
> within the codebase, only in the docs.
> Do the docs need to be cleared as well from those deps (just the written
> docs, not code samples)?
>
> Has anyone yet talked to the JasperReports guy?


If we want to do that, I'm willing to talk to them. I know the CTO of
JasperSoft and some other people there, although not the JasperReports guy
specifically. Let me know.

--
Martin Cooper


This would be a dependency really hard to replace...
>
> cheers,
> Rainer
>
> > On 3/25/06, Rainer Hermanns <he...@aixcept.de> wrote:
> >> How should those be "refactored"? Is there a guideline available for
> >> removing the "bad" deps?
> >
> > First, we should contact the authors and make sure they do want to put
> > the code under the LGPL. Sometimes people use that as a default and
> > don't actually care.
> >
> > If the author does care, then we have to find or create comparable
> > technology under a license that we can bundle with the Apache License,
> > without trespassing on anyone's IP.
> >
> > -Ted.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

Re: WebWork and LGPL dependencies

Posted by "Frank W. Zammetti" <fz...@omnytex.com>.
Indeed I do :)

And actually, some interesting things are happening there... Jim Menard, 
the creator of DataVision, is stepping away from it for lack of time. 
He has asked for volunteers to kind of take over (I offered to, as part 
of a team effort).  I wonder if he might be amenable to donating it to 
Apache outright?  That would not only serve the DataVision community, 
but would help here, and AFAIK would be the only report writer at Apache 
(I'm sure I'm missing a project somewhere!)

I'd probably have to say it isn't quite at the level of polish of 
JasperReports, but it *is* quite good.

Anyone should feel perfectly free to ping me for any reason if there is 
interest in going that route.  I'll help however I can.

Frank

Ted Husted wrote:
> On 3/27/06, Rainer Hermanns <he...@aixcept.de> wrote:
>> Has anyone yet talked to the JasperReports guy?
>> This would be a dependency really hard to replace...
> 
> One alternative might be DataVision.
> 
> * http://datavision.sourceforge.net/
> 
> Our friend Frank Zammetti  knows a little bit about it :)
> 
> -Ted.
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: WebWork and LGPL dependencies

Posted by Ted Husted <te...@gmail.com>.
On 3/27/06, Rainer Hermanns <he...@aixcept.de> wrote:
> Has anyone yet talked to the JasperReports guy?
> This would be a dependency really hard to replace...

One alternative might be DataVision.

* http://datavision.sourceforge.net/

Our friend Frank Zammetti  knows a little bit about it :)

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: WebWork and LGPL dependencies

Posted by Ted Husted <te...@gmail.com>.
On 3/27/06, Rainer Hermanns <he...@aixcept.de> wrote:
> Ted,
> thanks for clearifying this...
> Just removed the hibernate dep from ivy/pom. Hibernate was not used
> within the codebase, only in the docs.

Great!

> Do the docs need to be cleared as well from those deps (just the written
> docs, not code samples)?

If you mean mentioning the dependency in the documentation, no. It's
something we would have to do before a release. But it's not something
we need to do to clear the incubator.

We can *use* LGPL software to do our own work. The problem is we can't
*distribute* LGPL software, because the terms conflict with the more
liberal Apache License.

-Ted.

> Has anyone yet talked to the JasperReports guy?
> This would be a dependency really hard to replace...

This isn't our favorite option, but that could also be something that
was offered as an extension through SourceForge or Open Symphony. It
would not be maintained by the Apache Struts Project, though the same
indivduals might be involved.

Sometimes, it's also possible to provide a bridge API that would let
people use an extension like JasperReports if they downloaded the JAR
themselves. The bridge API would let us compile our code without
having the actual LPGL jar available. Again, this not something we
like to do, but it can be done if necessary.

I'll add JasperReports to the list.

-Ted.


>
> cheers,
> Rainer
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: WebWork and LGPL dependencies

Posted by Rainer Hermanns <he...@aixcept.de>.
Ted,
thanks for clearifying this...
Just removed the hibernate dep from ivy/pom. Hibernate was not used
within the codebase, only in the docs.
Do the docs need to be cleared as well from those deps (just the written
docs, not code samples)?

Has anyone yet talked to the JasperReports guy?
This would be a dependency really hard to replace...

cheers,
Rainer

> On 3/25/06, Rainer Hermanns <he...@aixcept.de> wrote:
>> How should those be "refactored"? Is there a guideline available for
>> removing the "bad" deps?
>
> First, we should contact the authors and make sure they do want to put
> the code under the LGPL. Sometimes people use that as a default and
> don't actually care.
>
> If the author does care, then we have to find or create comparable
> technology under a license that we can bundle with the Apache License,
> without trespassing on anyone's IP.
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: WebWork and LGPL dependencies

Posted by Ted Husted <te...@gmail.com>.
On 3/25/06, Rainer Hermanns <he...@aixcept.de> wrote:
> How should those be "refactored"? Is there a guideline available for
> removing the "bad" deps?

First, we should contact the authors and make sure they do want to put
the code under the LGPL. Sometimes people use that as a default and
don't actually care.

If the author does care, then we have to find or create comparable
technology under a license that we can bundle with the Apache License,
without trespassing on anyone's IP.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Re: WebWork and LGPL dependencies

Posted by Martin Cooper <ma...@apache.org>.
On 3/25/06, Rainer Hermanns <he...@aixcept.de> wrote:
>
> Some of the LGPL dependencies were already moved out of the main
> build process.
> As far as I could see the hibernate dep can completely be removed,
> cause there is no hibernate
> specific code in the codebase, just within the wikidocs.
>
> Next I just walked through the UI components of webworks tag library.
> There are some components with LGPL code, that need to be replaced or
> separated:
>
> * JSCalendar for the DatePicker tag
> * FCKEditor for the Richtexteditor tag
> * Walter Zorns tooltip library for all UI Tags
> * tabbedpane.vm Archived UI template
>
> How should those be "refactored"? Is there a guideline available for
> removing the "bad" deps?


As Ted mentioned, we could ask the authors of the LGPL code if they'd be
prepared to switch or dual-license.

Other than that, I believe equivalent components exist for the first two in
Dojo (although I don't know whether the functionality is the same). If the
tooltip library is a JavaScript one, then that exists in Dojo as well. Dojo
also has tabbed panes, but the one you mention sounds like it's a
server-side component.

If we want to continue to provide the existing components, then we need to
make them optional, not bundle them, and not have explicit ties to them.

--
Martin Cooper


tia,
> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>