JarCastingGreenMail
GreenMail is an open source, intuitive and easy-to-use test suite of email servers for testing purposes. Supports SMTP, POP3, IMAP with SSL socket support, and can be run either embedded in a junit test, as a standalone Java application or as a docker container. GreenMail is the first and only library that offers a test framework for both receiving and retrieving emails from Java.
Go to the project site for details:
The GreenMail project welcomes any contribution, so go ahead and fork/open a pull request! See the guidelines below.
Note: GreenMail recently moved to Github and was previously hosted on SF.
Development 
-
Build GreenMail from source
mvn clean install -PdockerMake sure you got Maven 3.6 or higher, and run a JDK 8 or newer. If you want to skip building the docker image, leave out the
-Pdockerprofile option.If you want to skip the long running tests, use the Maven option
-DskipITs. -
Build the Maven site (and the optional example report)
mvn site -Psite -
Build and deploy a release
For rolling a release including version increment and release upload, do
mvn clean release:prepare -Prelease,release-ossrh,docker,docker-tag-latestmvn release:perform -Prelease,release-ossrh,docker,docker-tag-latestFor a tagged release and deployment to Sonatype OpenSource Repository Hosting and later syncing to Maven Central, do
mvn clean deploy -Prelease,release-ossrh,docker,docker-tag-latestNote: Do only use docker-tag-latest profile if you really want the tag latest, e.g. for newest release of highest version.
-
Build and deploy a snapshot
For a Maven Snapshot deployment to Sonatype, do
mvn clean deploy -Prelease-ossrh,docker -
Check Sonar report
Roadmap
- 1.6 (current)
- Bugfix / maintenance
- 1.7
- Deprecations (no GreenMailRule in greenmail-core, ...)
- 2.x
- JakartaMail 2.x
Contribution guidelines
We really appreciate your contribution! To make it easier for integrating your contribution, have a look at the following guidelines.
Be concise
Try to keep your changes focused. Please avoid (major) refactorings and avoid re-formatting existing code. A good check is looking at the diff of the your pull requrest. Also, please refer to the open issue you're fixing by including a reference in your commit message.
Code formatter
Please set your code formatter to use 4 spaces for indentation of Java files (not tabs) and to two spaces for xml files (like the pom.xml). As a general best practise, your contribution should adhere to existing code style.
Bill of Materials
We have the pom.xml in the root where we set the versions of all dependencies to keep them consistent among subprojects. Please do not add any version tags into the child pom.xml files.
Please also do not introduce new dependencies as we try to keep these to a minimum. If you think you require a new dependencies or dependency update, discuss this up front with committers.
Starting your pull request
The best strategy for opening a pull request after a fork is to add the this repository as the "upstream" to your .git/config such as:
[remote "upstream"]
url = https://github.com/greenmail-mail-test/greenmail.git
fetch = +refs/heads/*:refs/remotes/upstream/*
Then you fetch "upstream" and create a new branch at upstream/master (name it issue-XXX or something like that). Now you can add commits on that branch and then create a pull request for that branch (after pushing it to your github). That way commits are isolated for one feature.
Tests for your pull request
Please also create a test for every feature you add. We know that currently there aren't many tests but in the medium term we want to increase test coverage.
Misc
Many thanks to JProfiler and Jetbrains for supporting this project with free OSS licenses