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 <[EMAIL PROTECTED]> wrote:
>
> On 3/27/06, Alexandru Popescu <[EMAIL PROTECTED]> wrote
On 3/27/06, Alexandru Popescu <[EMAIL PROTECTED]> 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
>
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.
I'm sure that we would want to talk to JasperSoft first, Martin.
-Ted.
On 3/27/06, Martin Cooper <[EMAIL PROTECTED]> 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 k
On 3/27/06, Rainer Hermanns <[EMAIL PROTECTED]> 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
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
On 3/27/06, Rainer Hermanns <[EMAIL PROTECTED]> 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 :)
-Te
On 3/27/06, Rainer Hermanns <[EMAIL PROTECTED]> 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, n
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 buil
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 woul
On 3/25/06, Rainer Hermanns <[EMAIL PROTECTED]> 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.
On 3/25/06, Rainer Hermanns <[EMAIL PROTECTED]> 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
12 matches
Mail list logo
