Actually, I had bigger things in mind....well, sort of ;)
See intermixed.
----- Original Message ----- From: "Martin Cooper" <[EMAIL PROTECTED]>
To: "Struts Developers List" <dev@struts.apache.org>
Sent: Tuesday, January 11, 2005 12:19 PM
Subject: Re: svn repository
On Tue, 11 Jan 2005 06:35:25 -0500, James Mitchell <[EMAIL PROTECTED]> wrote:Who is going to finish moving the directory structure?
Whoever pitches in? ;-)
Right now, I can't load core as an Eclipse project because some of the example apps rely on tiles, which relies on core. Creating a circular reference as far as project dependencies goes.
It should be easy enough to exclude the examples in your Eclipse project for now.
Yes, but that's actually what I am after.
I remember someone mentioning moving all the apps to an 'apps/trunk' base.
Is that still going to happen?
I had hoped to pull out the examples a couple of weekends ago, but the time didn't materialise as I had expected. It would be easy enough to pull them all out into an 'apps' subproject, but it's not quite as easy to get them all building again.
However, if folks are OK with temporary breakage, I can pull them out tonight and leave them broken until the weekend, when I'll hopefully have time to make them build again. This sort of follows Ted's suggestion, from some time ago, to focus on getting Core into shape first and then clean up behind us after that.
Well, before you do that I have a few more questions....and a plan.
1. Why does commons-chain have a sample application called "mailreader"? This looks to be the same mailreader as the one in Struts.
2. core doesn't compile with "ant dist" or "maven dist" due to half baked file structure changes. Specifically, the sample apps refer to TagUtils, which they can't find. How does the nightly run anyway?
3. What is the status of tiles? I though David Geary was extracting it from core and we would simply provide an integration library.
Also, tiles/trunk seems to be a copy of core/trunk, is this correct? The tiles stuff seem to be under tiles/trunk.old
[The plan (yes, I'm volunteering) ] So, unless someone says something, my plans are as follows: - move all the sample apps to a new "apps" subproject as follows: [-] trunk ' [-] blank ' ' [-] src ' ' [+] java (nothing in here right now) ' ' [+] resources ' ' [+] test ' ' [+] webapp ' ' ' [-] example (mailreader) ' ' (needs to be merged with latest ' ' from several places) ' ' [-] src ' ' [+] java ' ' [+] resources ' ' [+] test ' ' [+] webapp ' ' ' [-] examples ' ' (exercise, upload, validator) ' ' (i feel this should be renamed to 'modules') ' ' [-] src ' ' [+] java ' ' [+] resources ' ' [+] test ' ' [+] webapp ' ' ' [-] test ' ' (really need to get this back in order ' ' or figure out a new strategy..more on ' ' this later) ' ' [-] src ' ' [+] java ' ' [+] resources ' ' [+] test ' ' [+] webapp ' ' ' [-] tile-documentation ' ' (this should probably go to tiles/trunk) ' ' [-] src ' ' [+] java ' ' [+] resources ' ' [+] test ' ' [+] webapp
- merge the mailreader sample app (and tests) from commons-chain to struts "apps" (as indicated above)
I would like all the apps/trunk/foo to be mavenized, and each project.xml creates a single .war file suitable for deployment. Each project would/should inherit from a parent project.xml under apps/trunk that can build the entire set of apps. So you can build any app you like, or just build them all. The build.xml file will be generated by maven (hopefully the path issues will be resolved).
So long as the version dependencies for each app point to published JARs, this should work fine. For those that have some new stuff, may require the developer do a 'maven install' from core/trunk of course (for dev builds). And as we move along with the different subprojects, each can keep up with the latest.
-- Martin Cooper
-- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]