[
https://jira.codehaus.org/browse/MSITE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274496#comment-274496
]
Benson Margulies commented on MSITE-600:
----------------------------------------
I have projects where the parent is released and deployed independently of the
child. In fact, much of Maven itself works this way. There is still a
relativePath for use in SNAPSHOT development when everything in the tree
happens to be hanging out together.
This is a regression from 2.2 (2.3 has other problems in this area), where it
works fine.
It seems to me that the code should ask, 'is the resolved child <url>
absolute', and, if it is, don't change it; checking to see if the protocols are
different couldn't hurt either.
In general, if I wanted inheritance, I'd leave the <url> spec out of the child.
If I write a spec in a child, it has to override the parent.
> site plugin 2.4 does not permit a child to fully override parent site
> deployment URL
> ------------------------------------------------------------------------------------
>
> Key: MSITE-600
> URL: https://jira.codehaus.org/browse/MSITE-600
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: site:deploy
> Affects Versions: 2.4
> Reporter: Benson Margulies
> Attachments: muddle.tar
>
>
> The test cases here has a parent with a a distributionManagement/site/url,
> and then a child which overrides it with an absolute URL. Except that the
> override does not work ... or, at least, looks quite peculiar.
> the parent is file:///tmp/bloop
> the child is scp://localhost:/tmp/blop
> and the result is
> [INFO] Error uploading site
> Embedded error: Could not make directory
> '/tmp/bloop/../../Users/benson/asf/mvn/site-interp-muddle/child/scp:/localhost:/tmp/blop'.
> [INFO] ---------------------------------------
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
