hi,
thanks guys for the feedbacks.
So, if everybody agree I will resolve SLING-4223 and try to release Apache
Sling Default POST Servlets bundle.
Please raise your concerns if you do thing this is troublesome…
regards
antonio
On Jun 8, 2015, at 10:33 PM, Tomek Rękawek wrote:
> Hi,
>
> On Fr
Hi,
On Fri, Jun 5, 2015 at 10:50 AM, Bertrand Delacretaz wrote:
>
> SLING-4223 points to SLING-4537 and SLING-4538 which are both
> resolved, is there more to fix?
>
I don't think there is. The current version of the content loader passes
all tests and works, even if still can use some clean-up
On Wednesday 03 June 2015 09:39:41 Antonio Sanso wrote:
> hi *,
hi Antonio,
> I would like to release the Apache Sling Default POST Servlets bundle .
> I am a bit skeptic to do this due to [0]
> Indeed this has been reopened since it breaks some IT .
> May anybody shade some light :) ?
see my c
Hi,
On Wed, Jun 3, 2015 at 11:39 AM, Antonio Sanso wrote:
> ...I am a bit skeptic to do this due to [0]..
SLING-4223 points to SLING-4537 and SLING-4538 which are both
resolved, is there more to fix?
(I haven't followed so far, just trying to understand)
You mention failing integration tests b
+Tomek, Oliver
anyone ? :)
On Jun 3, 2015, at 11:39 AM, Antonio Sanso wrote:
> hi *,
>
> I would like to release the Apache Sling Default POST Servlets bundle .
> I am a bit skeptic to do this due to [0]
> Indeed this has been reopened since it breaks some IT .
> May anybody shade some light :
hi *,
I would like to release the Apache Sling Default POST Servlets bundle .
I am a bit skeptic to do this due to [0]
Indeed this has been reopened since it breaks some IT .
May anybody shade some light :) ?
regards
antonio
[0] https://issues.apache.org/jira/browse/SLING-4223
