[jira] [Commented] (SYNCOPE-1726) WA does not always get configuration from Core on startup
[ https://issues.apache.org/jira/browse/SYNCOPE-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17680475#comment-17680475 ] ASF subversion and git services commented on SYNCOPE-1726: -- Commit cb7cfa27e97e38178a608621671476e063272981 in syncope's branch refs/heads/3_0_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=cb7cfa27e9 ] [SYNCOPE-1726] Ensuring Core and calling WA instance are both available in Keymaster before refreshing > WA does not always get configuration from Core on startup > - > > Key: SYNCOPE-1726 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1726 > Project: Syncope > Issue Type: Bug > Components: wa >Affects Versions: 3.0.1 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.2, 4.0.0 > > > Sometimes it happens, especially when using Self Keymaster and WA and Core > are deployed together within the same JavaEE container instance, that all > seems to start successfully yet WA shows no configuration from Core. > In such cases, pushing the configuration resolves the situation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1726) WA does not always get configuration from Core on startup
Francesco Chicchiriccò created SYNCOPE-1726: --- Summary: WA does not always get configuration from Core on startup Key: SYNCOPE-1726 URL: https://issues.apache.org/jira/browse/SYNCOPE-1726 Project: Syncope Issue Type: Bug Components: wa Affects Versions: 3.0.1 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 3.0.2, 4.0.0 Sometimes it happens, especially when using Self Keymaster and WA and Core are deployed together within the same JavaEE container instance, that all seems to start successfully yet WA shows no configuration from Core. In such cases, pushing the configuration resolves the situation. -- This message was sent by Atlassian Jira (v8.20.10#820010)
JDK 20 Rampdown Phase 2 & JMX Heads-up
Hi, First off, on behalf of Oracle’s Java Team, I’d like to wish you a happy and prosperous new year! In 2023, two Java releases will be made available: JDK 20 (March) & JDK 21 (September). JDK 20 [1] has entered Rampdown Phase Two (RDP2) [2], its initial Release Candidate is planned for February 9. Given that and to be better prepared for the future, it makes sense to begin testing your project(s) using JDK 21 early-access (EA) builds. Your feedback allows us to evaluate and address issues you find while testing EA builds. [1] https://jdk.java.net/20/ [2] https://mail.openjdk.org/pipermail/jdk-dev/2023-January/007308.html [3] https://jdk.java.net/21/ ## Heads-up - JDK 21: JMX Subject Delegation & Fine-grained Security Deprecation JMX has some features that rely on Security Manager APIs which are deprecated for removal (see JEP 411 [4]). These features are "Subject Delegation" and "Fine-grained Security", which both seem to be generally unused, and would require significant investment to implement without touching the deprecated APIs. As a consequence, "Subject Delegation" is being proposed for deprecation in JDK 21 [5]. Fine-grained Security is also being considered for deprecation at the same time. This feature [6] has allowed configuration of a security policy to restrict or permit access to specific MBean actions. It is expected that this feature is generally unused, possibly because there is simply no demand for such detailed control, and that it is too complex to create and maintain the policies. [4] https://openjdk.org/jeps/411 [5] https://bugs.openjdk.org/browse/JDK-8298966 [6] https://docs.oracle.com/en/java/javase/19/jmx/fine-grained-security-example.html ## JDK 20 Early-Access builds The latest early-access builds of JDK 20 (builds 32) are available [7], and are provided under the GNU General Public License v2, with the Classpath Exception. The Release Notes are available here [8]. [7] https://openjdk.org/projects/jdk/20/ [8] https://jdk.java.net/20/release-notes ### JEPs integrated into JDK 20: - JEP 429: Scoped Values (Incubator) - JEP 432: Record Patterns (2nd Preview) - JEP 433: Pattern Matching for switch (4th Preview) - JEP 434: Foreign Function & Memory API (2nd Preview) - JEP 436: Virtual Threads (2nd Preview) - JEP 437: Structured Concurrency (2nd Incubator) ### Changes in recent JDK 20 builds that may be of interest: - JDK-8298525: javadoc crashes with "UnsupportedOperationException: Not yet implemented" in SeeTaglet.inherit [Reported by Apache Ant] - JDK-8298893: Rename option UsePolyIntrinsics to UsePoly1305Intrinsics - JDK-8287411: Enhance DTLS Performance - JDK-8293554: Enhanced DH Key Exchanges ## JDK 21 Early-Access builds The latest early-access builds of JDK 21 (builds 6) are available [9], and are provided under the GNU General Public License v2, with the Classpath Exception. The related EA API Javadoc is also available [10]. [9] https://jdk.java.net/21/ [10] https://download.java.net/java/early_access/jdk21/docs/api/ ### Changes in recent JDK 21 builds that may be of interest: - JDK-8297295: Remove ThreadGroup.allowThreadSuspension - JDK-8287411: Enhance DTLS performance - JDK-8233269: Improve handling of JAVA_ARGS - JDK-8297933: Compiler should only use verified interface types for optimization - JDK-8298381: Improve handling of session tickets for multiple SSLContexts - JDK-8299501: Usage of constructors of primitive wrapper classes should be avoided in java.util API docs - JDK-8299475: Enhance SocketException by cause where it is missing in net and nio area - JDK-8299544: Improve performance of CRC32C intrinsics (non-AVX-512) for small inputs - JDK-8299576: Reimplement java.io.Bits using VarHandle access - JDK-8278326: Socket close is not thread safe and other cleanup - JDK-8299673: Simplify object pinning interactions with string deduplication ## JavaFX 20 & 21 Early-Access Builds These are early-access builds of the JavaFX Runtime, built from openjdk/jfx [11]. Those EA builds are intended to allow JavaFX application developers to build and test their applications with JavaFX 20 on JDK 20. The latest EA builds (JavaFX 20 EA b16 2023/1/14) are now available [12] and are provided under the GNU General Public License, version 2, with the Classpath Exception. Please note that initial JavaFX 21 early-access builds (JavaFX 21 b1 2023/1/19) are now available [13] as well. Feedback should be reported to the openjfx-dev mailing list [14]. [11] https://github.com/openjdk/jfx [12] https://jdk.java.net/javafx20/ [13] https://jdk.java.net/javafx21/ [14] http://mail.openjdk.org/mailman/listinfo/openjfx-dev ## Topics of Interest: - On Markdown in (Java) documentation comments https://mail.openjdk.org/pipermail/javadoc-dev/2023-January/005563.html - Lifetimes in the Foreign Function & Memory API https://cr.openjdk.java.net/~mcimadamore/panama/why_lifetimes.html - Java's Plans for 2023 - Inside Java
[jira] [Resolved] (SYNCOPE-1723) remove some non-reproducible bits
[ https://issues.apache.org/jira/browse/SYNCOPE-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1723. - Resolution: Fixed > remove some non-reproducible bits > - > > Key: SYNCOPE-1723 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1723 > Project: Syncope > Issue Type: Improvement >Affects Versions: 3.0.0, 3.0.1 >Reporter: Herve Boutemy >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.2, 4.0.0 > > > Reproducible Builds issues found when rebuilding 3.0.0 release: > - non-reproducible content in git.properties > - absolute path of the builder inserted in properties files > see > https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/syncope/README.md > and more precisely > https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/syncope/syncope-3.0.0.diffoscope > Also relevant: why reproducible build matters: > https://reproducible-builds.org/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SYNCOPE-1723) remove some non-reproducible bits
[ https://issues.apache.org/jira/browse/SYNCOPE-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17680174#comment-17680174 ] ASF subversion and git services commented on SYNCOPE-1723: -- Commit 7388f21987e3cc6ade291691a2ced6e6fa292cd4 in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=7388f21987 ] [SYNCOPE-1723] Removing static paths from generated artifacts (#405) (#406) > remove some non-reproducible bits > - > > Key: SYNCOPE-1723 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1723 > Project: Syncope > Issue Type: Improvement >Affects Versions: 3.0.0, 3.0.1 >Reporter: Herve Boutemy >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.2, 4.0.0 > > > Reproducible Builds issues found when rebuilding 3.0.0 release: > - non-reproducible content in git.properties > - absolute path of the builder inserted in properties files > see > https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/syncope/README.md > and more precisely > https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/syncope/syncope-3.0.0.diffoscope > Also relevant: why reproducible build matters: > https://reproducible-builds.org/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [syncope] ilgrosso merged pull request #406: [SYNCOPE-1723] Removing static paths from generated artifacts (#405)
ilgrosso merged PR #406: URL: https://github.com/apache/syncope/pull/406 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SYNCOPE-1723) remove some non-reproducible bits
[ https://issues.apache.org/jira/browse/SYNCOPE-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17680152#comment-17680152 ] ASF subversion and git services commented on SYNCOPE-1723: -- Commit 1dbde5e1aae6598d4ca63b12dddc9e1a084ad552 in syncope's branch refs/heads/3_0_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=1dbde5e1aa ] [SYNCOPE-1723] Removing static paths from generated artifacts (#405) > remove some non-reproducible bits > - > > Key: SYNCOPE-1723 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1723 > Project: Syncope > Issue Type: Improvement >Affects Versions: 3.0.0, 3.0.1 >Reporter: Herve Boutemy >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.2, 4.0.0 > > > Reproducible Builds issues found when rebuilding 3.0.0 release: > - non-reproducible content in git.properties > - absolute path of the builder inserted in properties files > see > https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/syncope/README.md > and more precisely > https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/syncope/syncope-3.0.0.diffoscope > Also relevant: why reproducible build matters: > https://reproducible-builds.org/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [syncope] ilgrosso merged pull request #405: [SYNCOPE-1723] Removing static paths from generated artifacts
ilgrosso merged PR #405: URL: https://github.com/apache/syncope/pull/405 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (SYNCOPE-1723) remove some non-reproducible bits
[ https://issues.apache.org/jira/browse/SYNCOPE-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1723: Description: Reproducible Builds issues found when rebuilding 3.0.0 release: - non-reproducible content in git.properties - absolute path of the builder inserted in properties files see https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/syncope/README.md and more precisely https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/syncope/syncope-3.0.0.diffoscope Also relevant: why reproducible build matters: https://reproducible-builds.org/ was: Reproducible Builds issues found when rebuilding 3.0.0 release: - non-reproducible content in git.properties - absolute path of the builder inserted in properties files see https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/syncope/README.md and more precisely https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/syncope/syncope-3.0.0.diffoscope > remove some non-reproducible bits > - > > Key: SYNCOPE-1723 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1723 > Project: Syncope > Issue Type: Improvement >Affects Versions: 3.0.0, 3.0.1 >Reporter: Herve Boutemy >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 3.0.2, 4.0.0 > > > Reproducible Builds issues found when rebuilding 3.0.0 release: > - non-reproducible content in git.properties > - absolute path of the builder inserted in properties files > see > https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/syncope/README.md > and more precisely > https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/syncope/syncope-3.0.0.diffoscope > Also relevant: why reproducible build matters: > https://reproducible-builds.org/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[WARNING] Reproducible Builds: breaking changes ahead
Hi all, as reported by SYNCOPE-1723 [1], our releases up to 3.0.1 are not compliant with reproducible builds. You can read more details from the report [2]. With help from Hervé Boutemy we have prepared some changes [3] that should solve such an issue but will affect the way people is ordinarily building their Syncope-based Maven projects. Up to 3.0.1, in fact, the typical build command is the one reported by [4] e.g. mvn clean verify \ -Dconf.directory=/opt/syncope/conf \ -Dbundles.directory=/opt/syncope/bundles \ -Dlog.directory=/opt/syncope/log Once [3] will be merged, instead, this command will become a bare mvn clean verify but with need to specify the following system properties, either if run as a standalone application or deployed within a JavaEE container: * -Dsyncope.conf.dir=/opt/syncope/conf * -Dsyncope.connid.location=file:/opt/syncope/bundles * -Dsyncope.log.dir=/opt/syncope/log As you could see from [3], standalone, archetype and docker images were changed altogether to work in this way; docs were updated as well. Such a change is planned for next release 3.0.2; naturally, we will also need to include a proper message in its release notes. Regards. [1] https://issues.apache.org/jira/browse/SYNCOPE-1723 [2] https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/syncope/syncope-3.0.0.diffoscope [3] https://github.com/apache/syncope/pull/405 [4] https://syncope.apache.org/docs/3.0/reference-guide.html#customization -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
