Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A761E200D59 for ; Sun, 10 Dec 2017 15:03:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A5F52160C09; Sun, 10 Dec 2017 14:03:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id F346B160C00 for ; Sun, 10 Dec 2017 15:03:05 +0100 (CET) Received: (qmail 52318 invoked by uid 500); 10 Dec 2017 14:03:05 -0000 Mailing-List: contact dev-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list dev@sling.apache.org Received: (qmail 52307 invoked by uid 99); 10 Dec 2017 14:03:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Dec 2017 14:03:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 6652A1A0A48 for ; Sun, 10 Dec 2017 14:03:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id JO6rknoInhHp for ; Sun, 10 Dec 2017 14:03:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id DCD345F296 for ; Sun, 10 Dec 2017 14:03:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 20BA4E0162 for ; Sun, 10 Dec 2017 14:03:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 56BF4212FB for ; Sun, 10 Dec 2017 14:03:00 +0000 (UTC) Date: Sun, 10 Dec 2017 14:03:00 +0000 (UTC) From: "Konrad Windszus (JIRA)" To: dev@sling.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SLING-7298) Validation IT: Use slingstart-maven-plugin in favour of pax-exam MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 10 Dec 2017 14:03:06 -0000 [ https://issues.apache.org/jira/browse/SLING-7298?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1628= 5256#comment-16285256 ]=20 Konrad Windszus commented on SLING-7298: ---------------------------------------- bq. the issue is in Oak and not in Pax Exam (Pax Exam has disclosed several= issues in the past) =E2=80=93 and the issue has to be fixed in Oak anyway Maybe, but the issue is not visible when running the IT in the context of S= ling 9 Launchpad. That is all I care about right now in the context of the = validation IT. bq. Removing the test framework to hide an issue is not very clever. Settin= g up Sling Launchpad right for testing seems to be quite tricky, right? Leaving out the cleverness factor which seems to be quite a pretty personal= view, setting up Sling Launchpad for an IT is IMHO a lot easier than relyi= ng on Pax-Exam. I am just reusing the provisioning model being provided by = Sling anyhow. I just deploy on top of that the latest version of my own bun= dle and I am done. Also starting the according server with {{slingstart-mav= en-plugin}} is a configuration in the pom.xml only (in contrast to relying = on a lot of glue code for pax exam). > Validation IT: Use slingstart-maven-plugin in favour of pax-exam > ---------------------------------------------------------------- > > Key: SLING-7298 > URL: https://issues.apache.org/jira/browse/SLING-7298 > Project: Sling > Issue Type: Improvement > Components: Validation > Affects Versions: Validation 1.0.0 > Reporter: Konrad Windszus > Assignee: Konrad Windszus > Fix For: Validation Core 1.0.2 > > > Due to issues with pax-exam with the newest Oak 1.6.0 (described in https= ://www.mail-archive.com/dev@sling.apache.org/msg72805.html) and also becaus= e leveraging pax-exam with Sling is complex (to get all necessary dependenc= ies right) I propose to use the {{slingstart-maven-plugin}} together with a= custom Sling Launchpad instead. The according model is derived from the de= fault Sling 9 launchpad and only two additional bundles are added there. > In addition the deprecated {{testing.tools}} dependency should be removed= . -- This message was sent by Atlassian JIRA (v6.4.14#64029)