However, my experience using CVS is limited in this regard, so perhaps I see ghosts where there are none.
Before I/we take actions I'd like Jim to give some comments. Perhaps we have to postpone the restructuring until after 1.3.
Martijn
Nick Neuberger wrote:
sounds like a plan to me..
Do you think this will affect me making changes to jwebunit code in the JACOBIE branch? I haven't committed anything yet but will be soon. What do you suggest? I could just create a patch file and then apply the patch after your restructure changes.
Nick
-----Original Message----- *From:* Martijn Dashorst [mailto:[EMAIL PROTECTED] *Sent:* Sunday, October 24, 2004 8:14 AM *To:* [EMAIL PROTECTED] *Subject:* [Jwebunit-development] Future jWebUnit project directory layout
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.
*
adhere to the maven proposed/default directory structure described at http://wiki.codehaus.org/maven/DirectoryLayout
*
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
- - - - - -
This e-mail message is intended only for the use of the individual or entity identified in the alias address of this message and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this e-mail message is strictly prohibited. If you have received this e-mail message in error, please notify the sender immediately by reply e-mail and delete this message from your system. Thank you.
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Jwebunit-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jwebunit-development
