You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Matt Madhavan <ma...@gmail.com> on 2011/09/01 00:38:52 UTC
KARAF with Nexus and maven and firewall Issues
Hello,
I'm sitting behind a firewall. My maven .m2/settings.xml is pointing to our
Nexus server
Looks like mvn URL is not working properly!
Every command I issue breaks. Any ideas?
karaf@root> features:addurl
mvn:org.apache.camel/camel-example-osgi/2.7.0/xml/features
Could not add Feature Repository:
*java.lang.RuntimeException: URL
[mvn:org.apache.camel/camel-example-osgi/2.7.0/xml/features] could not be
resolved.
*karaf@root>
karaf@root> features:install webconsole
*Error executing command: URL
[mvn:org.apache.geronimo.specs/geronimo-activation_1.1_spec/1.1] could not
be resolved.
*karaf@root>
Thanks in advance!
Matt
--
View this message in context: http://karaf.922171.n3.nabble.com/KARAF-with-Nexus-and-maven-and-firewall-Issues-tp3299753p3299753.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: KARAF with Nexus and maven and firewall Issues
Posted by Andreas Pieber <an...@gmail.com>.
but this is no reason that it shouldn't answer us if it solves the problem
before we try to fix a problem already fixed on the paxurl master :-)
Kind regards,
Andreas
On Sat, Sep 3, 2011 at 21:41, Achim Nierbeck <bc...@googlemail.com>wrote:
> Not really, the only reason I can remember is the fact it's an
> uncompatible API change, a no-no for a bugfix release
> and also that in the beginning while we where releasing either 2.2.1 or
> 2.2.2 it wasn't as stable or working as expected :)
>
> regards, Achim
>
> Am 03.09.2011 20:53, schrieb Andreas Pieber:
>
> TBH I just wanted to know if it fixes the problem :-) Do you remember why
> we didn't switched?
>
> Kind regards,
> Andreas
>
> On Fri, Sep 2, 2011 at 11:52, Achim Nierbeck <bc...@googlemail.com>wrote:
>
>> Hi Andreas,
>>
>> we had a pretty good reason not to switch to Aether resolving in the
>> 2.2.x line.
>> So I'd be cautious with switching to the 1.3.5 of pax url :)
>>
>> So it's probably better to take a look at the 1.2.x line of pax-url to
>> see what might have
>> messed up there :)
>>
>> Regards, Achim
>>
>> 2011/9/2 Andreas Pieber <an...@gmail.com>:
>> > I would guess that the problem is somewhere hidden in pax-url. Karaf
>> uses
>> > pax-url underneath to lookup in the "local karaf repo" first, then in
>> your
>> > .m2 repo and then in the other repos you've configured.
>> > The problem now is that it seams that pax-url seams to ignore the
>> > settings.xml. I would have to dig deeper but my first guess is: 2.2.x
>> uses
>> > pax-url 1.2.x branch which does not use aether for artifact resolve. You
>> can
>> > either try to use the karaf trunk or upgrade to 1.3.x (1.3.5) yourself
>> for
>> > karaf-2.2.x branch and check if this fixes your problem.
>> > Kind regards,
>> > Andreas
>> >
>> > On Thu, Sep 1, 2011 at 17:14, Matt Madhavan <ma...@gmail.com>
>> wrote:
>> >>
>> >> HI Freeman,
>> >> Will do that. But my question is should n't Karaf be pointing to my
>> local
>> >> maven repo first? And my local maven repo has the settings.xml pointing
>> to
>> >> our client's Nexus.
>> >>
>> >> That is how all the maven build worked for us. So was PaxRunner/PaxExam
>> >> etc!
>> >>
>> >> It looks like Karaf does not even recognize my local maven repo! What
>> >> happens when there is no Nexus and I have just plain Maven. I tried
>> this
>> >> set
>> >> up also(by removing the settings.xml). It did not work even in that
>> case!
>> >>
>> >> Any ideas?
>> >>
>> >> Thanks in advance!
>> >> Matt
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://karaf.922171.n3.nabble.com/KARAF-with-Nexus-and-maven-and-firewall-Issues-tp3299753p3301597.html
>> >> Sent from the Karaf - User mailing list archive at Nabble.com.
>> >
>> >
>>
>>
>>
>> --
>> --
>> *Achim Nierbeck*
>>
>>
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>> Committer & Project Lead
>> blog <http://notizblog.nierbeck.de/>
>>
>
>
>
> --
> --
> *Achim Nierbeck*
>
>
> Apache Karaf <http://karaf.apache.org/> <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead
> blog <http://notizblog.nierbeck.de/> <http://notizblog.nierbeck.de/>
>
>
Re: KARAF with Nexus and maven and firewall Issues
Posted by Achim Nierbeck <bc...@googlemail.com>.
Not really, the only reason I can remember is the fact it's an
uncompatible API change, a no-no for a bugfix release
and also that in the beginning while we where releasing either 2.2.1 or
2.2.2 it wasn't as stable or working as expected :)
regards, Achim
Am 03.09.2011 20:53, schrieb Andreas Pieber:
> TBH I just wanted to know if it fixes the problem :-) Do you remember
> why we didn't switched?
>
> Kind regards,
> Andreas
>
> On Fri, Sep 2, 2011 at 11:52, Achim Nierbeck <bcanhome@googlemail.com
> <ma...@googlemail.com>> wrote:
>
> Hi Andreas,
>
> we had a pretty good reason not to switch to Aether resolving in the
> 2.2.x line.
> So I'd be cautious with switching to the 1.3.5 of pax url :)
>
> So it's probably better to take a look at the 1.2.x line of pax-url to
> see what might have
> messed up there :)
>
> Regards, Achim
>
> 2011/9/2 Andreas Pieber <anpieber@gmail.com
> <ma...@gmail.com>>:
> > I would guess that the problem is somewhere hidden in pax-url.
> Karaf uses
> > pax-url underneath to lookup in the "local karaf repo" first,
> then in your
> > .m2 repo and then in the other repos you've configured.
> > The problem now is that it seams that pax-url seams to ignore the
> > settings.xml. I would have to dig deeper but my first guess is:
> 2.2.x uses
> > pax-url 1.2.x branch which does not use aether for artifact
> resolve. You can
> > either try to use the karaf trunk or upgrade to 1.3.x (1.3.5)
> yourself for
> > karaf-2.2.x branch and check if this fixes your problem.
> > Kind regards,
> > Andreas
> >
> > On Thu, Sep 1, 2011 at 17:14, Matt Madhavan
> <mattmadhavan@gmail.com <ma...@gmail.com>> wrote:
> >>
> >> HI Freeman,
> >> Will do that. But my question is should n't Karaf be pointing
> to my local
> >> maven repo first? And my local maven repo has the settings.xml
> pointing to
> >> our client's Nexus.
> >>
> >> That is how all the maven build worked for us. So was
> PaxRunner/PaxExam
> >> etc!
> >>
> >> It looks like Karaf does not even recognize my local maven
> repo! What
> >> happens when there is no Nexus and I have just plain Maven. I
> tried this
> >> set
> >> up also(by removing the settings.xml). It did not work even in
> that case!
> >>
> >> Any ideas?
> >>
> >> Thanks in advance!
> >> Matt
> >>
> >> --
> >> View this message in context:
> >>
> http://karaf.922171.n3.nabble.com/KARAF-with-Nexus-and-maven-and-firewall-Issues-tp3299753p3301597.html
> >> Sent from the Karaf - User mailing list archive at Nabble.com.
> >
> >
>
>
>
> --
> --
> *Achim Nierbeck*
>
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> Committer & Project Lead
> blog <http://notizblog.nierbeck.de/>
>
>
--
--
*Achim Nierbeck*
Apache Karaf<http://karaf.apache.org/> Committer& PMC
OPS4J Pax Web<http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer& Project Lead
blog<http://notizblog.nierbeck.de/>
Re: KARAF with Nexus and maven and firewall Issues
Posted by Andreas Pieber <an...@gmail.com>.
TBH I just wanted to know if it fixes the problem :-) Do you remember why we
didn't switched?
Kind regards,
Andreas
On Fri, Sep 2, 2011 at 11:52, Achim Nierbeck <bc...@googlemail.com>wrote:
> Hi Andreas,
>
> we had a pretty good reason not to switch to Aether resolving in the
> 2.2.x line.
> So I'd be cautious with switching to the 1.3.5 of pax url :)
>
> So it's probably better to take a look at the 1.2.x line of pax-url to
> see what might have
> messed up there :)
>
> Regards, Achim
>
> 2011/9/2 Andreas Pieber <an...@gmail.com>:
> > I would guess that the problem is somewhere hidden in pax-url. Karaf uses
> > pax-url underneath to lookup in the "local karaf repo" first, then in
> your
> > .m2 repo and then in the other repos you've configured.
> > The problem now is that it seams that pax-url seams to ignore the
> > settings.xml. I would have to dig deeper but my first guess is: 2.2.x
> uses
> > pax-url 1.2.x branch which does not use aether for artifact resolve. You
> can
> > either try to use the karaf trunk or upgrade to 1.3.x (1.3.5) yourself
> for
> > karaf-2.2.x branch and check if this fixes your problem.
> > Kind regards,
> > Andreas
> >
> > On Thu, Sep 1, 2011 at 17:14, Matt Madhavan <ma...@gmail.com>
> wrote:
> >>
> >> HI Freeman,
> >> Will do that. But my question is should n't Karaf be pointing to my
> local
> >> maven repo first? And my local maven repo has the settings.xml pointing
> to
> >> our client's Nexus.
> >>
> >> That is how all the maven build worked for us. So was PaxRunner/PaxExam
> >> etc!
> >>
> >> It looks like Karaf does not even recognize my local maven repo! What
> >> happens when there is no Nexus and I have just plain Maven. I tried this
> >> set
> >> up also(by removing the settings.xml). It did not work even in that
> case!
> >>
> >> Any ideas?
> >>
> >> Thanks in advance!
> >> Matt
> >>
> >> --
> >> View this message in context:
> >>
> http://karaf.922171.n3.nabble.com/KARAF-with-Nexus-and-maven-and-firewall-Issues-tp3299753p3301597.html
> >> Sent from the Karaf - User mailing list archive at Nabble.com.
> >
> >
>
>
>
> --
> --
> *Achim Nierbeck*
>
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> Committer & Project Lead
> blog <http://notizblog.nierbeck.de/>
>
Re: KARAF with Nexus and maven and firewall Issues
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi Andreas,
we had a pretty good reason not to switch to Aether resolving in the
2.2.x line.
So I'd be cautious with switching to the 1.3.5 of pax url :)
So it's probably better to take a look at the 1.2.x line of pax-url to
see what might have
messed up there :)
Regards, Achim
2011/9/2 Andreas Pieber <an...@gmail.com>:
> I would guess that the problem is somewhere hidden in pax-url. Karaf uses
> pax-url underneath to lookup in the "local karaf repo" first, then in your
> .m2 repo and then in the other repos you've configured.
> The problem now is that it seams that pax-url seams to ignore the
> settings.xml. I would have to dig deeper but my first guess is: 2.2.x uses
> pax-url 1.2.x branch which does not use aether for artifact resolve. You can
> either try to use the karaf trunk or upgrade to 1.3.x (1.3.5) yourself for
> karaf-2.2.x branch and check if this fixes your problem.
> Kind regards,
> Andreas
>
> On Thu, Sep 1, 2011 at 17:14, Matt Madhavan <ma...@gmail.com> wrote:
>>
>> HI Freeman,
>> Will do that. But my question is should n't Karaf be pointing to my local
>> maven repo first? And my local maven repo has the settings.xml pointing to
>> our client's Nexus.
>>
>> That is how all the maven build worked for us. So was PaxRunner/PaxExam
>> etc!
>>
>> It looks like Karaf does not even recognize my local maven repo! What
>> happens when there is no Nexus and I have just plain Maven. I tried this
>> set
>> up also(by removing the settings.xml). It did not work even in that case!
>>
>> Any ideas?
>>
>> Thanks in advance!
>> Matt
>>
>> --
>> View this message in context:
>> http://karaf.922171.n3.nabble.com/KARAF-with-Nexus-and-maven-and-firewall-Issues-tp3299753p3301597.html
>> Sent from the Karaf - User mailing list archive at Nabble.com.
>
>
--
--
*Achim Nierbeck*
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
Committer & Project Lead
blog <http://notizblog.nierbeck.de/>
Re: KARAF with Nexus and maven and firewall Issues
Posted by Andreas Pieber <an...@gmail.com>.
I would guess that the problem is somewhere hidden in pax-url. Karaf uses
pax-url underneath to lookup in the "local karaf repo" first, then in your
.m2 repo and then in the other repos you've configured.
The problem now is that it seams that pax-url seams to ignore the
settings.xml. I would have to dig deeper but my first guess is: 2.2.x uses
pax-url 1.2.x branch which does not use aether for artifact resolve. You can
either try to use the karaf trunk or upgrade to 1.3.x (1.3.5) yourself for
karaf-2.2.x branch and check if this fixes your problem.
Kind regards,
Andreas
On Thu, Sep 1, 2011 at 17:14, Matt Madhavan <ma...@gmail.com> wrote:
> HI Freeman,
> Will do that. But my question is should n't Karaf be pointing to my local
> maven repo first? And my local maven repo has the settings.xml pointing to
> our client's Nexus.
>
> That is how all the maven build worked for us. So was PaxRunner/PaxExam
> etc!
>
> It looks like Karaf does not even recognize my local maven repo! What
> happens when there is no Nexus and I have just plain Maven. I tried this
> set
> up also(by removing the settings.xml). It did not work even in that case!
>
> Any ideas?
>
> Thanks in advance!
> Matt
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/KARAF-with-Nexus-and-maven-and-firewall-Issues-tp3299753p3301597.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
Re: KARAF with Nexus and maven and firewall Issues
Posted by Matt Madhavan <ma...@gmail.com>.
HI Freeman,
Will do that. But my question is should n't Karaf be pointing to my local
maven repo first? And my local maven repo has the settings.xml pointing to
our client's Nexus.
That is how all the maven build worked for us. So was PaxRunner/PaxExam etc!
It looks like Karaf does not even recognize my local maven repo! What
happens when there is no Nexus and I have just plain Maven. I tried this set
up also(by removing the settings.xml). It did not work even in that case!
Any ideas?
Thanks in advance!
Matt
--
View this message in context: http://karaf.922171.n3.nabble.com/KARAF-with-Nexus-and-maven-and-firewall-Issues-tp3299753p3301597.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: KARAF with Nexus and maven and firewall Issues
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
You also need add your nexus url to the
org.ops4j.pax.url.mvn.repositories properties of etc/
org.ops4j.pax.url.mvn.cfg, which can make it available inside KARAF.
Freeman
On 2011-9-1, at 上午7:29, Matt Madhavan wrote:
> Hi,
> yes I can run Maven build from command line or using m2eclipse just
> fine!
> Only Karaf seems to have this issue.
>
> I use karaf 2.2.2
>
>
> Thanks
> Matt
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/KARAF-with-Nexus-and-maven-and-firewall-Issues-tp3299753p3299868.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
---------------------------------------------
Freeman Fang
FuseSource
Email:ffang@fusesource.com
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
Re: KARAF with Nexus and maven and firewall Issues
Posted by Matt Madhavan <ma...@gmail.com>.
Hi,
yes I can run Maven build from command line or using m2eclipse just fine!
Only Karaf seems to have this issue.
I use karaf 2.2.2
Thanks
Matt
--
View this message in context: http://karaf.922171.n3.nabble.com/KARAF-with-Nexus-and-maven-and-firewall-Issues-tp3299753p3299868.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: KARAF with Nexus and maven and firewall Issues
Posted by mikevan <mv...@comcast.net>.
Matt,
Outside of Karaf, are you able to build anything with Maven that requires access to a nexus?
----- Original Message -----
From: "Matt Madhavan [via Karaf]" <ml...@n3.nabble.com>
To: "mikevan" <mv...@comcast.net>
Sent: Wednesday, August 31, 2011 6:38:53 PM
Subject: KARAF with Nexus and maven and firewall Issues
Hello,
I'm sitting behind a firewall. My maven .m2/settings.xml is pointing to our Nexus server
Looks like mvn URL is not working properly!
Every command I issue breaks. Any ideas?
karaf@root> features:addurl mvn:org.apache.camel/camel-example-osgi/2.7.0/xml/features
Could not add Feature Repository:
java.lang.RuntimeException: URL [mvn:org.apache.camel/camel-example-osgi/2.7.0/xml/features] could not be resolved.
karaf@root>
karaf@root> features:install webconsole
Error executing command: URL [mvn:org.apache.geronimo.specs/geronimo-activation_1.1_spec/1.1] could not be resolved.
karaf@root>
Thanks in advance!
Matt
If you reply to this email, your message will be added to the discussion below: http://karaf.922171.n3.nabble.com/KARAF-with-Nexus-and-maven-and-firewall-Issues-tp3299753p3299753.html
To start a new topic under Karaf - User, email ml-node+930749-917263437-228489@n3.nabble.com
To unsubscribe from Karaf - User, click here .
-----
Mike Van
Mike Van's Open Source Technologies Blog
--
View this message in context: http://karaf.922171.n3.nabble.com/KARAF-with-Nexus-and-maven-and-firewall-Issues-tp3299753p3299854.html
Sent from the Karaf - User mailing list archive at Nabble.com.