Since you use Nexus, there is another workaround. Upload the jar and pom
with the build in upload function in Nexus. Just right-click the
repository where you want to deploy you artifact and select upload.
//Swanthe
[email protected] wrote:
Our company have recently decided to switch to wicket 1.4, even though
is still hasn't reached GA status. Therefore, first we started using
latest rc1 builds, and later on even cutting edge builds from the
trunk. And then we stumbled upon a severe (but resolvable) problem
which is not wicket related but rather belongs to the maven. To be
short: we use a mirror repository (nexus) and deploy trunk builds of
wicket right there. It should be as easy as getting sources from trunk
(svn checkout http://svn.apache.org/repos/asf/wicket/) and building
using (mvn package deploy
-DaltDeploymentRepository=Nexus::default::http://w51229:8081/nexus/content/repositories/snapshots).
Apparently it isn't. 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> in the effective
profile in order to substitute its configuration with the parameters
passed on te command line. Without it, which is the case when building
wicket, maven fails. Though I hate such workarounds, would you please
consider adding a dummy <distributionManagment> to the "all" profilein
the wicket parent pom, possibly with some reasonable defaults for
<url> element.
It should look like this.
<distributionManagement>
<repository>
<id>repo</id>
<name>Repository Name</name>
<url>scp://host/path/to/repo</url>
</repository>
<snapshotRepository>
<id>repo</id>
<name>Repository Name</name>
<url>scp://host/path/to/repo</url>
</snapshotRepository>
</distributionManagement>
I'll file a jira issue against wicket 1.4 rc3 if you find it reasonable.
regz,
Dominik Drzewiecki
