On 9/24/06, Stephen Duncan <[EMAIL PROTECTED]> wrote:
On 9/24/06, Garrett Rooney <[EMAIL PROTECTED]> wrote:
> On 9/24/06, Stephen Duncan <[EMAIL PROTECTED]> wrote:
> > I don't see any harm in them at least staying correct for the trunk;
> > no maintenance to keep that true.
>
> Except that they're incorrect on every non-trunk branch or tag unless
> we update them every time we branch/tag. That seems bad to me.
>
> -garrett
Being incorrect seems no worse than not being there. And being
correct on trunk has some benefits. Even though we do not use the
Maven site as the Abdera website, creating the Maven site locally to
use for seeing code reports, including, potentially, the changelog
report that reports on file-activity, dev-activity, and a general
changelog, is still useful.
Honestly, being wrong really does seem worse than not having it in my
opinion, but maybe that's just me.
Ideally we'd only be changing it in one place: the parent pom.
However, that apparently would require the modules folder-names to
match their artifactId, i.e. java/trunk/core -> java/trunk/abdera-core
Maven doesn't allow any way to override that sort of behavior?
-garrett
