Hey Helder

On 12.02.2011 16:32:23 Helder Magalhães wrote:
> Hi Jeremias and everyone,
> 
> Sorry for the delay in answering, I did notice your
> build-simplification branch creation but was too overflow to keep
> up...

No apologies required.

> 
> > Working towards preparing the color branch for a merge into trunk I
> > noticed how much code duplication there is in the Ant build and how many
> > hard-coded JAR names are in manifest Class-Path entries or security
> > policy files.
> 
> I got a few minor fixes for the builld.xml file. Should I commit them
> to the trunk?

Absolutely. Don't feel blocked by anything I announced to do but still
haven't done. ;-)

> 
> > Batik currently has an Ant 1.6.5 in lib\build. I would suggest that this
> > be removed in favor of an Ant installed on the developer's machine. We
> > don't have any negative experience on this in FOP that I can remember.
> > I'm always building with my local Ant installation rather than the
> > build.bat from Batik anyway.
> 
> I guess it's fair to assume a developer to install Ant. In the
> meantime, I was preparing an upgrade Ant to 1.7.1 (I memory doesn't
> fail, it's the latest version compatible with Java 1.4 but I need to
> double check this).
> 
> In the meantime, I do like the convenience of a build script. Unless
> the Ant-equivalent commands are easy enough to memorize, of course.
> ;-)
> 
> 
> > And the crimson.jar in lib\build is by now
> > an ancient relic. ;-)
> 
> This is where one needs to have some care. I'm also preparing a few
> fixes for the build scripts of "contrib/rasterizertask" which were
> broken for a similar reason (a Java parser unavailable and reference
> to crimson was broken).
> 
> 
> > If any of you have any thoughts on the above, I'd love to hear them.
> 
> What do you think? Should I commit my stuff to the trunk ASAP (as bugs
> are fixed) and integration will be performed afterward or should I try
> to integrate applicable stuff in the branch already? (I'd vote for the
> first approach!)

I can always merge into the build branch. Just do what you think is
useful.

> 
> > Thanks,
> > Jeremias Maerki
> 
> Thank you very much for all the hard work in getting us rid of those
> broken build nagging messages! :-)

Hold that thought until I've really gotten rid of the com.sun problem.
;-)

> Cheers,
>  Helder
> 
> 
> --
> Helder "Lthere" Magalhães
> http://heldermagalhaes.com/



Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to