this PomRepositoryTest. testGetViaBSNAndGAV() will fail, which we try to fix in the next commit.

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

1st draft, base for discussion.
I hooked into the indexing of BridgeRepository because commons-cli:commons-cli:1.2 (commons-cli-1.2.jar) is indexed as commons-cli:commons-cli:1.2.0 by bridge repo (notice 1.2 vs. 1.2.0). To satisfy the existing testcase of MavenBndRepo this was the only place where I could get the version as 3 digit semver. To be discussed if it really should be that way

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

This reverts commit 3e82952.

Revert "pass test for GAV"

This reverts commit dabeb36.

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

* based on Peter's suggestion. Since BndPomRepository.archives and PomRepository.archives were both null when using a pom.xml (instead of revisions) I populated them in PomRepository.save(). If there is another / better way, we can change that

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

After testing the initial problem it turned out the ${repo;gav;latest} also runs through repo.versions(gav) so we have to support it too

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

fixes the testcase from previous commit and solves the initial reported issue with (${repo;gav;latest} not working with BndPomRepo)

Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>