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 20:59:59 UTC

[jira] Created: (WICKET-2073) mvn deploy -DaltDeploymentRepository=... fails

mvn deploy -DaltDeploymentRepository=... fails
----------------------------------------------

                 Key: WICKET-2073
                 URL: https://issues.apache.org/jira/browse/WICKET-2073
             Project: Wicket
          Issue Type: Wish
    Affects Versions: 1.4-RC3
            Reporter: Dominik Drzewiecki
            Priority: Minor


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.


[jira] Reopened: (WICKET-2073) mvn deploy -DaltDeploymentRepository=... fails

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki reopened WICKET-2073:
----------------------------------------


My patch was indeed broken for I have stripped manually generated .diff from the changes that were not related to this issue. My bad, sorry.
But what you have done was not what I had had in mind. I noticed that you added the snapshot repo element in the "bamboo" profile (which, to me, might have some unforeseen implications and I definitely wouldn't have tinker with), while I originally wanted it to exist in the "all" profile which is the default one when no profile is selected either on the CLI or in $M2_HOME/settings.xml. I'll provide another patch reverting your change and applying mine correctly.

> 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-RC2
>            Reporter: Dominik Drzewiecki
>            Assignee: Igor Vaynberg
>            Priority: Minor
>             Fix For: 1.4-RC3
>
>         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.


[jira] Updated: (WICKET-2073) mvn deploy -DaltDeploymentRepository=... fails

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-2073:
---------------------------------------

        Fix Version/s: 1.4-RC3
    Affects Version/s:     (was: 1.4-RC3)
                       1.4-RC2

> 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-RC2
>            Reporter: Dominik Drzewiecki
>            Assignee: Martijn Dashorst
>            Priority: Minor
>             Fix For: 1.4-RC3
>
>         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.


[jira] Assigned: (WICKET-2073) mvn deploy -DaltDeploymentRepository=... fails

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg reassigned WICKET-2073:
-------------------------------------

    Assignee: Martijn Dashorst

> 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
>            Assignee: Martijn Dashorst
>            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.


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

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Updated: (WICKET-2073) mvn deploy -DaltDeploymentRepository=... fails

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-2073:
---------------------------------------

    Attachment: pom.xml.patch

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
>    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.


[jira] Updated: (WICKET-2073) mvn deploy -DaltDeploymentRepository=... fails

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-2073:
---------------------------------------

    Attachment:     (was: pom.xml.patch)

> 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-RC2
>            Reporter: Dominik Drzewiecki
>            Assignee: Igor Vaynberg
>            Priority: Minor
>             Fix For: 1.4-RC3
>
>         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.


[jira] Resolved: (WICKET-2073) mvn deploy -DaltDeploymentRepository=... fails

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-2073.
-----------------------------------

    Resolution: Fixed

yeah, my bad. i didnt notice i added it to the bamboo profile

> 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-RC2
>            Reporter: Dominik Drzewiecki
>            Assignee: Igor Vaynberg
>            Priority: Minor
>             Fix For: 1.4-RC3
>
>         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.


[jira] Resolved: (WICKET-2073) mvn deploy -DaltDeploymentRepository=... fails

Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-2073.
-----------------------------------

    Resolution: Fixed
      Assignee: Igor Vaynberg  (was: Martijn Dashorst)

we already had a snapshot repo defined, so your patch broke pom.xml. did you not try applying it before you provided it?

anyways, i added the regular repo into the pom.

> 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-RC2
>            Reporter: Dominik Drzewiecki
>            Assignee: Igor Vaynberg
>            Priority: Minor
>             Fix For: 1.4-RC3
>
>         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.


[jira] Updated: (WICKET-2073) mvn deploy -DaltDeploymentRepository=... fails

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-2073:
---------------------------------------

    Attachment: pom.xml.patch

Corrected patch.

> 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-RC2
>            Reporter: Dominik Drzewiecki
>            Assignee: Igor Vaynberg
>            Priority: Minor
>             Fix For: 1.4-RC3
>
>         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.


[jira] Updated: (WICKET-2073) mvn deploy -DaltDeploymentRepository=... fails

Posted by "Dominik Drzewiecki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Drzewiecki updated WICKET-2073:
---------------------------------------

    Component/s: wicket

> 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.