Re: [picocontainer-dev] webapp-common jar

Paul Hammant wrote:
> We have some five or so example webapps that demo WebWork or Struts 
> permutations.
> 
> The used to depend on a common jar that contained components common to all.
> 
> The trouble is that newbie experiences mean that a person only has a 
> short period of time to decide whether they like something or not, and 
> having source in one place for a single webapp demo, makes a positive 
> experience about 10x more likely.
> 
> Thus I have copied the handful of classes to each example webapp in 
> turn, even if that means code duplication.

We just need to make sure that there is no duplication of packages, so 
that all examples can co-exist in same IDE classpath.  It can ATM.

> Aside from the 10x experience factor, we could now move subtly in an 
> idiomatically correct direction for each web framework.

On a separate point, why did you check into svn the demo warfiles?

I really don't the idea of checking *any* artifact in svn.

We can upload them to snapshot repo (or even make them versioned 
releases) and then pull them down via dependency plugin when building 
distribution.

Cheers






---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email