我在测试环境中从远程仓库更新捆绑软件时遇到问题。环境包括带有ServiceMix(或同为Karaf)的多台服务器和带有JFrog Artifactory的服务器。
在karaf 3.0.X
之前,我们使用SNAPSHOT版本动态更新OSGi容器上的捆绑软件,但是现在karaf搜索捆绑软件在本地存储库中,如果存在,则永远不要检查远程存储库(人工工厂)上的最新版本。我该如何解决?
karaf和maven的配置示例(已为用户设置M2_HOME
)
settings.xml($M2_HOME/conf/settings.xml
)
<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<pluginGroups/>
<proxies/>
<servers/>
<mirrors/>
<profiles>
<profile>
<id>default-repo-settings</id>
<activation>
<activeByDefault/>
</activation>
<repositories>
<repository>
<id>artifactory</id>
<url>http://artifactory/ext-snapshot-local</url>
<snapshots>
<updatePolicy>always</updatePolicy>
</snapshots>
<releases>
<updatePolicy>always</updatePolicy>
</releases>
</repository>
<!-- same repos here -->
</repositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>default-repo-settings</activeProfile>
</activeProfiles>
</settings>
org.ops4j.pax.url.mvn.cfg(
$KARAF_HOME/etc/org.ops4j.pax.url.mvn.cfg
)org.ops4j.pax.url.mvn.useFallbackRepositories=false
org.ops4j.pax.url.mvn.disableAether=true
org.ops4j.pax.url.mvn.useLocalRepositoryAsRemote=true
org.ops4j.pax.url.mvn.globalUpdatePolicy=always
org.ops4j.pax.url.mvn.defaultRepositories=file:${karaf.home}}/${karaf.default.repository}}@snapshots@id=karaf.${karaf.default.repository}}
org.ops4j.pax.url.mvn.repositories= \
http://artifactory/ext-snapshot-local@snapshots@id=artifactory, \
http://repo1.maven.org/maven2@id=central, \
http://repository.springsource.com/maven/bundles/release@id=spring.ebr.release, \
http://repository.springsource.com/maven/bundles/external@id=spring.ebr.external, \
http://zodiac.springsource.com/maven/bundles/release@id=gemini, \
http://repository.apache.org/content/groups/snapshots-group@id=apache@snapshots@noreleases, \
https://oss.sonatype.org/content/repositories/snapshots@id=sonatype.snapshots.deploy@snapshots@noreleases, \
https://oss.sonatype.org/content/repositories/ops4j-snapshots@id=ops4j.sonatype.snapshots.deploy@snapshots@noreleases
最佳答案
最好简化您的工件升级方法,使其只有一个位置才能将工件传输到SMX / Karaf容器。我建议您设置Artifactory,以便您有一个虚拟存储库,它将您的内部存储库与远程存储库(Maven Central,Spring等)合并。您的容器应仅指向您的内部Artifactory实例。这也使您的Artifactory可以缓存远程仓库,而您不再依赖于Internet的建立以及远程Maven Repos的建立。
现在,无论何时您执行“更新$ bundleId”,它都会查询虚拟仓库,Artifactory将在-SNAPSHOT工件上为您提供最佳的匹配项。
另外,从本地文件中删除@snapshots可能是个好主意:repo行有助于避免混淆。