NekoHTMLGenerator and Gump

[Upayavira <uv...@upaya.co.uk>]

I have written a simple NekoHTMLGenerator, much like the existing one, 
but based around NekoHTML. This does much less clever stuff compared to 
JTidy, and parses to SAX events instead of via a DOM object, which 
should be much more efficient. I have also been told by one happy user 
of my generator that it fixed a problem where JTidy didn't preseve CDATA 
sections in scripts, or some such.

The NekoHTML jar adds 46k to the distribution, and its licence is ASL1.1 
based.

I'd like to commit it to the HTML block.

I have one question though, which relates to gump.xml. If I am adding a 
new jar, presumably I need to reference NekoHTML as a project. In which 
case, presumably the NekoHTML needs to be defined somewhere else?

Or should I just not mention NekoHTML in gump.xml?

Regards, Upayavira

Re: NekoHTMLGenerator and Gump

[Stefano Mazzocchi <st...@apache.org>]

Upayavira wrote:

> I have written a simple NekoHTMLGenerator, much like the existing one, 
> but based around NekoHTML. This does much less clever stuff compared to 
> JTidy, and parses to SAX events instead of via a DOM object, which 
> should be much more efficient. I have also been told by one happy user 
> of my generator that it fixed a problem where JTidy didn't preseve CDATA 
> sections in scripts, or some such.
> 
> The NekoHTML jar adds 46k to the distribution, and its licence is ASL1.1 
> based.
> 
> I'd like to commit it to the HTML block.

+1

> I have one question though, which relates to gump.xml. If I am adding a 
> new jar, presumably I need to reference NekoHTML as a project. In which 
> case, presumably the NekoHTML needs to be defined somewhere else?
> 
> Or should I just not mention NekoHTML in gump.xml?

no, you have to mention the dependency, but you can add the dependency 
as a library (not as a running gump project). see the bottom of gump.xml 
for examples of that (we do that for a number of libraries already).

-- 
Stefano.