I'm definately +1 on a core Strut JAR. I'm alo +1 on a struts-template.jar. We might consider moving this to contrib, since many people are migrating to Tiles. I could help with that if it matters, or just update the documentation when we are through.
I'm +0 on either putting the others (bean, html, logic) into a struts-taglibs.jar, since in practice it's unusual to use one without at least one of the other two, and this cuts down on the number of jars we need to talk about :) Taken together, they do form a kind of component unto themselves. I'm also +0 on having separate struts-bean.jar, struts-html.jar, and struts-logic.jar, since (1) this is how Taglibs does it and (2) there is then a 1:1 correlation between the jar and tld. You end up with a lot of JARs in the lib, but then this is Java, and that's the Java way. So on the latter two, I'm good with either case. -Ted. Martin Cooper wrote: > > I know I'm coming in a month late on this, but the holidays are over and now > I'm paying attention again... ;-) > > I guess I missed the original thread suggesting the breakup of the Struts > jar file into core and taglibs. I can see the rationale for splitting the > taglibs out from the core framework. However, I'm not so sure that all the > taglibs should be split out as a single entity. It seems to me that it would > make more sense to split out each taglib as its own self-contained entity, > in the manner of Jakarta Taglibs. > > I'm planning on making some other changes to the Struts build process in the > near future, and I could certainly roll these in if people think it would be > desirable. > > What do people think? > > -- > Martin Cooper -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
