Brian E. Fox wrote:
Seems fishy to me as well. We have inheritance for a reason.
Over at Mojo I suggested adding <scm> several times for the following
reason. Most of the time, a plugin inherits from a released parent whose
SCM URL points to its tag, say
repo/tags/parent-1
Now, running "mvn site" on a plugin POM that just inherits this URL will
deliver
repo/tags/parent-1/foo-maven-plugin-X
i.e. the plugin's SCM URL points erroneously to a sub directory of the
parent's tag.
This phenomenon is irrelevant as long as no snapshot sites are deployed
from the trunk. During a release, the Release Plugin's tagBase parameter
should kick in and ensure the assembled SCM URL is correct. Not sure
how/if this is related to the problems Dennis described.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
