You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Dominik Drzewiecki (JIRA)" <ji...@apache.org> on 2009/02/03 21:15:59 UTC

[jira] Issue Comment Edited: (WICKET-2073) mvn deploy -DaltDeploymentRepository=... fails

    [ https://issues.apache.org/jira/browse/WICKET-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670090#action_12670090 ] 

drzewo edited comment on WICKET-2073 at 2/3/09 12:14 PM:
---------------------------------------------------------------------

Proposed patch for the wicket-parent/pom.xml. After applying, by default, when mvn deploy is invoked with no extra parameters, it deploys built artifacts (both snapshots and releases) to the target/m2-repo in the wicket-parent directory. When -DaltDeploymentRepository parameter is passed in, deployment works just fine fine. I hate such a workaround as it is maven deploy plugin itself that should be fixed, but well, I guess we'll have to live with that.

      was (Author: drzewo):
    Proposed patch for the wickrt-paren/pom.xml. After applying, by default, when mvn deploy is invoked with no extra parameters, it deploys built artifacts (both snapshots and releases) to the target/m2-repo in the wicket-parent directory. When -DaltDeploymentRepository parameter is passed in, deployment works just fine fine. I hate such a workaround as it is maven deploy plugin itself that should be fixed, but well, I guess we'll have to live with that.
  
> mvn deploy -DaltDeploymentRepository=... fails
> ----------------------------------------------
>
>                 Key: WICKET-2073
>                 URL: https://issues.apache.org/jira/browse/WICKET-2073
>             Project: Wicket
>          Issue Type: Wish
>          Components: wicket
>    Affects Versions: 1.4-RC3
>            Reporter: Dominik Drzewiecki
>            Priority: Minor
>         Attachments: pom.xml.patch
>
>
> Due to the longstanding bug in maven deploy plugin (http://jira.codehaus.org/browse/MDEPLOY-54) it is required that the pom itself contains <distributionManagment> element in the effective profile in order to substitute its configuration with the parameters passed onto command line. Without it, which is the case when building wicket and deploying it to the corporate repository (using mvn package deploy -DaltDeploymentRepository=Nexus::default::http://host/nexus/content/repositories/snapshots), maven fails. Please provide <distributionManagment> to the "all" profile in the wicket parent pom, possibly with some reasonable/transparent defaults for <url> subelements.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.