That's the ideal scenario, but pom changes mean 2.1. I can't think of any other way to handle this without causing even more havoc.
-----Original Message----- From: William Ferguson [mailto:[EMAIL PROTECTED] Sent: Sunday, October 28, 2007 8:25 PM To: Maven Developers List Subject: MNG-3244 [was RE: 2.0.8 Release Candidate] Brian, are you suggesting that a POM property be used invoke the new behaviour, and lack of it invokes existing behaviour? I'd be happy with that. William -----Original Message----- From: Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Thursday, 25 October 2007 10:09 PM To: Maven Developers List Subject: [***POSSIBLE SPAM***] - RE: 2.0.8 Release Candidate - Email has different SMTP TO: and MIME TO: fields in the email addresses I think the biggest problem with fixing this issue is that it will probably break lots of people's builds. If there is some other indicator that it shouldn't be inherited, then that would probably be acceptable. -----Original Message----- From: William Ferguson [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 10:01 PM To: Maven Developers List Subject: RE: 2.0.8 Release Candidate It's a real shame that MNG-3244 had to be reverted. Now there is no way for an inherited site#url to actually specify the url for a project. The current behaviour in which the child artifactId is always appended is non-intuitive IMHO. It only makes sense for inherited POMs in multi-modules POMs and not always then. In any case, since this has been reverted, can the documentation at http://maven.apache.org/guides/mini/guide-site.html be updated to reflect the actual behaviour. William --------------------------------------------------------------------- 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]