[jira] [Commented] (KARAF-2970) Software deployed on Karaf will not update if Karaf detects the presence of a previous .M2 directory

["Grzegorz Grzybek (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KARAF-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083770#comment-16083770 ] 

Grzegorz Grzybek commented on KARAF-2970:
-----------------------------------------

[~ChrisIsGood], are you still interested in this issue?

Shortly - I don't think it's valid. local maven repository (by default {{~/.m2/repository}}) is not something specific to Karaf, but pax-url-aether.

{{etc/org.ops4j.pax.url.mvn.cfg}} file contains {{org.ops4j.pax.url.mvn.localRepository}} property (if not specified, it defaults to {{~/.m2/repository}}) which is used to store artifacts resolved in remote Maven repositories (e.g., in Maven Central).

I'm not sure what you mean by _Deploy a revised application build on Karaf_ - usually it's done by {{mvn clean install}} new version of artifact to your local repository and doing {{osgi:update BundleId}} from Karaf shell. Did you expect something opposite?

> 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
>
> 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)