Jonathan Sinovassin-Naïk created UNOMI-981: ----------------------------------------------
Summary: The package module deploys nothing, so no 3.1.0-SNAPSHOT
distribution has been published since June
Key: UNOMI-981
URL: https://issues.apache.org/jira/browse/UNOMI-981
Project: Apache Unomi
Issue Type: Bug
Reporter: Jonathan Sinovassin-Naïk
The package module deploys nothing, so no 3.1.0-SNAPSHOT distribution has been
published since June
h1. Description
The last published distribution snapshot is
unomi-3.1.0-20260602.094524-27.tar.gz, from 2026-06-02.
Every other module kept publishing: unomi-services is at build 65, from
2026-09-04.
Commit 02ab3c670, from 2026-06-06, added this to package/pom.xml:
{code:java}
<!-- Ensure the dummy jar is NOT deployed -->
<plugin>
<artifactId>maven-deploy-plugin</artifactId>
<configuration>
<skip>true</skip>
</configuration>
</plugin>
{code}
The comment names the dummy jar, and the setting skips the whole module. The
tar.gz and the zip go with it.
The dummy jar carries no classifier, and the module is packaged as a pom. The
jar plugin makes that jar the artifact of the module. Giving it a classifier
keeps it a side artifact, and the blanket skip is then not needed.
Consequence: every change made under package/src/main/resources/etc/ since
2026-06-06 is missing from the published distribution.
One example is the setting v2CompatibilityModeEnabled, added on 2026-06-08 by
UNOMI-904.
A downstream build unpacks the distribution, and ships a
custom.system.properties that carries none of the 3.1 authentication settings.
The documented environment variable then sets nothing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
