I think this is reasonable, but I'm not totally thrilled about the fact that you then cannot build the distributions with Maven.
Sure we can, we just use the reactor and set the check style props to a relative path (say ../site/conf/qa/CheckStyle and ../site/LICENSE.CheckStyle)
Also, I don't use "current", although maybe I should, but I think it would then be annoying that the relative paths to the shared files only works in one of two possible SVN states.
No problem there either, we just run through a set of known paths and set the appropriate prop to match.
We would test for ../core, then ../../core/trunk, then svn.core.path, if still not found, then fail.
I don't mean to say that it's better to have copies all over the place, but these are things that have frustrated me about our options.
Joe
The more I use Maven, the more I likes. There are definitely some quirks, but I feel comfortable with it.
-- 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]
