pax runner reads .m2/settings.xml but doesn't respect snapshot value [PAXCONSTRUCT-125]

[ops4j-issues]

Anders Storsveen created PAXCONSTRUCT-125

When pax runner is ran without needed packages in local repo, but correct repo in settings.xml it refuses to load snapshots.

<repositories>
<repository>
<id>bjarne</id>
<url>http://bjarne.pats.no:8081/artifactory/repo</url>
<snapshots>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
</snapshots>
<releases>
<enabled>true</enabled>
</releases>
</repository>
</repositories>

when running it it gives:

-> Collecting versions from repository http://bjarne.pats.no:8081/artifactory/repo/,releases=true,snapshots=false
-> Skipping repository http://bjarne.pats.no:8081/artifactory/repo/,releases=true,snapshots=false, reason: Snapshots not enabled

In pax:provision this problem is even worse, since it refuses to accept even the "--repositories=+http://bjarne.pats.no:8081/artifactory/repo@snapshots" from the runner.args file. This works in pax-runner....

---

Fixed in: 1.5 Votes: 0, Watches: 0

[ops4j-issues]

Alin Dreghiciu commented

This has to be a Pax Construct problem as there are specific tests about this in pax runner and also tested manually right now. Snapshots are read correctly.
But in case of pax construct the plugin overrides all repositories using --repositories (without a starting +) but pax runner does not honor the snapshots setting.

[ops4j-issues]

Stuart McCulloch commented

This has already been fixed in trunk (I think sometime last year) - you'll need to use the 1.5-SNAPSHOT of the pax plugin, or build it from trunk.

[ops4j-issues]

Anders Storsveen commented

Well, when using pax-runner with this settings-file, I shouldn't get:

-> Collecting versions from repository http://bjarne.pats.no:8081/artifactory/repo/,releases=true,snapshots=false
-> Skipping repository http://bjarne.pats.no:8081/artifactory/repo/,releases=true,snapshots=false, reason: Snapshots not enabled

This is with 1.2.0.