Message-ID: <1835897991.2633.1369306381770.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2632_629264317.1369306381769" ------=_Part_2632_629264317.1369306381769 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Quaere depends on you to contribute. Anyone can get inv= olved by submitting patches to the code or anything else. If you discover a= defect in Quaere, please let us know.
Quaere is a Codehaus project and therefore lives by the Codehaus= manifesto. Please refer to this manifesto if your interested joining t= he project. The best way to become part of the project is to show your comm= itment by submitting patches, taking part in discussions on the mailing lis= ts and so forth.
The day to day discussions takes place on the developer mailing list. If you're interested in participating, we str=
ongly suggest that you subscribe to this list. However, this is not a requi=
rement, you can also submit patches through our issue trac=
You can also chat with developers from Quaere, and other Codehaus projects,= in the codehaus room at irc.codehaus.org.
To get started with Quaere development you can get the source code from = our Subversion repository. Anonymous access is available through = http://svn.codehaus.org/quaere/.
Quaere is built with Maven. To build and test your fresh copy of = the project you can use the following command;
To jump start development you can use Maven to setup IDE.
A patch is a file shows the changes of one or more files. It is useful t= o us as we can see exactly what you changed, think about the implications a= nd ultimately approve the patch so your changes are committed to the code r= epository.
We strongly encourage that you include test cases and documentation chan= ges on your patch. If you need any help on how to test something, ask for h= elp on the development mailing list.
Once you've made a change to one or more files in you working copy of Qu= aere you can create your patch using your favorite Subversion client. Below= is an example of how to use the command line SVN client.
If your patch targets many files in different directories, we prefer tha= t you create your patch from the project root. This makes it easier for a c= ommitter to recognize where the patch should be applied.
|Adding new files|
If your modification includes new files or new folders you must =
add them before you create the patch. If you're using the command =
line client you can do this with the
To contribute your patch to the project, we prefer if you write a commen= t on the JIRA issue the patch is for in our issue tracker<= /a> and attach your patch to this comment. Alternatively, you can attach th= e patch to an email on our developer mailing li= st.------=_Part_2632_629264317.1369306381769--