Maven 2.x and 3.x Site Plugin

Make the distributionManagement.site.url configurable from the command line

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 2.0-beta-6
  • Fix Version/s: None
  • Component/s: site:deploy, site:stage(-deploy)
  • Labels:
    None
  • Number of attachments :
    0

Description

It should be possible to override the attribute distributionManagement.site.url from the command line like this:

mvn site:site site:deploy -DdistributionManagement.site.url=file:///some/local/or/external/path/

This would not really be necessary if site:stage worked like it should but is needed since it does not.

Issue Links

This issue is duplicated by:
MSITE-308 allow specifying an alternate repository URL on the command-line Major Closed
MSITE-414 Add configuration parameter to the deploy goal, where effective deployment location is. Major Closed
This issue is related to:
MSITE-533 make site:stage a local file deploy Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Yongshin Yu added a comment -

Is there a way that I could set the site url to be dynamic? I would like to publish to a folder based on a buildNumber generated by the maven-buildnumber-plugin. Please let me know. Otherwise I am going to be forced to open up a new issue. Thanks.

<distributionManagement>
<site>
<id>buildsite</id>
<name>Build Site</name>
<url>
scp://mycompany.com/buildrepository/builds/${buildNumber}
</url>
</site>
</distributionManagement>

Show
Yongshin Yu added a comment - Is there a way that I could set the site url to be dynamic? I would like to publish to a folder based on a buildNumber generated by the maven-buildnumber-plugin. Please let me know. Otherwise I am going to be forced to open up a new issue. Thanks. <distributionManagement> <site> <id>buildsite</id> <name>Build Site</name> <url> scp://mycompany.com/buildrepository/builds/${buildNumber} </url> </site> </distributionManagement>
Hide
Permalink
luke w patterson added a comment -

this feature is needed, it would align with deploy's altDeploymentRepository parameter

http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#altDeploymentRepository

Show
luke w patterson added a comment - this feature is needed, it would align with deploy's altDeploymentRepository parameter http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#altDeploymentRepository
Hide
Permalink
Wendy Smoak added a comment -

Did you try it with the build helper plugin and ${buildNumber} in the url?

Or with another property, and then passing it in with -Dpropname=value on the command line?

I routinely use ${project.version} in the site url to publish docs for each version (to /docs/1.0-SNAPSHOT most of the time, then to /docs/1.0/ from the tag, without changing anything.)

Show
Wendy Smoak added a comment - Did you try it with the build helper plugin and ${buildNumber} in the url? Or with another property, and then passing it in with -Dpropname=value on the command line? I routinely use ${project.version} in the site url to publish docs for each version (to /docs/1.0-SNAPSHOT most of the time, then to /docs/1.0/ from the tag, without changing anything.)
Hide
Permalink
Matthias Wegerhoff added a comment -

I got the same problem. We are running multiple builds with site:deploy on our build-server. Currently every projects pom has to configure the
distributionManagement.site.url which describes a path on the buildserver. In my opinion the best way to solve this problem would be to allow
configuration of distributions in Maven Local Settings Model as described in http://jira.codehaus.org/browse/MNG-2553.

Show
Matthias Wegerhoff added a comment - I got the same problem. We are running multiple builds with site:deploy on our build-server. Currently every projects pom has to configure the distributionManagement.site.url which describes a path on the buildserver. In my opinion the best way to solve this problem would be to allow configuration of distributions in Maven Local Settings Model as described in http://jira.codehaus.org/browse/MNG-2553.
Hide
Permalink
Lukas Theussl added a comment -

After MSITE-533 you can use site:stage or site:stage-deploy which can both be configured.

Show
Lukas Theussl added a comment - After MSITE-533 you can use site:stage or site:stage-deploy which can both be configured.

People

Vote (6)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.