Zakaria El OrcheandClaude Sonnet 5
5a16bc690c
Lets Pathway (and other consumers) resolve dev.relism:flash from Gitea's Maven registry instead of requiring a local `mvn install`. Every push stamps all modules with a commit-scoped version (2.1.0-<short-sha>) before deploying, since Gitea's registry won't let a build overwrite an existing name+version. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
25 lines
1.0 KiB
XML
25 lines
1.0 KiB
XML
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
|
|
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
|
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
|
|
<!--
|
|
Used only by .gitea/workflows/publish-maven.yml (mvn -s .gitea/maven-settings.xml deploy).
|
|
Not used for local builds. The token is read from the GITEA_TOKEN env var the workflow
|
|
already exports (Gitea Actions' built-in per-job token, scoped to this repo/org — see
|
|
https://docs.gitea.com/usage/packages/maven#configuring-the-package-registry), never
|
|
written to disk.
|
|
-->
|
|
<servers>
|
|
<server>
|
|
<id>gitea</id>
|
|
<configuration>
|
|
<httpHeaders>
|
|
<property>
|
|
<name>Authorization</name>
|
|
<value>token ${env.GITEA_TOKEN}</value>
|
|
</property>
|
|
</httpHeaders>
|
|
</configuration>
|
|
</server>
|
|
</servers>
|
|
</settings>
|