Message-ID: <1917941303.41212.1371644005754.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_41211_958285108.1371644005753" ------=_Part_41211_958285108.1371644005753 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This document is indended to record the development precedures used by t= he Maven development community.
The primary audience is Maven committers.
To be able to build the latest SVN version of some part of Maven you wil= l need to add some configuration on your development machine.
First on the agenda is to enable you to download snapshot versions from =
the Apache snapshot repository. Add a profile for your Apache related setti=
ngs in your
settings.xml like this:
This tells Maven where to find snapshot versions of plugins and other ar= tifacts. To use a profile you must tell Maven that you want to use a profil= e and pass along the id of that profile. When invoking Maven do it like thi= s:
If you want to read more about profiles, see this page.
To publish a snapshot of some part of Maven you need to tell Maven what = your Apache username is. This is how you do it:
You also need to be a member of the group apcvs on people.apach= e.org.
Due to a bug in Maven there may be problems with the file permissions on= the server after a snapshot has been published. Please read this page on how to fix your own files.
If someone else has not cleaned up after themselves you can run these co=
mmands on the shell to fix it. Important: don't run it all=
in one batch, as it uses the
-f flag for
e sure the files have been copied before you remove them.
To publish a website for some part of Maven you need to tell Maven what = your Apache username is. This is how you do it:
You also need to be a member of the group maven on people.apach= e.org.
When publishing plugin docs, be sure to activate the reporting = profile with -P reporting.
To publish a schema, first generate it, then scp it to people.apache.org= .
The schemas should be published to http://maven.apache.org/xsd/= a>
The schemas currently in /www/maven.apache.org are:
These files should be removed, and symlinks added to the actual files in= /xsd.
See: http://www.nabble.com/Publish= ing-schemas-t2566129s177.html for discussion------=_Part_41211_958285108.1371644005753--