You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lukas Theussl (JIRA)" <ji...@codehaus.org> on 2010/12/20 15:45:58 UTC

[jira] Commented: (MSITE-471) ${project.distributionManagement.site.url} can't use ${property} values in multi module projects

    [ http://jira.codehaus.org/browse/MSITE-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249149#action_249149 ] 

Lukas Theussl commented on MSITE-471:
-------------------------------------

The project.distributionManagement.site.url is still required in a multi-module build in order to know the effective deploy location of the sub-modules, so indicating a dummy url as above is actually the proper solution.

I didn't see anything unusual with the property resolution either (note that things like ${project.artifactId} will resolve to the child artifactId, so it will be different for each module.) Otherwise please specify what exactly you see vs. what you expect.

> ${project.distributionManagement.site.url} can't use ${property} values in multi module projects
> ------------------------------------------------------------------------------------------------
>
>                 Key: MSITE-471
>                 URL: http://jira.codehaus.org/browse/MSITE-471
>             Project: Maven 2.x and 3.x Site Plugin
>          Issue Type: Bug
>          Components: inheritance, site:deploy
>    Affects Versions: 2.1
>            Reporter: Andrew Hughes
>
> I wanted to use the site:stage-deploy goal. In order to use this I needed to provide a ${project.distributionManagement.site.url}. Which, first I think it wrong, since I provide my own 'stagingSiteURL' the ${project.distributionManagement.site.*} will not be used.
> Because we don't actually have a scp, ftp, svn... location to deploy to I tried to substitute a ${project.distributionManagement.site.url} that I knew every maven user would have. Since they have ~/.m2/repository I tried using...
> <url>file://${settings.localRepository}/../sites/${project.groupId}</url>
> But when this is used with a multi module project, and with a 'stagingSiteURL' some very strange url's are built when trying to stage-deploy. This means the modules never deploy.
> There's a few things going on here. My workaround means I just have to have ${project.distributionManagement.site.url}=='<url>not-used</url>'.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira