More details are here: beanstalk.jcabi.com

The plugin automates deployment of Java WAR applications to AWS Elastic Beanstalk. The plugin is designed with a minimalistic approach, so that you don't need to provide a lot of configuration options. Instead, there are a few conventions:

• CNAME of a "primary" environment is always the same as the application name

• Environments are configured only by saved configuration templates

• Deployment is done either by CNAME swap or version update

• An application always contains only one "primary" environment.

Details are explained in usage documentation, but in short it works like this:

<project>
  <build>
    <plugins>
      <plugin>
        <groupId>com.jcabi</groupId>
        <artifactId>jcabi-beanstalk-maven-plugin</artifactId>
        <configuration>
          <name>example</name>
          <bucket>webapps.example.com</bucket>
          <key>${project.artifactId}-${project.version}.war</key>
          <template>example</template>
        </configuration>
        <executions>
          <execution>
            <goals>
              <goal>deploy</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
</project>

Questions?

If you have any questions about the framework, or something doesn't work as expected, please submit an issue here.

How to contribute?

Fork the repository, make changes, submit a pull request. We promise to review your changes same day and apply to the master branch, if they look correct.

Please run Maven build before submitting a pull request:

$ mvn clean install -Pqulice