[+1] release it

I spot checked the signatures, and they all appear to be valid:
 gpg --verify fulcrum-security-1.1.3-bin.tar.gz.asc fulcrum-security-1.1.3-bin.tar.gz  gpg --verify fulcrum-security-1.1.3-bin.zip.asc fulcrum-security-1.1.3-bin.zip  gpg --verify fulcrum-security-1.1.3-src.zip.asc fulcrum-security-1.1.3-src.zip  gpg --verify fulcrum-security-api-1.1.3.jar.asc fulcrum-security-api-1.1.3.jar  gpg --verify fulcrum-security-memory-1.1.3.jar.asc fulcrum-security-memory-1.1.3.jar

All with the same result:

gpg: Signature made Fri 29 Mar 2019 08:59:18 AM EDT
gpg:                using RSA key 83221A9E13D9F6A39E718DD76EAAE3D2F615E012
gpg: Good signature from "Georg Kallidis (APACHE CODE SIGNING KEY) <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 8322 1A9E 13D9 F6A3 9E71  8DD7 6EAA E3D2 F615 E012

Build environment:

 Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T14:41:47-04:00)
 Maven home: /usr/java/maven
 Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: /usr/java/jdk1.8.0_202/jre
 Default locale: en_US, platform encoding: UTF-8
 OS name: "linux", version: "4.18.0-16-generic", arch: "amd64", family: "unix"


Tag checkout of: fulcrum-security-1.1.3

Parent checkout build results:
  "mvn clean install" ends with BUILD SUCCESS
  "mvn clean site" fails - see below

"mvn clean site" success on following sub-modules:
   security/api
   security/hibernate
   security/memory
   security/dist

 fails only on:
   security/torque

The errors are a result of non-Javadoc compliance based on the
generated code coming from Torque 4.0.  This should be fixed after
we update to Torque 4.1 and bump this to fulcrum-security 2.0.0.

Georg, before we do a site update, maybe there is a way to turn off javadoc
for this one submodule or let it ignore the javadoc errors? I looked briefly, but could not find a way to disable it... I am sure there must be an option somewhere

Thanks!
Jeff



On 3/29/19 9:18 AM, Georg Kallidis wrote:
Hello Turbine devs,

A release candidate for Fulcrum security version 1.1.3 has been prepared.

This release contains the following updates:

  - TurbineAccessControlList interface with generic type bound
  - Fix Torque OM build lifecycle (depends on Torque 4.0)
  - Update some Tests to Junit 5
  - Fix Torque build failures

  Java Dependency updates:

  - Update to commons-lang3
  - Update Fulcrum-yaafi to 1.0.8
  - Update Fulcrum-testcontainer to 1.0.8


Please verify this release candidate carefully and vote.

Tag:
https://svn.apache.org/repos/asf/turbine/fulcrum/tags/fulcrum-security-1.1.3


Artifacts:
https://repository.apache.org/content/repositories/orgapacheturbine-1047/


[ ] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because


Thanks!
Jeff Painter



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to