Message-ID: <87173625.4851.1425179854757.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4850_1793301610.1425179854757" ------=_Part_4850_1793301610.1425179854757 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Here are the steps you'll need to follow to get Maven 2 working = with the Codehaus's WebDav system= .=20
The M2 repository ID is automatically configured when your project is cr= eated. In the event you need to change it, please contact Support to get them to change it.=20
There are many downstream effects and we need to review non-standard IDs= .=20
The repository is automatically synchronized with the main Maven reposit= ory on a 4 hourly schedule.=20
Then you'll need to tell the <build> section about the Wagon WebDA= V plugin:=20 =20
Next you'll need to update your distributionManagement section:=20 =20
Note: the trailing slash is important; otherwise Apache will send 301 re= directs that confuse the Maven WebDAV plugin.=20
You should only put these in your root POM in a multi-module pro= ject. If you put the same settings in a child POM, that child woul= d overwrite the files at this location. You can either inherit it using Mav= en's parent mechanism (which will automatically append the artifactId to th= e URL), or you can specify as above but change the individual paths to the = location you'd like the files deployed to.=20
Then you'll need to tell maven's settings.xml file about your username a= nd password (this file belongs in ~/.m2):=20 =20
Finally, Before you can upload via HTTP= S you'll need to add the AddTrust CA certificate (the issuer of the Codehau= s certificate). To do this, follow the instructions at the bottom of the WebDAV page.
You must configure a repository ID is set.=20
Now you can use the normal maven deploy command:=20 =20
You will need to navigate down to the appropriate location for your arti= facts.