TBD

Source code for the Apache Abdera2 Project is currently managed through Subversion (SVN).

If you just want to browse the source code, you can use the web interface to Subversion.

Anyone can check code out of Subversion. You only need to specify a username and password in order to update the Subversion repository but only Abdera committers have the permissions to do that. You can use the command line in order to check out the current version of Abdera2 code:

svn checkout http://svn.apache.org/repos/asf/abdera/abdera2/

Any Abdera committer should have access to the abdera repository at svn.apache.org. If not please write a mail to dev@abdera.apache.org. Please make sure that you used a secure connection for checkout (or use relocate):

svn checkout https://svn.apache.org/repos/asf/abdera/abdera2/

Committing changes:

svn commit

If Subversion can't figure out your username, you can tell it explicitly:

svn --username you commit

Subversion will prompt you for a password, and once you enter it once, it will remember it for you.

Abdera2 uses Maven for building and dependency management. Simply navigate to the root of the Abdera2 project and run:

mvn install

To build the distribution, include the deploy profile:

mvn install -Pdeploy

The built artfacts for the project will be installed to your local Maven Repository.

The Abdera2 build generates a handful of individual jar files, each of which can be used in various combinations depending on the specific requirements of your application. These modules include: Contains the Abdera2 Common Code Library, a generic collection of utilities supporting a broad range of functionality including URI Templates, Date/Time handling, extended HTTP Header support, IRI and Language Tags, and much more. The Common Code Library can be used independently of the rest of the Abdera2 code. Contains the generic Abdera2 HTTP Client. Implemented as a thin layer on top of the Apache HttpComponents Client, the Abdera2 Client library provides a client API for working with REST services. Contains the core of the Atom Syndication Format and Atom Publishing Protocol code, including the Feed Object Model API znc Atom-specific extensions to the HTTP Client. Contains the core of the Atom Publishing Protocol Server Framework. Contains the XML Digital Signatures and XML Encryption implementations for the Atom Syndication Format. Contains a range of standard and common extensions to the Atom Syndication Format including Threading, Paging, Licensing, etc Contains the JSON Activity Streams implementation. This module depends directly on the Common and Client modules, but can be used independently of all the Atom Syndication Format and Atom Publishing Protocol code.

To see the list of dependencies required by Abdera2, you can run the following command using Maven (source):

mvn -o dependency:list | grep ":.*:.*:.*" | cut -d] -f2- | sed 's/:[a-z]*$//g' | sort -u

To use Abdera2 within a Maven-based project, simply add the following dependencies to you pom.xml:

Common: org.apache.abdera2 abdera2-common 2.0-SNAPSHOT ]]>

Client: org.apache.abdera2 abdera2-client 2.0-SNAPSHOT ]]>

Atom Core: org.apache.abdera2 abdera2-core 2.0-SNAPSHOT ]]>

Atom Server: org.apache.abdera2 abdera2-server 2.0-SNAPSHOT ]]>

Atom Security: org.apache.abdera2 abdera2-security 2.0-SNAPSHOT ]]>

Atom Extensions: org.apache.abdera2 abdera2-ext 2.0-SNAPSHOT ]]>

Activity Streams: org.apache.abdera2 abdera2-activities 2.0-SNAPSHOT ]]>

Maven will automatically pull in all the necessary dependencies for each of the modules.