Update maven publish

[offtherailz]

Can not publish 1.7

See this task. Probably due to wagon or server setup.

https://github.com/geosolutions-it/http-proxy/actions/runs/28017796337/job/82927714587

[INFO] --- resources:3.4.0:testResources (default-testResources) @ http_proxy ---
[INFO] Copying 3 resources from src/test/resources to target/test-classes
[INFO] 
[INFO] --- compiler:3.5.1:testCompile (default-testCompile) @ http_proxy ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- surefire:2.19.1:test (default-test) @ http_proxy ---
[INFO] Skipping execution of surefire because it has already been run for this configuration
[INFO] 
[INFO] --- war:2.6:war (default-war) @ http_proxy ---
[INFO] Packaging webapp
[INFO] Assembling webapp [http_proxy] in [/home/runner/work/http-proxy/http-proxy/target/http_proxy-1.7-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/runner/work/http-proxy/http-proxy/src/main/webapp]
[INFO] Webapp assembled in [14 msecs]
[INFO] Building war: /home/runner/work/http-proxy/http-proxy/target/http_proxy.war
[INFO] 
[INFO] --- install:2.5.2:install (default-install) @ http_proxy ---
[INFO] Installing /home/runner/work/http-proxy/http-proxy/target/http_proxy.war to /home/runner/.m2/repository/proxy/http_proxy/1.7-SNAPSHOT/http_proxy-1.7-SNAPSHOT.war
[INFO] Installing /home/runner/work/http-proxy/http-proxy/pom.xml to /home/runner/.m2/repository/proxy/http_proxy/1.7-SNAPSHOT/http_proxy-1.7-SNAPSHOT.pom
[INFO] 
[INFO] --- install:2.5.2:install-file (default) @ http_proxy ---
[INFO] Installing /home/runner/work/http-proxy/http-proxy/target/http_proxy-1.7-SNAPSHOT.jar to /home/runner/.m2/repository/proxy/http_proxy/1.7-SNAPSHOT/http_proxy-1.7-SNAPSHOT.jar
[INFO] 
[INFO] --- deploy:2.8.2:deploy (default-deploy) @ http_proxy ---
[INFO] Downloading from geosolutions: sftp://***.geo-solutions.it/proxy/http_proxy/1.7-SNAPSHOT/***-metadata.xml
Warning:  Could not transfer metadata proxy:http_proxy:1.7-SNAPSHOT/***-metadata.xml from/to geosolutions (sftp://***.geo-solutions.it): Error occurred while downloading 'proxy/http_proxy/1.7-SNAPSHOT/***-metadata.xml' from the remote repository:Repository[geosolutions|sftp://***.geo-solutions.it]: no such file
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  21.924 s
[INFO] Finished at: 2026-06-23T10:01:45Z
[INFO] ------------------------------------------------------------------------
Error:  Failed to execute goal org.apache.***.plugins:***-deploy-plugin:2.8.2:deploy (default-deploy) on project http_proxy: Failed to retrieve remote metadata proxy:http_proxy:1.7-SNAPSHOT/***-metadata.xml: Could not transfer metadata proxy:http_proxy:1.7-SNAPSHOT/***-metadata.xml from/to geosolutions (sftp://***.geo-solutions.it): Error occurred while downloading 'proxy/http_proxy/1.7-SNAPSHOT/***-metadata.xml' from the remote repository:Repository[geosolutions|sftp://***.geo-solutions.it]: no such file -> [Help 1]
Error:  
Error:  To see the full stack trace of the errors, re-run Maven with the -e switch.
Error:  Re-run Maven using the -X switch to enable full debug logging.
Error:  
Error:  For more information about the errors and possible solutions, please read the following articles:
Error:  [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Error: Process completed with exit code 1.

[tdipisa]

This is blocking geosolutions-it/MapStore2#12535

[mahesh-wor]

Summary

Publishing proxy:http_proxy:1.7-SNAPSHOT to the GeoSolutions Maven repository over SFTP failed during Maven deploy because the version-level snapshot metadata file did not exist yet:
proxy/http_proxy/1.7-SNAPSHOT/maven-metadata.xml

Deploy failed with

[INFO] --- deploy:2.8.2:deploy (default-deploy) @ http_proxy ---
[INFO] Downloading from geosolutions: sftp://***.geo-solutions.it/proxy/http_proxy/1.7-SNAPSHOT/***-metadata.xml
Warning: Could not transfer metadata proxy:http_proxy:1.7-SNAPSHOT/***-metadata.xml from/to geosolutions (sftp://***.geo-solutions.it): no such file
[INFO] BUILD FAILURE

Maven seems to treat the missing metadata download as fatal.
Failed to retrieve remote metadata proxy:http_proxy:1.7-SNAPSHOT/maven-metadata.xml

So the failure is strictly because this is the version 1.7 didn't exist earlier in the maven repository. It's still unknown why the maven-deploy-plugin cannot create new dir and respective maven-metadata.xml.

Tests Done

I tested if the issue is due to old maven-deploy-plugin 2.8.2 published in 2014 with the recent one 3.1.4.
Tested with

<artifactId>maven-deploy-plugin</artifactId>
- <version>2.8.2</version>
+ <version>3.1.4</version>

But it didn't work, action status here.

Fix Performed

I manually created the directory and bootstraped 1.7-SNAPSHOT/maven-metadata.xml with

mkdir -p ~/data-volume/artifacts/proxy/http_proxy/1.7-SNAPSHOT

cat > ~/data-volume/artifacts/proxy/http_proxy/1.7-SNAPSHOT/maven-metadata.xml <<'EOF'
<?xml version="1.0" encoding="UTF-8"?>
<metadata>
  <groupId>proxy</groupId>
  <artifactId>http_proxy</artifactId>
  <version>1.7-SNAPSHOT</version>
  <versioning>
    <snapshot>
      <buildNumber>0</buildNumber>
    </snapshot>
    <lastUpdated>20260623113055</lastUpdated>
  </versioning>
</metadata>
EOF

Later the build was rerun here, and it succeeded.
The maven-metadata.xml was created with proper version and timestamp by maven publish job.
https://maven.geo-solutions.it/proxy/http_proxy/1.7-SNAPSHOT/

@tdipisa it is still unknown why a missing dir/maven-metadata.xml is fatal and maven-deploy-plugin doesn't handle it. But it will not fail as the needed dirs/files are now present. Need to investigate further so it's not an issue in next version updates.
cc: @offtherailz

[offtherailz]

Given that we may have different configurations in the near future (one only repo for geostore+mapstore+proxy) or different solutions for deploy, if we unlocked issues on 1.7 I'd leave this issue in stale as very low proprity.

[mahesh-wor]

The issue seems to be on wagon-ssh + ssh implementation, where it fails to determine whether a missing file is ResourceDoesNotExistException or TransferFailedException.

Normally that should have been considered via the sftp response code SSH_FX_NO_SUCH_FILE = 2, but it seem to take in the response message to determine this.

So broke due to brittle wagon-ssh classification of the exception that's determined via e.toString().trim().endsWith("No such file").
No such file vs no such file message response text just broke it.

Sadly it's out of our scope, i think it's time to consider a different solution for deploy like you suggested later @offtherailz , or think of nexus/artifactory direction.

Keeping it low-prio and moving to inbox for later.