Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
2.1
-
None
-
None
Description
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>'.