Bump jakarta.mail from 1.6.5 to 2.0.1

Bumps [jakarta.mail](https://github.com/eclipse-ee4j/mail) from 1.6.5 to 2.0.1.
- [Release notes](https://github.com/eclipse-ee4j/mail/releases)
- [Commits](https://github.com/eclipse-ee4j/mail/compare/1.6.5...2.0.1)

Signed-off-by: dependabot[bot] <support@github.com>
1 file changed
tree: 5a76dba92b1982e90edb37e8addcd8b0d8460766
  1. .github/
  2. commons-email2-bom/
  3. commons-email2-core/
  4. commons-email2-distribution/
  5. commons-email2-jakarta/
  6. commons-email2-javax/
  7. src/
  8. .asf.yaml
  9. .gitignore
  10. CODE_OF_CONDUCT.md
  11. CONTRIBUTING.md
  12. LICENSE.txt
  13. NOTICE.txt
  14. pom.xml
  15. README.md
  16. RELEASE-NOTES.txt
  17. SECURITY.md
README.md

Apache Commons Email

Java CI Coverage Status Maven Central Javadocs CodeQL OpenSSF Scorecard

Apache Commons Email provides an API for sending email, simplifying the JavaMail API.

Documentation

More information can be found on the Apache Commons Email homepage. The Javadoc can be browsed. Questions related to the usage of Apache Commons Email should be posted to the user mailing list.

Getting the latest release

You can download source and binaries from our download page.

Alternatively, you can pull it from the central Maven repositories:

<dependency>
  <groupId>org.apache.commons</groupId>
  <artifactId>commons-email</artifactId>
  <version>1.6.0</version>
</dependency>

Building

Building requires a Java JDK and Apache Maven. The required Java version is found in the pom.xml as the maven.compiler.source property.

From a command shell, run mvn without arguments to invoke the default Maven goal to run all tests and checks.

Contributing

We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors. There are some guidelines which will make applying PRs easier for us:

  • No tabs! Please use spaces for indentation.
  • Respect the existing code style for each file.
  • Create minimal diffs - disable on save actions like reformat source code or organize imports. If you feel the source code should be reformatted create a separate PR for this change.
  • Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running mvn.

If you plan to contribute on a regular basis, please consider filing a contributor license agreement. You can learn more about contributing via GitHub in our contribution guidelines.

License

This code is licensed under the Apache License v2.

See the NOTICE.txt file for required notices and attributions.

Donating

You like Apache Commons Email? Then donate back to the ASF to support development.

Additional Resources

Apache Commons Components

Please see the list of components