A Maven plugin for deploying a p2 update site to an AWS S3 bucket.

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.

Java 1.7+

Maven 3.1.0+

To build the plugin locally, simply run the following:

$ mvn clean install

The aws-p2-maven-plugin is available from Maven Central.

Add the plugin to the build section of the pom.xml:

<plugin>
    <groupId>com.avojak.mojo</groupId>
    <artifactId>aws-p2-maven-plugin</artifactId>
    <version>1.0</version>
    <configuration>
        <bucket>p2.example.com</bucket>
    </configuration>
    <executions>
        <execution>
            <goals>
                <goal>deploy</goal>
            </goals>
        </execution>
    </executions>
</plugin>

The plugin will run automatically during the deploy phase.

Additionally, you may add a pluginGroup entry to the Maven settings file (User: ${user.home}/.m2/settings.xml, Global: ${maven.home}/conf/settings.xml), which will allow the use of aws-p2:* command line goals interactively in all projects:

<pluginGroups>
    <pluginGroup>com.avojak.mojo</pluginGroup>
</pluginGroups>

For example, $ mvn aws-p2:deploy -Daws-p2.bucket=p2.example.com.

The following goals are available:

The following parameters can be set in the configuration:

The AWS p2 Maven Plugin uses the Default Credential Provider Chain for authentication. See Working with AWS Credentials for details on all supported methods of providing credentials.

In order to host a static p2 update site on an S3 bucket, you will need to ensure several bucket settings:

1. In the bucket properties tab, "Static website hosting" must be enabled
2. In the bucket permissions tab, "Public access" to list bucket contents must be enabled

It is up to the consumer to configure the AWS account used for deployments, although we recommend creating an account whose sole responsibility is deploying to this bucket. Only the minimum required permissions should be granted to this user.

If versioning is enabled on the bucket, not all versions are deleted during an overwrite. When a new site is uploaded, only current content is deleted, and delete markers are not touched.

• Maven - Dependency Management
• AWS SDK for Java - Used to interact with AWS S3 buckets
• Travis CI - Continuous Integration and Deployment
• JaCoCo - Code Coverage

We use SemVer for versioning. For the versions available, see the tags on this repository.

For more information on the development, check out my blog post.

This project is licensed under the Apache License, Version 2.0 - see the LICENSE file for details