> -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: 20 September 2003 22:29 > To: 'Cactus Developers List' > Subject: RE: [Q] New structure for cactus documentations? > > > > > -----Original Message----- > > From: Christopher Lenz [mailto:[EMAIL PROTECTED] > > Sent: 20 September 2003 22:21 > > To: Cactus Developers List > > Subject: Re: [Q] New structure for cactus documentations? > > > > [snip] > > > > What do you think? > > > > Sounds good. However, where would we put things like the skin (css, > > images, etc)? > > > > Good point Chris! We have several options: > > 1/ put it in the master project and make it an artifact of that project. > Subprojects will depend on it > > 2/ Create a build project containing custom stuff needed by our build. > For example build-common.xml, any custom Ant task, skins, etc could go > in there > > 3/ Duplicate it... arg! >
Actually there is a 4th option (it's a variation of 2/) 4/ All shared build stuff goes in the root directory. This is actually what we've been doing so far: - build-common.xml - checkstyle.xml - common properties If we follow that we could add the XSL stylesheets. Thinking about it, what we're doing is not really clean and having a build/ directory with these shared build data would be an better option. However with option 4/ it doesn't have to be a specific project, simply a well-known location for shared build data. My option 2/ was a real project. All in all, I prefer option 4/ as it is more lightweight and does not necessitate to build a project before being able to build the other projects. -Vincent > I'm hesitating between 1/ and 2/. I think 2/ is cleaner. In maven terms > it means we would have custom Maven plugins for complex stuff which is > probably the best way. So I would tend to prefer 2/. > > -Vincent > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
