Hi,
FYI, KARAF-2316 get fixed, you can edit pom.xml
like
<groupId>org.apache.karaf.tooling</groupId>
<artifactId>features-maven-plugin</artifactId>
- <version>${karaf.version}</version>
+ <version>2.3.2-SNAPSHOT</version>
to pick up the SNAPSHOT version to test it.
Also, another work around is add
<repository>
<id>scriptengines.googlecode.com</id>
<name>Script Engines</name>
<url>http://scriptengines.googlecode.com/svn/m2-repo</url>
</repository>
to your pom, so that when this DefaultArtifactRepository get created, the proxy
configuration in maven settings.xml could be injected.
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋
www.camelone.org : The open source integration conference:
On 2013-5-17, at 下午4:45, Daniel Pocock wrote:
> On 17/05/13 02:23, Freeman Fang wrote:
>> Hi,
>>
>> Thanks for the info, I'm gonna take a close look, already create
>> KARAF-2316[1] to track it.
>>
>> [1]https://issues.apache.org/jira/browse/KARAF-2316
>
> Ok, thanks for this. In this particular case, the build has been
> attempted on a Windows machine.
>
> I'm also going to try exactly the same procedure on a Linux machine that
> is behind the same proxy, just to make sure it is not some
> platform-specific issue that is causing it to behave badly with proxy
> settings.
>
>
