If you want Maven to be able to find the artifacts in the staging repository during
its build processing,
follow the next instructions, and then add this additional parameter to your "mvn"
commands: -Pstaged-release
.
This is sometimes needed to test new build tooling,
for example. The test would be done by (temporarily) updating some code to depend
on the new version, and then trying to build it. In this case, with the
-Pstaged-release
added, Maven would be able to find the staged
artifacts.
To enable Maven to find artifacts in the staging repository location:
- Update your Maven "settings.xml" file
located in the directory containing your local Maven repository;
in Windows, this is c:\Documents and Settings\<your-userid>\.m2\settings.xml.
The idea is to add
a repository spec called "staged-release" that points to the staging repository
of interest. This
changes for each staged release - the right url will be provided in the [VOTE] email).
Here's a sample settings file, with just this profile element in it:
<settings xmlns="https://maven.apache.org/POM/4.0.0"
xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="https://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/settings-1.0.0.xsd">
<profiles>
<profile>
<id>staged-release</id>
<repositories>
<repository>
<id>staged-release</id>
<url>https://repository.apache.org/content/repositories/orgapacheuima-xxx/</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>staged-release</id>
<url>https://repository.apache.org/content/repositories/orgapacheuima-xxx/</url>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
</settings>
Note: The url element above is just a sample;
each release will have its own unique staging repository name,
which is provided in the [VOTE] email.
Replace the .../orgapacheuima-xxxxxx with the correct url.