> I'd like to get them all consolidated (at least as much as can be done)providing a single mailreader.jar for the variations.
Do you mean one jar of the bits common to all flavours, and then separate apps for each variation? If so, I think this would be a good approach. If you mean combine the various mailreader apps into one, I think that would muddy the waters, and wouldn't work as well as examples of how to do things.
I've seen talk before about bundling the "business app" part of Mailreader into its own jar, which I think is what you meant in your first sentence, Martin. I think this is a good idea, because I think beginning struts users sometimes don't have a good sense of how to arrange for good separation of Struts from a more generalized framework. In so far as we can demonstrate this a little bit, that would be a good thing.
> >> We need to come up with one standard structure - we seem to have quite > a few at the moment. The sources go in different places, the config > files go in different places, etc. Not easy to follow at all.
Yes, that's exactly what I intend to clean up. Please don't hesitate if something looks odd, or if you prefer a diffent name.
Where did 'conf' or 'config' go? We currently have 'conf/share', 'src/conf', etc., but I don't see where those land in your structures.
I was assuming most of those things landed in src/resources. Personally, I'd be more comfortable with putting the things that get bound into the jar in src/resources under their final classpath. This works more automatically with maven, and I think it's clearer.
That is, move conf/share/chain-config.xml to src/resources/org/apache/struts/chain/chain-config.xml
For things which are conventionally put in WEB-INF, we'd need to agree to a location. I think it might be nice to be more clear about that, perhaps with conf/webinf or src/webinf but I don't feel too strongly about it.
> Not sure how many people caught my rename for 'examples' :D
I admit that I missed it until you mentioned it just now. It could certainly use a new name, but I'm not sure about 'modules'.
I missed it too. I'm nervous that "modules" is too reminiscent of Struts modules specifically, especially since it's a relatively uncommon word otherwise. What's wrong with examples, besides that there's also an "example"? Should those two be merged? I have to admit that I haven't spent a lot of time with the example webapps (until this week!) and don't want to get in the way of anything you're motivated to do...
No, that's fine. If you have an itch to put a Maven build system together, more power to you. I was actually taking tips from Maven for the Ant build system anyway. ;-)
On the topic, I think that one of the biggest perceived limitations of Maven for Struts right now is that it doesn't "do everything that the Ant build does." While this is true, it's likely to become less so if we move the webapps and the Struts site into their own areas of the SVN repository. If "core" is really just about creating a struts.jar, I think we'll find that we can get Maven doing everything it needs to do much more readily.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
