slider-50; changing path for published configs

2014-05-13 Thread Steve Loughran
I'm looking to check in a patch that updates the path for configurations from /xml /properties & c to .xml, .properties .json - and so give more intuitive URLs for generated configurations https://issues.apache.org/jira/browse/SLIDER-50 Is this going to break anyone's tests? -steve -- CONFIDEN

Re: slider-50; changing path for published configs

2014-05-13 Thread Jon Maron
Probably a good idea in light of slider-51. Not sure how jersey would differentiate between ../yarn-site/xml and ../yarn-site/yarn.some.property (or a property named “xml” in the yarn-site file - bad example but you get the idea) — Jon On May 13, 2014, at 2:32 PM, Steve Loughran wrote: > I'm

Re: slider-50; changing path for published configs

2014-05-14 Thread Steve Loughran
it does work -JAX-RS even lets you specify more complex URI patterns as full regular expressions http://docs.oracle.com/cd/E19798-01/821-1841/ginpw/ even without playing with regexps, {name}.{id} does get split up when name does not contain "." On 13 May 2014 22:40, Jon Maron wrote: > Probab

Re: slider-50; changing path for published configs

2014-05-14 Thread Jon Maron
On May 14, 2014, at 5:42 AM, Steve Loughran wrote: > it does work -JAX-RS even lets you specify more complex URI patterns as > full regular expressions > > http://docs.oracle.com/cd/E19798-01/821-1841/ginpw/ > > even without playing with regexps, {name}.{id} does get split up when name > does

Re: slider-50; changing path for published configs

2014-05-14 Thread Steve Loughran
yes, jax-rs patterns always go for the ^/ exclusion. On 14 May 2014 13:10, Jon Maron wrote: > > On May 14, 2014, at 5:42 AM, Steve Loughran > wrote: > > > it does work -JAX-RS even lets you specify more complex URI patterns as > > full regular expressions > > > > http://docs.oracle.com/cd/E197