incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pedro Giffuni <...@apache.org>
Subject Re: Report Builder extension (was Re: [proposal] development for the first AOO release)
Date Fri, 11 Nov 2011 16:34:38 GMT
Hi Oliver;

It's OK. The priority is clearly to get the IP
clearance done; I was just trying to set out
some plan to preserve the functionality much
easier for end users but this surely can wait.

Thanks for your hard work,

Pedro.

--- On Fri, 11/11/11, Oliver-Rainer Wittmann wrote:
...
> Hi,
> 
> sorry for the late response - I was busy with some other
> stuff.
> 
> Yes, I agree - the configure options are too much.
> I did not invest the time to clean it up - I was just using
> and adapting what already exists.
> 
> The intrinsic output of the build of module reportbuilder
> is an extension for Apache OOo. I kept the build of it with
> the corresponding jars available in the system for everybody
> who wants to bundle it with Apache OOo and/or who wants to
> adjust/enhance/correct it.
> Such an extension is of high value for a certain part of
> our users, but it is an optional functionality. Thus, I think
> it was decided to implement this functionality as an extension.
> 
> My main focus here was to make this part of our code IP
> clear.
> If further interest and resources are available in the
> future this 
> project will evolve. But currently that was not my focus.
> 
> Best regards, Oliver.
> 
> On 09.11.2011 17:19, Pedro Giffuni wrote:
> > Hi Oliver;
> >
> > I won't ask you to revert this but I think it's a
> complete
> > waste of time.
> >
> > Those tarballs don't really have a home so it's
> > improbable that someone will get them into their
> > build, plus it's too many flags to get that building.
> >
> > My attempt to contact Pentaho concerning this
> extension
> > produced no result. I consider this extension
> orphaned
> > and I think it should be moved elsewhere out.
> >
> > Pedro.
> >
> > (Yes, I woke up on the left side of the bed
> >   today ;-) ).
> >
> > --- On Wed, 11/9/11, Oliver-Rainer Wittmann wrote:
> > ...
> >>
> >> I have finished the improvement - or better the
> >> correction.
> >> Now, it should be possible to build the Report
> Builder
> >> extension with
> >> jars available in the system.
> >> To do so, the following (already existing)
> configure
> >> options have to be
> >> used:
> >> --enable-report-builder
> >> --with-sac-jar=JARFILE
> >> --with-libxml-jar=JARFILE
> >> --with-flute-jar=JARFILE
> >> --with-jfreereport-jar=JARFILE
> >> --with-liblayout-jar=JARFILE
> >> --with-libloader-jar=JARFILE
> >> --with-libloader-jar=JARFILE
> >> --with-libformula-jar=JARFILE
> >> --with-librepository-jar=JARFILE
> >> --with-libfonts-jar=JARFILE
> >> --with-libserializer-jar=JARFILE
> >> --with-libbase-jar=JARFILE
> >>
> >> I have reactivated environment variable
> SYSTEM_JFREEREPORT.
> >> It can not
> >> be used via a configure option, but is by default
> set to
> >> "YES", if
> >> configure option --enable-report-builder is used.
> >>
> >> Thanks again for reporting the defect in my
> contribution.
> >> Again, feedback is welcome.
> >>
> >> Best regards, Oliver.
> >>
> 

Mime
View raw message