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 4F0C3200CC4 for ; Thu, 13 Jul 2017 08:48:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4D82016AA53; Thu, 13 Jul 2017 06:48:10 +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 936AB16AA4E for ; Thu, 13 Jul 2017 08:48:09 +0200 (CEST) Received: (qmail 35486 invoked by uid 500); 13 Jul 2017 06:48:08 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 35475 invoked by uid 99); 13 Jul 2017 06:48:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jul 2017 06:48:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 48DB819627E for ; Thu, 13 Jul 2017 06:48:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Vtf86QdIQxd7 for ; Thu, 13 Jul 2017 06:48:07 +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 8D5E05F523 for ; Thu, 13 Jul 2017 06:48:06 +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 B96B9E00A3 for ; Thu, 13 Jul 2017 06:48:05 +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 1A03424736 for ; Thu, 13 Jul 2017 06:48:00 +0000 (UTC) Date: Thu, 13 Jul 2017 06:48:00 +0000 (UTC) From: "Grzegorz Grzybek (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (KARAF-2970) Software deployed on Karaf will not update if Karaf detects the presence of a previous .M2 directory MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 13 Jul 2017 06:48:10 -0000 [ https://issues.apache.org/jira/browse/KARAF-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved KARAF-2970. ------------------------------------- Resolution: Not A Problem > Software deployed on Karaf will not update if Karaf detects the presence of a previous .M2 directory > ----------------------------------------------------------------------------------------------------- > > Key: KARAF-2970 > URL: https://issues.apache.org/jira/browse/KARAF-2970 > Project: Karaf > Issue Type: Bug > Components: karaf-archetypes, karaf-config, karaf-core, karaf-documentation, karaf-exam, karaf-feature, karaf-instance, karaf-kar, karaf-os-integration, karaf-osgi, karaf-repository, karaf-scheduler, karaf-scr, karaf-security, karaf-shell, karaf-test, karaf-tooling, karaf-webconsole, karaf-webcontainer > Affects Versions: 3.0.0 > Environment: Windows Server 2008 R2, Windows 2008 R2 SP2, Windows 2012 R2 > Reporter: Chris Longo > Assignee: Grzegorz Grzybek > > The presence of a .M2 directory causes an application deployed on Karaf not to update. > Prerequisites: > A) Deploy an application on Karaf > B) Verify there is the presence of an .M2 directory > Steps to Reproduce: > Deploy a revised application build on Karaf > Actual Result: > The bits from the local .M2 repo are kept and not overwritten with the newest modified bits > Expected Result: > The bits from the local .M2 repo should be updated even if the .M2 directory was present prior to installing the updated app deployed on Karaf > Workaround: > 1.Delete the .M2 directory > 2.Deploy the software on Karaf > 3.The local .M2 directory will now be updated -- This message was sent by Atlassian JIRA (v6.4.14#64029)