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