We have a large non-maven Java project. As well as this, we also have some smaller Maven projects and an Archiva repository.
I would like to use Maven libraries in the non-Maven project for snapshot and 3rd party dependencies.
I set this up - using 'Maven libraries' as dependencies for the modules in the non-Maven project. So far so good. However, there doesn't seem to be a check done for newer versions in Archiva.
For example, if I delete the artifact in my local Maven repository, nothing goes off and downloads it from Archiva (like what would happen if it was a Maven project). I'm guessing (because I haven't been able to test it yet) that if a newer version existed in Archiva then that wouldn't be picked up either.
Is this expected behaviour?
The non-Maven project also uses Ivy (and we were using IvyIDEA plugin in IDEA), but this wasn't working very well for the snapshot dependencies (it was a mistake to use it I think), so that's why I'm looking into using Maven libraries. FYI I disabled all Ivy detection for the Maven library experiment.
So is it possible to use Maven libraries and expect to be able to pick up newer versions? That is, expect it to behave like Maven?