actually, adding the latest version would be better
[artifacts]
org.apache.sling/org.apache.sling.models.jacksonexporter/1.0.7-SNAPSHOT
com.fasterxml.jackson.core/jackson-databind/2.8.6
com.fasterxml.jackson.core/jackson-core/2.8.6
com.fasterxml.jackson.core/jackson-annotations/2.8.6On 4/3/2017 11:26 AM, Ruben Reusser wrote:
while you are at fixing the launchpad, would be good to add [feature name=model-exporter] # Add the dependencies on the Model exporter [artifacts] org.apache.sling/org.apache.sling.models.jacksonexporter/1.0.7-SNAPSHOT com.fasterxml.jackson.core/jackson-databind/2.3.2 com.fasterxml.jackson.core/jackson-core/2.3.2 com.fasterxml.jackson.core/jackson-annotations/2.3.2 at the same time Ruben On 4/3/2017 11:24 AM, Oliver Lietz wrote:On Monday 03 April 2017 20:16:49 Carsten Ziegeler wrote:Some packages changed in Sightly recently. Using latest Sightly snapshots inJust fixed the bug in the servlets post servlet, still remaining: ServerSideInstallerTest.noActiveResources:61 Active resources found:[group[[resource[entityId=bundle:org.apache.sling.scripting.sightly.js.provider, scheme=launchpad,url=launchpad:resources/install/0/org.apache.sling.scripting.sightly.js.prov ider-1.0.20.jar, type=bundle, error=null, state=INSTALL, version=1.0.20,lastChange=-1, priority=50, digest=1491243240000]]]]Launchpad fixed it for me. Regards, O.Carsten Carsten Ziegeler wroteRuben Reusser wroteseems to me it's because Apache Sling Scripting HTL JavaScript Use Provider does not activate anymore.Yes, that seems to be one error.But the file upload is currently not fully working either and that's due to my "improvements" in that area. I just fixed one of the failing testcases, looking into the other now. Carsten
