Google Git
Sign in
apache / incubator-retired-tamaya-sandbox / bf99f3fb60b403d3e980678838519b82cb3acbae
commitbf99f3fb60b403d3e980678838519b82cb3acbae[log] [tgz]
authorP. Ottlinger <ottlinger@users.noreply.github.com>Mon Feb 25 12:38:49 2019 +0100
committerGitHub <noreply@github.com>Mon Feb 25 12:38:49 2019 +0100
tree901e7765767a46647bbe3a45f19ad1e982ece879
parente212349b720a97b4add9afbc321a9be7ae4ab6ab [diff]
[Security] Do not use http to transfer artifacts

Following a mail thread via security team: Fixes:
CWE-829: Inclusion of Functionality from Untrusted Control Sphere
CWE-494: Download of Code Without Integrity Check
1 file changed
tree: 901e7765767a46647bbe3a45f19ad1e982ece879
  1. apache-commons/
  2. buildtools/
  3. camel/
  4. configjsr/
  5. configured-sysprops/
  6. documentation/
  7. hjson/
  8. jodatime/
  9. kubernetes/
  10. management/
  11. metamodel/
  12. propertysources/
  13. remote/
  14. server/
  15. ui/
  16. uom/
  17. usagetracker/
  18. validation/
  19. vertx/
  20. .gitignore
  21. .travis.yml
  22. LICENSE
  23. NOTICE
  24. pom.xml
  25. README.md
README.md

Apache Tamaya (incubating) Sandbox

This is the sandbox of Apache Tamaya. The sandbox contains additional modules (extensions) of Apache Tamaya (incubating) which are not mature enough to be part of Apache Tamaya itself or the official extensions of Apache Tamaya.

Rules for sandbox modules

  • All modules must be independent of each other.
  • A module can be promoted by the PMC of Tamaya to be part of the official Tamaya extensions package if it is mature enough.
  • A sandbox module should have it's own build chain in Tamaya's Jenkins view

Building Apache Tamaya Sandbox

The Apache Tamaya project is built with Maven 3 and Java 8, so you need JDK >=1.8 and a reasonable version of maven installed on your computer.

Then you can build Tamaya Sandbox via:

$ export MAVEN_OPTS="-Xmx512m -XX:PermGenSpace=200m"
$ mvn

Travis / CI

Apart from integration into ASF CI there's a travis build:

Build Status