Hi Jason,
> Easiest way I know of is using Aether directly:
https://github.com/eclipse/aether-demo/blob/master/aether-demo-snippets/src/main/java/org/eclipse/aether/examples/FindAvailableVersions.java
This is predicated on their being intact Maven metadata for that
particular artifact, which is in turn predicated on the deploying system
understanding Maven metadata. Maven obviously does, but other build
systems may not.
The only way to get a definitive list of versions is to use something
that is produced, and validated, on the server side. Something like the
Nexus index. The Maven metadata is reasonably decent and is the only
thing a client can use with a dumb server but can never be absolutely
correct.
so this tip brought me into the right direction and now i have working
result. Thanks for that...
Only for one thing I'm not sure about if this is correct or the right
path...
I'm using the following in my plugin
(https://github.com/khmarbaise/uptodate-maven-plugin/blob/master/src/main/java/com/soebes/maven/plugins/uptodate/AbstractUpToDateMojo.java):
/**
* The project's remote repositories to use for the resolution.
*/
@Parameter( defaultValue = "${project.remoteProjectRepositories}" )
private List<RemoteRepository> remoteRepos;
cause i couldn't find an documented equivalent of it...but it seemed to
be working...I know the docs about evaluation:
http://maven.apache.org/ref/3.1.1/maven-core/apidocs/org/apache/maven/plugin/PluginParameterExpressionEvaluator.html
which gives a reference to the project....so does this include the aboce
remoteProjectRepositories ?
Kind regards
Karl-Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
