Hi, Yes, you can have a struts/site with site documentation that can include all modules documentation (and is the recommended way)
About extending projects you shouldn't extend the concrete projects (e.g. struts core), it's better to create convenience project.xml files (e.g. in struts/maven) BTW the Maven 1.0 will be released by this week, it has already been voted in the PMC Carlos Sanchez A Coruņa, Spain Oness Project http://oness.sourceforge.net > -----Original Message----- > From: Joe Germuska [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 13, 2004 12:45 AM > To: Struts Developers List > Subject: Re: CVS reorg: jakarta-struts -> struts > > At 2:43 PM -0700 7/12/04, Martin Cooper wrote: > >I'm not completely sure I understand what you're proposing, but here > >are a couple of points to bear in mind: > > I may not understand it either. But I decided I'd like to > see it move forward. So... > > Regarding CVS vs. SVN. I have zero SVN experience. I'm not > opposed to it, but it will be slower for me personally if we > go that route, > as I'm starting at the bottom of the learning curve. However, the > tool is much less important to what I'm trying to achieve > than the structuring in preparation for using maven to its fullest. > > Regarding the "limitations of Maven's multi-project capabilities," > I'm sure there are some, but I'm not sure I'll know what they > are until I see them. I've already set up struts-el and > struts-chain with project.xml files which extend the Struts > base one and it works for those, at least. This is just for > building, not necessarily for extended features. > > I would agree that we should have a consensus on the > top-level structure. After that, I would need to have some > real files to work on to make sure that Maven is building > correctly, etc. > > Regarding the structure: > > My understanding was that we had settled on a single module, > "struts", under which we would have something like below > (mostly lifted from an email from Ted to the [EMAIL PROTECTED] list) > > struts/ > struts/core > struts/apps > struts/site > struts/opt-taglib > struts/opt-el > struts/opt-faces > > etc. > > But I'm not married to that. I think a single module is > easier for a lot of reasons, and you can partition the space > within the module as much as you want so that I don't think > you need parallel modules. I don't have a strong opinion > about how the module is partitioned. One of the things I > need to experiment with is whether it works to have a "site" > directory alongside other directories when you go to build > the site with Maven. I'm not sure if that'll work or not. > > Regarding Martin's suggestion to import the current CVS HEAD > into SVN and then move things around... I don't know enough > SVN to know if that makes sense or not. > > Please speak up with suggestions and opinions... > > 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]
