Re: [Webwork-devel] Relase refactor - need input

[Bill B. <bi...@pr...>]

Hello,

Kjetil Paulsen wrote:
> 
> Hi
> 
> Questions:
> 
> * Strictly speaking, Velocity and Xslt support, are addons to the WW core - IMO. Anyone?
> * Should this be moved? (to f.ex src/addon lib/addon)
>   - this would make container compliance even easier

If I understand you correctly, I don't think it's necessary (see below).

> Someone said something about out of date Velocity, the -dep-1.2-rc3.jar is in CVS and I guess there are a 1.2 release out there.
> * Is there a reason NOT to get the 1.2 release into CVS?

Can't think of one.  I've been using the -dep-1.2 against the current WW
CVS recently without issues.

> * Should we use the -dep- file or not
>   - if not we have to include commons from jakarta (I guess ?)
>      - THIS should at least not be part of the core!

The -dep .jar includes Avalon LogKit which Velocity will use by default. 
By using the velocity.jar + commons .jar, it might require configuring
Velocity to use Log4J.  This should be done anyway but probably not for
1.0.  This is explained in the WHY_TWO_JARS.txt file in the dist root. 
I'll try and test this later today.

> * The documentation states that the later is the way to go - we should be consistent

Agreed.  Actually, the documentation should state that either approach is
valid.

> This would make 3 builds
> - core

No Velocity or XSLT support included.
Maybe web.xml does not include Velocity or XSLT support?

> - core-with-addon
> - examples-with-addon

Velocity and XSLT support in lib just as now.
web.xml is the same as now.

Also, I think the examples-with-addon build should also include the
current Log4J .jar so you can deploy the .war and use it without any other
downloads.  This makes for a much better user experience for anyone
investigating WW ... just deploy and run.

-Bill