<commit_before># ElasticSpring

ElasticSpring is a cloud application framework for the [Amazon Webservice Platform] [AWS]. ElasticSpring enables developers to
use popular Amazon Webservices with the [Spring Framework] [Spring]. With ElasticSpring, developers can re-use their existing
knowledge, code and components built with the Spring Framework programming model and build applications using the
Amazon Webservices. While continuing to use the programming model, developers can take advantage of the scalability
of the service provided by the Amazon cloud platform.


# Checking out and Building

To check out the project and build it from source, do the following:

    git clone https://github.com/aemruli/elasticspring.git
    cd elasticspring
    ./gradlew build

If you encounter out of memory errors during the build, increase available heap and permgen for Gradle:

    GRADLE_OPTS='-XX:MaxPermSize=1024m -Xmx1024m'

To build and install jars into your local Maven cache:

    ./gradlew install

To build api Javadoc (results will be in `build/api`):

    ./gradlew api

To build reference documentation (results will be in `build/reference`):

    ./gradlew reference

# Using IntelliJ IDEA

ElasticSpring development is done with [IntelliJ IDEA] [IntelliJ]. In order to create all [IntelliJ IDEA] [IntelliJ]
 project files, you have to execute the following Gradle task:

 	./gradlew idea

 Then you can open the project through File --> Open... (select the elasticspring.ipr file locate at the project root).
 If for some reason you want to remove the [IntelliJ IDEA] [IntelliJ] project files you can run:

 	./gradlew cleanIdea


# Running integration tests
ElasticSpring contains a test-suite which runs integration tests to ensure compatibility with the Amazon Webservices.
In order to run the integration tests, the build process has to create different resources on the Amazon Webservice
platform (Amazon EC2 instances, Amazon RDS instances, Amazon S3 Buckets, Amazon SQS Queues). Creating these resources
takes time and costs money, because every instance creation is charged with a one hour usage. Therefore ElasticSpring
does not execute the integration tests by default.

In order to execute the integration tests you have to create two configuration files that configure the necessary
parameters to build the environment.

Please create a new file named access.properties. This file must contain two properties named accessKey and secretKey.
These two properties are account/user specific and should never be shared to anyone. Two retrieve these settings you have
to open your account inside the AWS console and retrieve them through the [Security Credentials Page]
[AWS-Security-Credentials].
*Note:* In general we recommend that you use an [Amazon IAM] [Amazon-IAM] user instead of the account itself.

An example file will look like this

	accessKey=<KEY>
	secretKey=<KEY>

Also you have to create another file named mail.properties which will provide the sender and recipient mail address to
test the [Amazon Simple E-Mail Service] [Amazon-SES]. These two addresses must be verified for the Amazon SES Service.

An example file will have the following contents

	senderAddress=<EMAIL>
	recipientAddress=<EMAIL>

After creating both files and storing them outside the project (or inside the project, they are ignored in git)
you have to provide the configuration directory when running the build. Providing these configuration settings will
automatically execute the integration tests.

To build with the integration tests you must execute

	./gradlew build -Dels.config.dir=/Users/foo/config/dir
 	(on windows you will also need a leading slash before the drive letter e.g. /C:/users/foo/config/dir)

The integration test will create an [Amazon Webservices CloudFormation] [Amazon-CloudFormation] stack and execute the
tests. The stack is destroyed after executing the tests (either successful or failed) to ensure that there are no
unnecessary costs.

### Costs of integration tests
The costs for one integration test run should not be more then 0.13 $ (excl. VAT).


# Developing using Amazon Webservices
During development it might be time-consuming to run the integration tests regularly. In order to create a stack only
once, and reuse them for the tests run, you have to create the stack manually using the template found in
/elasticspring-integration-test/src/test/resources. You will need to create the stack with the name
"IntegrationTestStack" to ensure that the integration tests will re-use the stack.

# Getting in touch
ElasticSpring on [Twitter](https://twitter.com/elasticspring)

Individual team members can be found on different social media channels

* <NAME> ([Twitter](http://twitter.com/aemruli) / [LinkedIn](http://de.linkedin.com/in/agimemruli/))
* <NAME> ([Twitter](http://twitter.com/sahlialain) / [LinkedIn](http://ch.linkedin.com/in/asahli))
* <NAME> ([Twitter](http://twitter.com/chrisstettler))

[AWS]: http://aws.amazon.com/
[Spring]: http://www.springsource.org
[IntelliJ]: http://www.jetbrains.com/idea/
[AWS-Security-Credentials]: https://portal.aws.amazon.com/gp/aws/securityCredentials
[Amazon-IAM]: https://aws.amazon.com/iam/
[Amazon-SES]: https://aws.amazon.com/ses/
[Amazon-CloudFormation]: https://aws.amazon.com/de/cloudformation/
[Twitter]: https://www.twitter.com
[LinkedIn]: http://www.linkedin.com<commit_msg>Changed readme to reflect new process to import gradle project<commit_after># ElasticSpring

ElasticSpring is a cloud application framework for the [Amazon Webservice Platform] [AWS]. ElasticSpring enables developers to
use popular Amazon Webservices with the [Spring Framework] [Spring]. With ElasticSpring, developers can re-use their existing
knowledge, code and components built with the Spring Framework programming model and build applications using the
Amazon Webservices. While continuing to use the programming model, developers can take advantage of the scalability
of the service provided by the Amazon cloud platform.


# Checking out and Building

To check out the project and build it from source, do the following:

    git clone https://github.com/aemruli/elasticspring.git
    cd elasticspring
    ./gradlew build

If you encounter out of memory errors during the build, increase available heap and permgen for Gradle:

    GRADLE_OPTS='-XX:MaxPermSize=1024m -Xmx1024m'

To build and install jars into your local Maven cache:

    ./gradlew install

To build api Javadoc (results will be in `build/api`):

    ./gradlew api

To build reference documentation (results will be in `build/reference`):

    ./gradlew reference

# Using IntelliJ IDEA

ElasticSpring development is done with [IntelliJ IDEA] [IntelliJ]. In order to create all [IntelliJ IDEA] [IntelliJ]
 project files, you have to import the file within idea as a gradle project.

*Note:* Please make sure to revert all changes in the .idea config file directory, as the gradle plugin overwrites
the configuration files kept in the scm.

# Running integration tests
ElasticSpring contains a test-suite which runs integration tests to ensure compatibility with the Amazon Webservices.
In order to run the integration tests, the build process has to create different resources on the Amazon Webservice
platform (Amazon EC2 instances, Amazon RDS instances, Amazon S3 Buckets, Amazon SQS Queues). Creating these resources
takes time and costs money, because every instance creation is charged with a one hour usage. Therefore ElasticSpring
does not execute the integration tests by default.

In order to execute the integration tests you have to create two configuration files that configure the necessary
parameters to build the environment.

Please create a new file named access.properties. This file must contain two properties named accessKey and secretKey.
These two properties are account/user specific and should never be shared to anyone. Two retrieve these settings you have
to open your account inside the AWS console and retrieve them through the [Security Credentials Page]
[AWS-Security-Credentials].
*Note:* In general we recommend that you use an [Amazon IAM] [Amazon-IAM] user instead of the account itself.

An example file will look like this

	accessKey=<KEY>
	secretKey=<KEY>

Also you have to create another file named mail.properties which will provide the sender and recipient mail address to
test the [Amazon Simple E-Mail Service] [Amazon-SES]. These two addresses must be verified for the Amazon SES Service.

An example file will have the following contents

	senderAddress=<EMAIL>
	recipientAddress=<EMAIL>

After creating both files and storing them outside the project (or inside the project, they are ignored in git)
you have to provide the configuration directory when running the build. Providing these configuration settings will
automatically execute the integration tests.

To build with the integration tests you must execute

	./gradlew build -Dels.config.dir=/Users/foo/config/dir
 	(on windows you will also need a leading slash before the drive letter e.g. /C:/users/foo/config/dir)

The integration test will create an [Amazon Webservices CloudFormation] [Amazon-CloudFormation] stack and execute the
tests. The stack is destroyed after executing the tests (either successful or failed) to ensure that there are no
unnecessary costs.

### Costs of integration tests
The costs for one integration test run should not be more then 0.13 $ (excl. VAT).


# Developing using Amazon Webservices
During development it might be time-consuming to run the integration tests regularly. In order to create a stack only
once, and reuse them for the tests run, you have to create the stack manually using the template found in
/elasticspring-integration-test/src/test/resources. You will need to create the stack with the name
"IntegrationTestStack" to ensure that the integration tests will re-use the stack.

# Getting in touch
ElasticSpring on [Twitter](https://twitter.com/elasticspring)

Individual team members can be found on different social media channels

* <NAME> ([Twitter](http://twitter.com/aemruli) / [LinkedIn](http://de.linkedin.com/in/agimemruli/))
* <NAME> ([Twitter](http://twitter.com/sahlialain) / [LinkedIn](http://ch.linkedin.com/in/asahli))
* <NAME> ([Twitter](http://twitter.com/chrisstettler))

[AWS]: http://aws.amazon.com/
[Spring]: http://www.springsource.org
[IntelliJ]: http://www.jetbrains.com/idea/
[AWS-Security-Credentials]: https://portal.aws.amazon.com/gp/aws/securityCredentials
[Amazon-IAM]: https://aws.amazon.com/iam/
[Amazon-SES]: https://aws.amazon.com/ses/
[Amazon-CloudFormation]: https://aws.amazon.com/de/cloudformation/
[Twitter]: https://www.twitter.com
[LinkedIn]: http://www.linkedin.com
{'fraction_non_alphanumeric': 0.0685378590078329, 'fraction_numerical': 0.002424468481909735, 'mean_word_length': 4.713905167820991, 'pattern_counts': {'":': 0, '<': 17, '<?xml version=': 0, '>': 18, 'https://': 14, 'lorem ipsum': 0, 'www.': 8, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6354672', 'n_tokens_mistral': 2857, 'n_tokens_neox': 2714, 'n_words': 1355}