Re: 2.0 release

> I feel it has nothing to do in the main tree. At all.

I am inclined to agree with you, but I think it is important enough to 
WM's adoption that it must be a major part of the WM availability.

Most people these days take templating as just a small part of a bigger 
whole, and use templating technologies that already work with their 
application framework.

I really think that very few new people are going to use WM on its own, 
because you have to learn how to setup a WM instance etc, write 
templates out etc.

> | Maybe a general "WM Adapters" subproject could incorporate JSP, Spring,
> | and Struts integration along with any other framework that folks want to
> | support.  We could kick off the subproject in conjunction with the WM
> | 2.0 release.
> 
> This I find interesting, but what about just sticking it into a jar inside
> the WM distro? Like a contrib, but with a purpose?
> 
> Note that you anywhichway can't change package names and such, if
> compatiblity is an issue at all.
> 
> Remeber that WM is pretty much dying, and that someone mentioned that the
> 2.0 probably will be one of the final releases ever. DOn't have too many
> grand plans going along with it. The 2.0 -might- kick off new revived
> interest in the project, but please don't get your hopes and visions up
> too much before this actually happens.

It is exactly the taglib plus Spring view etc that have a chance of 
reviving the project. WM is stable, and doesn't need much added. 
Velocity is a successful project only because it has all these extra 
things that WM does not. (because it was fast-tracked by having lots 
more active developers because of the Apache background).

I think that a single org.webmacro source tree with a build.xml that 
builds core WM without any "views" in it (i.e. what we have now) plus a 
separate ANT target which builds a "webmacro-views" JAR with just the 
views code in it is a good solution.

That way we can (a) pump it out now, (b) shout about new support for JSP 
and Spring in 2.0 release, even if it is experimental, and (c) not 
bother anybody who just wants raw WM.

Take a look at Spring, MX4J et al to see how projects with these 
external dependencies are put out now. Typically they have one main jar 
with everything in, and then a bunch of smaller jars with subsets.

I think it should be sort of the other way around for wm - webmacro.jar 
= webmacro, nothing else. webmacro-views.jar = the new view code. 
webmacro-tools.jar = some top-grade documented context tools.

When the Spring view becomes mature we might be able to get it put out 
in the core Spring distro - they already do this for JSP, Velocity and 
FreeMarker.

Cheers

-- 
Marc Palmer    [email protected]
			
Wangjammers - Java, J2ME and Web Consultants
   ~ http://www.wangjammers.org/



-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005