Re: Subversion Refactoring Frenzy and Maven Questions
On Sun, 10 Oct 2004 08:29:20 -0400, Ted Husted [EMAIL PROTECTED] wrote: On Sat, 09 Oct 2004 21:06:44 -0700, Craig McClanahan wrote: ... Interestingly, this subproject has four subsubprojects ... Are you counting the MailReader database as a separate artifact? I hadn't been, and that actually makes sense ... it's used by two of the artifacts that I *did* count (both the non-Tiles and Tiles versions of mailreader). We also use it for the conventional Struts example, and it might be best if it were a separate entity that could shared by the various examples. Yep ... even the form beans and actions of mailreader are likely to be abstractable into something separate if we wanted to. For the sake of continuity, I had also started to use the MailReader as an example for using Commons Chain as an web application platform. One of my comrades on Team iBATIS, Larry Meadors, has also done a iBATIS version of MailReader. If there were a MailReaderDatabase subproject, we might be able to get him to donate the code, so there would be both XML and JDBC implementations of the MailReader DAOs. Splitting out the database part of mailreader seems like an obvious first step. How about a top level examples directory with a mailreader-database subdirectory to contain this artifact? If the business logic turns out to be reusable too, that could go in a parallel mailreader-actions subdirectory. -Ted. Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Roadmap
On Sun, 10 Oct 2004 16:04:40 -0400, Mike Stanley wrote: Another simple suggstion I would like to make (enhancement request) - it would be extremely powerful to add the property support that exists for plugin configuration, to action and request processors. This can go along way for special purpose actions. The parameter attribute is ok - but too limiting (IMO). Sounds good to me. You should file this with Bugzilla and attach a patch if you can. A related enhancement, which is long overdue, is * Enhance all configs to extend one configuration element from another, as is done with Tiles Definitions I'd dearly love to see a patch for this enhancement. It would make such a difference in so many Struts config files. And now that we're in the 1.3 zone, the gloves are off :) -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: struts, maven example projects
I intend to continue to work to make Maven a good way to build Struts. We use Maven extensively at my day job, so I'm happy to build synergy between that and working on Struts. Nathan, in looking specifically at your project, I'm wondering one thing: are you using the term Module synonymously with the sense of a Struts module as a separate config/* entry in the web.xml? Or is module just your term for a unit of a web application? I will make a note of your project. I can't guarantee when I'll have time to check it out further, and I have to admit that I don't immediately see it as a solution to any specific problem I've been having -- but since I am a Maven user and a Struts user, it may turn out to be interesting. So by now you've gotten the message that Struts will continue to have a Maven project.xml file, and it may be a while (if ever) before it matters more than that how official Struts' use of Maven is -- but if you have suggestions for improving the ways in which Struts (the project) uses Maven, I'm all ears. Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn back; I'll know I'm in the wrong place. - Carlos Santana - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Subversion Refactoring Frenzy and Maven Questions
On Sun, 10 Oct 2004 13:22:27 -0700, Craig McClanahan wrote: Splitting out the database part of mailreader seems like an obvious first step. How about a top level examples directory with a mailreader-database subdirectory to contain this artifact? If the business logic turns out to be reusable too, that could go in a parallel mailreader-actions subdirectory. Moving everything over into a standard Subversion layout was the right thing to do, but as we reorganize, we may want to create a top-level directories for each major release series. Such as: /v1/trunk/struts-core /v1/trunk/struts-faces /v1/branches and /v2/trunk/struts-core /v2/trunk/struts-faces (if we needed such a thing) /v2/branches Since it does look like we will have parallel v2 development and v1 maintenance/evolution. Then, whatever is under the root /trunk has not been reorganized yet, and everything under /v1/trunk has already been reorganized as an artifact. Since we have a number of applications knocking around, I would suggest we have an applications or apps subproject, that could host all the various examples. So, we might have something like /v1/trunk/apps/struts-blank /v1/trunk/apps/struts-examples /v1/trunk/apps/struts-mailreader /v1/trunk/apps/struts-mailreader-database /v1/trunk/apps/struts-mailreader-faces /v1/trunk/apps/struts-mailreader-faces-tiles /v1/trunk/apps/struts-tiles-examples Here, each folder under apps/ would represent a separate artifact that could be released separately, or bundled with other subprojects to form a product distribution. (Like the best available of everything.) Aside from apps/, the other top-level folders under trunk/ might each represent a separate artifact that could be released separately, such as: apps/ struts-core/ struts-site/ struts-bsf/ struts-el/ struts-faces/ struts-scripting/ struts-taglib/ -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: struts, maven example projects
Nathan, in looking specifically at your project, I'm wondering one thing: are you using the term Module synonymously with the sense of a Struts module as a separate config/* entry in the web.xml? Or is module just your term for a unit of a web application? yes, we're using 'module' to mean a struts module - /WEB-INF/[module-name]/struts-config.xml /WEB-INF/[module-name]/tiles-defs.xml /[module-name]/foobar.jsp /[module-name]/styles/ /[module-name]/images/ etc following this structure: http://www.codeczar.com/beta/maven-struts-module-plugin/standards.html I will make a note of your project. I can't guarantee when I'll have time to check it out further, and I have to admit that I don't immediately see it as a solution to any specific problem I've been having -- but since I am a Maven user and a Struts user, it may turn out to be interesting. We see two uses of this plugin: 1) a mechanism to include 3rd party struts-module components within your web-application. e.g. LogWeb. http://www.codeczar.com/beta/logweb/ We had the idea for this plugin as many users had problems bundling LogWeb within their web-apps, so we automated the bundling process with this plugin. This is just an idea, but this plugin would pave the way for other generic web-components. It then becomes simple for developers to bundle these components into their webapps - e.g user management module, security module, messageboard module, etc. 2) a mechanism to manage complex web-apps consisting of many modules - facilitates decomposing your web-app project into many smaller module projects e.g: http://www.codeczar.com/beta/struts-examples/ not strictly neccessary for the struts example web-app (as its fairly simple) but it demonstates the plugin. Another idea would be that all of the struts webapps could be built as modules as part of a single web-app - example, examples (upload, validator, exercise), documentation, tiles-documentation So by now you've gotten the message that Struts will continue to have a Maven project.xml file, and it may be a while (if ever) before it matters more than that how official Struts' use of Maven is -- but if you have suggestions for improving the ways in which Struts (the project) uses Maven, I'm all ears. we hacked around the project xml for the example app: http://www.codeczar.com/viewcvs/viewcvs.cgi/struts-examples/project.xml?rev=HEADcvsroot=Strutscontent-type=text/vnd.viewcvs-markup not sure if this is of use to you. More than happy to lend a hand getting the struts examples working with maven regardless of whether they use our struts-module plugin. let me know where I can help. cheers Nathan Joe -- Nathan Coast Managing Director codeczar ltd mobile: (852) 9049 5581 email: mailto:[EMAIL PROTECTED] web:http://www.codeczar.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
