Re: Releasing with lazy consensus

The commons project often releases their parent pom with lazy consensus, for example: https://lists.apache.org/thread/34onls4fw189smx5gjznkk8z80t3j6lc Am Freitag, dem 01.09.2023 um 08:52 +0200 schrieb Volkan Yazıcı: > Is such a thing possible? It is pretty common that many Java projects > have > m

Releasing with lazy consensus

Is such a thing possible? It is pretty common that many Java projects have multiple modules having their own release cycles. Some of these modules are miscellaneous "utilities" to support the rest of the code base. Common examples I can think of are - BOM project covering a dozen other projects

[jira] [Created] (COMDEV-534) 3rd party downloads not allowed by privacy policy

Sebb created COMDEV-534: --- Summary: 3rd party downloads not allowed by privacy policy Key: COMDEV-534 URL: https://issues.apache.org/jira/browse/COMDEV-534 Project: Community Development Issue Type: Bug