Vincent Massol wrote:
> Yes, I understand that but my point is only to make it easy for person who
> download struts and want to try it. I'm always trying to make the software I
> write as much "plug and play" (or should I say "download and run") as
> possible. But this does not preclude power users to use other versions of
> these libraries.
Hugely +1 here.
Tire-kickers welcome!
> Then you can have 2 build files, one to build stuts with Servlet API 2.2 and
> one for Servlet API 2.3. You'll need that someday, when you'll have to
> support both API and you'll have some code specific to 2.2 and other
> specific to 2.3
Just to brainstorm -- Resin (I think) did a neat thing during the 1.1
transition. There was a preprocessor that would scan the code and switch
it back and forth between 1.1 and 1.2.
> Yes, I agree but everything in jakarta-struts is part of the source, right ?
> I don't really care either. Only that (example, share, test, unit) really
> seem to go together because they are code whereas conf/, doc/ are other
> subjects. Here is my preferred structure (updated) :
After unpacking the applications that come with Struts, the first thing
I find myself doing is copying the source from src/$application to
$application/WEB-INF/src. This way the source for the classes is near
the source for the JSPs.
If the source for the Web applications travelled with the webapp JARs,
people could download just the applications, try those on for size, and
take a peek at the source code. This leads to a staged introduction to
Struts where people can
(1) Download and install the Struts documentation and example
applications,
(2) Then download the binary distribution to try compiling your own
Struts application,
(3) And/or, download the full source distribution, to build Struts from
scratch.
Some people may stop at (2), others may skip directly to (3).
Of course, with Ant I guess we could keep the Web app source where it
is, and then just copy it over when the Web applications were built as
deliverables.
<
http://www.mail-archive.com/struts-dev%40jakarta.apache.org/msg00320.html
>
The other thing to think about is the idea of Struts "template"
applications, that people could download use as the base for their own
work. Here, we would want a common approach to storing the source with
the application so that these would be easy to download and use.
-Ted.
