Re: [aether-users] Snapshot version resolution

[Lars Braubach <braubach@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Thank you for the quick reply.

What I actually try to achieve is checking if a newer
snapshot is available than that I am currently running on
and restart the application to let it use the new artifacts.

If it is not possible find out the local snapshot version
how does maven itself know when to perform an
autoupdate from a remote repo for a snapshot?

Or is aether the wrong tool for that?

Best
Lars

Am 17.07.2012 12:19, schrieb Benjamin Bentmann:
> Lars Braubach wrote:
>
> > Now I tried to find out the concrete timestamped version
> > of the artifact using the aether system session and different methods
> > (resolveVersion(), resolveArtifact()) but with no success.
> > I always get version and base version being resolved to "2.1-SNAPSHOT".
> >
> > I have inspected the .m2 local repo and looked into our metadata which
> > looks like below.  So, in the metadata there is the timestamp recorded.
> > [...]
> > <?xml version="1.0" encoding="UTF-8"?>
> > <metadata modelVersion="1.1.0">
> >    <groupId>net.sourceforge.jadex</groupId>
> >    <artifactId>jadex-applications-bdi</artifactId>
> >    <version>2.1-SNAPSHOT</version>
> >    <versioning>
> >      <snapshot>
> >        <localCopy>true</localCopy>
> >      </snapshot>
>
> Artifacts that have been built/installed into a local Maven repository 
> simply have no timestamped version, only remote repos use timestamped 
> snapshots.
>
> Using timestamped snapshots for local artifacts would require to 
> implement your own MetadataGeneratorFactory and maybe VersionResolver.
>
>
> Benjamin
> _______________________________________________
> aether-users mailing list
> aether-users@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/aether-users