In term of deliverables to download that would mean : * Jakarta-cactus-framework.zip * Jakarta-cactus-ant.zip * Jakarta-cactus-sample-servlet.zip * Jakarta-cactus-sample-j2ee.zip * Jakarta-cactus-src.zip (the full Jakarta-cactus/ directory)
I'm hesitating over the documentation ... Should we extract it from jakarta-cactus-framework.zip and others and have and additional : * Jakarta-cactus-doc.zip In which case, we would have : * Jakarta-cactus-servlet-22.jar (which will be replaced by Jakarta-cactus-j2ee-12.jar soon) * Jakarta-cactus-servlet-23.jar (which will be replaced by Jakarta-cactus-j2ee-13.jar soon) * Jakarta-cactus-ant.jar * Jakarta-cactus-sample-servlet.zip * Jakarta-cactus-sample-j2ee.zip * Jakarta-cactus-src.zip * Jakarta-cactus-doc.zip (contains HTML doc for framework + ant tasks + all javadocs) ?? What do you think ? Thanks -Vincent P.S. : Of course, all files end with the current Cactus version. Eg.: Jakarta-cactus-servlet-22-1.3.jar > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED]] > Sent: 23 February 2002 22:56 > To: 'Cactus Developers List' > Subject: [proposal] Build reorganisation > > I'd like to perform a build directory structure reorganization as I find > the current one limiting (it actually make it very difficult to > implement some todo items). Here is the new proposal : > > jakarta-cactus > |_ ant > |_ build > |_ build.xml > |_ doc > |_ src > |_ framework > |_ build > |_ build.xml > |_ doc > |_ conf > |_ src > |_ web > |_ sample-servlet > |_ build > |_ build.xml > |_ doc > |_ conf > |_ src > |_ web > |_ sample-j2ee > |_ build > |_ build.xml > |_ doc > |_ conf > |_ src > |_ build.xml > > where : > > Jakarta-cactus/ant : contains the custom Cactus Ant tasks + the Ant > build scripts to start/stop the different containers. The deliverables > from this sub-projects are : > * cactus-ant.jar > * build scripts for starting/stopping the different containers > * documentation of Ant tasks (HTML + javadocs) > > Jakarta-cactus/framework : contains the core Cactus framework + web site > documentation. The deliverables are : > * cactus-xx.jar (where xx is 22 or 23 and depends on the servlet.jar > used) > * web site documentation (HTML) + javadocs > > Jakarta-cactus/sample-servlet : Sample that shows how to write Cactus > tests for the Servlet API (Servlets, Taglibs and Filters). The > deliverables are : > * The sources of a full sample project (full directory structure), > including the needed jars (including the cactus jars). It also contains > the start/stop scripts for the different containers. In other words, it > is a fully working project that is a superset of cactus-jakarta/ant and > cactus-jakarta/framework in term of deliverables. > > Jakarta-cactus/sample-j2ee : Sample that shows how to write Cactus tests > for EJBs (Session Bean to start with). The deliverables are : > * The sources of a full sample project (full directory structure), > including the needed jars (including the cactus jars). It also contains > the start/stop scripts for the different containers. In other words, it > is a fully working project that is a superset of cactus-jakarta/ant and > cactus-jakarta/framework in term of deliverables. (in the future this > may also become a superset of Jakarta-cactus/sample-servlet). > > Jakarta-cactus/build.xml : build it all in one go. > > Do you like it ? Do you see any issues ? I'd like to get started ASAP so > please voice your concern if you have any ! :-) > > Thanks > -Vincent > > > > -- > To unsubscribe, e-mail: <mailto:cactus-dev- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:cactus-dev- > [EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
