[
https://issues.apache.org/jira/browse/KARAF-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062669#comment-16062669
]
Grzegorz Grzybek commented on KARAF-2970:
-----------------------------------------
Please read [aether configuration
documentation|https://ops4j1.jira.com/wiki/display/paxurl/Aether+Configuration]
where you can see various configuration options related to update policies etc.
Also, I hope you'll find helpful my series of articles related to "Maven on
OSGi":
*
[introduction|http://ggrzybek.blogspot.com/2016/07/using-maven-with-osgi-part-1.html]
*
[configuration|http://ggrzybek.blogspot.com/2016/07/using-maven-with-osgi-part-2.html]
*
[SNAPSHOTs|http://ggrzybek.blogspot.com/2016/10/using-maven-with-osgi-part-3.html]
> 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)
