Jetty

[Tom Zeller]

> On Aug 28, 2015, at 9:42 AM, Rod Widdowson <rdw at steadingsoftware.com> wrote:
> 
>> I guess it depends on what you mean by “collect”, whether building the
>> distribution or running unit tests. 
> 
> I mean "get the collections of jar and configuration files that represents a Jetty Installation and put it somewhere where the testbed can access it", we need to do this once per jetty version that we want to test against.

>> I think we have agreed that the somewhere we define
>> jetty.version should probably not be the parent-v3 POM, but I have not
>> moved jetty.version out of that POM because of the unit tests that use it.
> 
> My straw man states that it not appear in *any* POM (thus leaving the classpath "clean"), but that then leads to the question of how we collect both the 9.2 and 9.3 versions of Jetty.

If jetty.version does not appear in *any* POM, then we will need to provide it at runtime when running unit tests or hardcode the version in those tests. Shrug, not sure which is better/worse.