Hi,

Since the inception of jWebUnit, the project has grown and many directories have evolved under the jWebUnit CVS module. I think it is now time to make a clean cut for the project in order to keep it organized and maintainable. For people reading this message without HTML support, I apologize, but I couldn't find a better way to use the tables for the directory layout.

If there are no objections, I want us to implement this proposal in the next few weeks. I think I'll need some help from Jim for doing this in a wise and consistent manner.

Here's what I propose:

  • separate jwebunit - fit plug in from the jwebunit core into a project/CVS module of its own

  • make maven the main build tool for jwebunit. Ant script will be provided/maintained for people to create their own build.

  • use solely XDOC type documentation to maintain the documentation of the project and generate the website from the XDOCs and maven plug ins

This will result in the following CVS tree:

Module

Description

/CVSROOT

CVS admin directory

/jWebUnit

Jwebunit main project

/jwebunit-fit

Fit-project

/site

deprecated, to be removed by sourceforge.net administrators

Other projects, for instance the jwebunit-maven plugin, will get their own module in cvs next to the existing modules.

jWebUnit directory structure (in the CVS module):

Directory/file

Description

project.xml

maven project object model

maven.xml

maven build file

project.properties

customizations for maven builds

build.xml

ant build file for building jwebunit with ant

LICENSE.txt

the jWebUnit license

license-checkstyle.txt

checkstyle file for checking the headers of each java file

licenses/

licenses for supplied libraries

lib/

lib directory for supplied libraries

src/

source directory containing all source files

src/main

source directory containing all jwebunit framework sources

src/main/java

all java source files for jwebunit

src/test

source directory containing all jwebunit test source files.

src/test/java

all java testcases

src/test/webapp

the webapplication directory for testcases (using jetty)

src/test/resources

resources for testing purposes (jetty config, etc)

xdocs

documentation directory


Reply via email to