Closed ops4j-issues closed 13 years ago
Toni Menzel commented
We should make Pax Runner 1.8 version agnostic. I think unless the framework change their config script layout there is no need to just let pax runner pick any arbitrary felix version.
There are two distinguishing cases:
1. no version specified. In that case the new "default" would something that is today version="LATEST" or just resolve to: mvn:<framework>:<frameworkartifact>:(0.0:] (open version range).
2. if the user specifies a version, just try to resolve that.
There are some more details to be taken care of but should worth the effort doing.
As another task we should have a "genericPlatform" using framework independent launcher api. Though not sure if we can and should make the generated config file stuff agnostic too (is there a standard as well?)
Toni
Dmytro Pishchukhin commented
Toni,
I think, that cases your just mentioned belong to the next major version 2.x, don't they?
Dmytro
Toni Menzel commented
added fix version 1.7.2
Toni Menzel commented
released with 1.7.2
Dmytro Pishchukhin created PAXRUNNER-392
Fixed in: 1.7.2, 1.8.0 Votes: 0, Watches: 0