Hi,
based on the discussions in the "move o.a.s.xss.JsonUtil into a
separate package" and the "Versioning of o.a.s.xss" threads I would
like to get consensus on the following way forward:
- create a new bundle xss.compat based on the last release of the xss bundle,
- deprecate all classes in its
+1
regards,
Karl
On Wed, Apr 26, 2017 at 4:36 PM, Karl Pauls wrote:
> Hi,
>
> based on the discussions in the "move o.a.s.xss.JsonUtil into a
> separate package" and the "Versioning of o.a.s.xss" threads I would
> like to get consensus on the following way forward:
>
> - create a new bundle xss
Sounds good to me, +1
Carsten
Karl Pauls wrote
> Hi,
>
> based on the discussions in the "move o.a.s.xss.JsonUtil into a
> separate package" and the "Versioning of o.a.s.xss" threads I would
> like to get consensus on the following way forward:
>
> - create a new bundle xss.compat based on the
+1
>-Original Message-
>From: Karl Pauls [mailto:karlpa...@gmail.com]
>Sent: Wednesday, April 26, 2017 4:36 PM
>To: dev@sling.apache.org
>Subject: [VOTE] XSSAPI
>
>Hi,
>
>based on the discussions in the "move o.a.s.xss.JsonUtil into a
>separate packag
+1
On Wed, 26 Apr 2017 at 18:15 Stefan Seifert wrote:
> +1
>
> >-Original Message-
> >From: Karl Pauls [mailto:karlpa...@gmail.com]
> >Sent: Wednesday, April 26, 2017 4:36 PM
> >To: dev@sling.apache.org
> >Subject: [VOTE] XSSAPI
> >
> >
tescu wrote:
> +1
>
> On Wed, 26 Apr 2017 at 18:15 Stefan Seifert wrote:
>
>> +1
>>
>> >-Original Message-
>> >From: Karl Pauls [mailto:karlpa...@gmail.com]
>> >Sent: Wednesday, April 26, 2017 4:36 PM
>> >To: dev@sling.apache.