Is this just me or does this seem like its being done in haste?
There was valid (from what I interpreted as rather severe) concerns
raised about one of the fixes included here that were not seemingly
addressed:
https://lists.apache.org/thread.html/790d7880e385a113e420c15ab85eff85e18a4fb097e9be63b5
This feels like an "eating your own dog food" scenario, where Sling
could just switch to using its own developed/maintained commons JSON
library...
Or is there something missing from the public conversation as to why
it's being avoided/not mentioned?
[
https://issues.apache.org/jira/browse/SLING-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367653#comment-15367653
]
Steven Walters commented on SLING-5829:
---
Fair enough I suppose, though I&#
[
https://issues.apache.org/jira/browse/SLING-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367639#comment-15367639
]
Steven Walters commented on SLING-5829:
---
I have concerns regarding the changes
On Fri, Jun 3, 2016 at 6:20 PM, Oliver Lietz wrote:
>
> On Monday 30 May 2016 15:28:04 Robert Munteanu wrote:
> > On Fri, 2016-05-27 at 11:14 +0200, Oliver Lietz wrote:
> > > I don't think there is support in Maven 3 for unit tests using a
> > > different
> > > version than for compile. Not sure i
On Wed, Feb 24, 2016 at 4:27 PM, Carsten Ziegeler
wrote:
> Thanks for bringing up this old topic :)
>
> I'm fine with either solution. It seems that nowadays webdav is used and
> as Robert mentions it's more likely that the POST servlet is available.
> But we can go with Webdav (solution a) ) for
Steven Walters created SLING-5335:
-
Summary: maven-sling-plugin: Allow installing bundles through
SlingPostServlet mechanisms
Key: SLING-5335
URL: https://issues.apache.org/jira/browse/SLING-5335
Steven Walters created SLING-4376:
-
Summary: ResourceResolver-mock throws NullPointerException in
resolve when absPath = null
Key: SLING-4376
URL: https://issues.apache.org/jira/browse/SLING-4376
