This is an automated email from the ASF dual-hosted git repository.

jsinovassin pushed a commit to branch UNOMI-package-deploy-fix
in repository https://gitbox.apache.org/repos/asf/unomi.git

commit b1b8c0c0a5594ebfabcbcaf85963b1e20e14134c
Author: jsinovassin <[email protected]>
AuthorDate: Tue Sep 15 15:44:49 2026 +0200

    UNOMI-981: deploy the distribution again
    
    The last published distribution snapshot is 
unomi-3.1.0-20260602.094524-27.tar.gz,
    from 2026-06-02, while unomi-services is at build 65 from 2026-09-04. Commit
    02ab3c670 added a maven-deploy-plugin skip to package/pom.xml on 2026-06-06,
    under the comment "Ensure the dummy jar is NOT deployed". The setting skips 
the
    whole module, so the tar.gz and the zip stopped being published with the 
jar.
    
    The dummy jar carries no classifier, and this module is packaged as a pom, 
so the
    jar plugin makes that jar the artifact of the module. Give the jar the 
classifier
    buildcache, which keeps it a side artifact, and drop the blanket skip.
    
    Verified with mvn deploy against a local repository: the module now 
deposits its
    pom, unomi-3.1.0-SNAPSHOT.tar.gz, unomi-3.1.0-SNAPSHOT.zip, and the dummy 
jar
    under its classifier.
    
    Every change made under package/src/main/resources/etc/ since 2026-06-06 was
    missing from the published distribution, which is how a downstream build 
that
    unpacks it, such as Jahia jCustomer, shipped a custom.system.properties 
with none
    of the 3.1 authentication settings.
---
 package/pom.xml | 13 ++++---------
 1 file changed, 4 insertions(+), 9 deletions(-)

diff --git a/package/pom.xml b/package/pom.xml
index 7fd7b4d41..0c9b57b68 100644
--- a/package/pom.xml
+++ b/package/pom.xml
@@ -414,6 +414,10 @@
                     <goal>jar</goal>
                 </goals>
                 <configuration>
+                    <!-- A classifier keeps this jar a side artifact. Without 
one, the jar plugin makes it
+                         the artifact of this pom-packaged module, which is 
what the blanket deploy skip
+                         below was added to hide, and that skip took the 
distribution with it. -->
+                    <classifier>buildcache</classifier>
                     <archive>
                     <manifest>
                         
<addDefaultImplementationEntries>true</addDefaultImplementationEntries>
@@ -424,15 +428,6 @@
             </executions>
             </plugin>
 
-            <!-- Ensure the dummy jar is NOT deployed -->
-            <plugin>
-            <groupId>org.apache.maven.plugins</groupId>
-            <artifactId>maven-deploy-plugin</artifactId>
-            <configuration>
-                <skip>true</skip>
-            </configuration>
-            </plugin>
-
         </plugins>
     </build>
 

Reply via email to