Hey Michael,
Slash was not source of problems. The source of all issues was space before it.
Sorry for late response, but take a look for this example:
org.ops4j.pax.url.mvn.repositories= \ - this is wrong
org.ops4j.pax.url.mvn.repositories=\ - this is correct
You can use slash without any
Hello,
my Karaf Installation is behind a Firewall, so I have to use my own
Maven Repository in the same subnet (Nexus) to fetch the wrapper
feature from my nexus.
So I changed the file org.ops4j.pax.url.mvn.cfg, uncommented the other
repository and added my repository:
This error typically points out that your artifact is corrupted. Is it
possible that the artifact in your repository has a different md5sum than
the one on m2 central?
Kind regards,
Andreas
On Tue, Nov 15, 2011 at 13:02, Michael Prieß mailingliste...@googlemail.com
wrote:
Hello,
my Karaf
I think in some cases, the error message can be misleading. Can you check
that the jar returned by your nexus is a real jar and not an error page?
On Tue, Nov 15, 2011 at 13:02, Michael Prieß mailingliste...@googlemail.com
wrote:
Hello,
my Karaf Installation is behind a Firewall, so I have
Hi,
my repro it the last position in the config and I read in the PAX Url
Documentation that Pax Url not need a local maven installation to
fetch dependencys is this right?
Did Karaf store the fetcht dependencys under
/opt/apache-karaf-2.2.4/local-repo? Because there is no file at the
moment.
Hi Michael,
No, local-repo is only used to uncompress KAR files.
In Pax URL, if you have central in the repositories list, it will go
there: it's the default configuration.
The process is:
- first, check in the Karaf system local repository (it's a Maven repo
basically)
- second, check in
Hi,
im using no http proxy to access my maven repository, because its in
the same network.
I looked into the directory
/opt/apache-karaf-2.2.4/system/org/apache/karaf/shell but there is no
directory which have the name org.apache.karaf.shell.wrapper which I
expect.
After that I started to set
For the system folder, it's normal: wrapper is an optional feature and
not shipped in Karaf by default.
It seems taht Karaf is not able to get the wrapper jar file.
Could you try a simple wget or curl from where Karaf is installed and
check that you can get the file ?
I had something
Hi,
requesting the jar with wget works, but the response need a lot of time.
Regards,
Michael
2011/11/15 Jean-Baptiste Onofré j...@nanthrax.net:
For the system folder, it's normal: wrapper is an optional feature and not
shipped in Karaf by default.
It seems taht Karaf is not able to get
Hi,
when I fire the feature:install wrapper command I get the error msg in
the same moment back.
Maybe something in my configuration is wrong?
https://gist.github.com/3cc3606b5e4f35634a96
Regards,
Michael
2011/11/15 Jean-Baptiste Onofré j...@nanthrax.net:
AFAIR, the default timeout is PAX
I guess that you repository is configured as a proxy: it can get
artifacts from the central when it's present locally, correct ?
Could you check in your Nexus log if the repository is able to get the
artifacts from central (maybe a firewall configuration missing between
your Nexus and the
Hi,
a slash before my repository definition was the mistake.
Thanks for your help.
Cheers,
Michael
12 matches
Mail list logo
