You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Todd Nine <to...@gmail.com> on 2008/01/11 21:38:31 UTC
Remote repository with self signed cert
Hi all,
I have a repository that is DAV compatible. I can upload to it, as well
as download from an http client. Only the upload requires a password.
However whenever I try to perform a build that requires me to download an
artifact I receive the following stacktrace. If I go to the repo with my
browser (firefox), the artifacts are located exactly where they should be.
The repository uses a self signed certificate, however I have installed the
certificate into my keystore with the "keytool" command. I can successfully
release/deploy to the repository, but I can't download the released
artifacts on another machine, or my own if I delete the built artifacts from
my local repo. Is this possibly an issue with the self signed cert? Below
is my stack trace, any help would be appreciated.
Thanks,
Todd
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
bnp-repo (https://projects.bnpmedia.com/repository/)
for project com.bnpmedia.standards:config
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(
DefaultMavenProjectBuilder.java:571)
at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(
DefaultMavenProjectBuilder.java:1255)
... 17 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
Unable to download the artifact from any repository
com.bnpmedia.standards:config:pom:1.0.0
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
bnp-repo (https://projects.bnpmedia.com/repository/)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
DefaultArtifactResolver.java:206)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
DefaultArtifactResolver.java:73)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(
DefaultMavenProjectBuilder.java:524)
... 18 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to
download the artifact from any repository
at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(
DefaultWagonManager.java:324)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
DefaultArtifactResolver.java:194)
... 20 more
Re: Remote repository with self signed cert
Posted by Wayne Fay <wa...@gmail.com>.
Does running with mvn -X tell you any more details than what we're seeing here?
Wayne
On 1/11/08, Todd Nine <to...@gmail.com> wrote:
> Hi all,
> I have a repository that is DAV compatible. I can upload to it, as well
> as download from an http client. Only the upload requires a password.
> However whenever I try to perform a build that requires me to download an
> artifact I receive the following stacktrace. If I go to the repo with my
> browser (firefox), the artifacts are located exactly where they should be.
> The repository uses a self signed certificate, however I have installed the
> certificate into my keystore with the "keytool" command. I can successfully
> release/deploy to the repository, but I can't download the released
> artifacts on another machine, or my own if I delete the built artifacts from
> my local repo. Is this possibly an issue with the self signed cert? Below
> is my stack trace, any help would be appreciated.
>
> Thanks,
> Todd
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> bnp-repo (https://projects.bnpmedia.com/repository/)
> for project com.bnpmedia.standards:config
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(
> DefaultMavenProjectBuilder.java:571)
> at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(
> DefaultMavenProjectBuilder.java:1255)
> ... 17 more
> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> Unable to download the artifact from any repository
>
> com.bnpmedia.standards:config:pom:1.0.0
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> bnp-repo (https://projects.bnpmedia.com/repository/)
>
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:206)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:73)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(
> DefaultMavenProjectBuilder.java:524)
> ... 18 more
> Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to
> download the artifact from any repository
> at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(
> DefaultWagonManager.java:324)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:194)
> ... 20 more
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Remote repository with self signed cert
Posted by Todd Nine <to...@gmail.com>.
Thanks for the info. I've actually already performed those steps, its what
I did to import the certificate in order to get the dav deployment to work
with a self signed cert. It turns out that this was a routing issue with
the VPN routing. Its since been fixed. Thanks to everyone for all the help
you've provided.
On Jan 12, 2008 3:11 AM, Insitu <ab...@oqube.com> wrote:
> Hello,
> I managed to deploy/download from https sites with client side
> authentication following this guide:
>
> http://maven.apache.org/guides/mini/guide-repository-ssl.html
>
> Maybe you could provide more information on your configuration (pom +
> settings) ?
>
> Regards,
> --
> Arnaud Bailly, PhD
> OQube - Software Engineering
> http://www.oqube.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Remote repository with self signed cert
Posted by Insitu <ab...@oqube.com>.
Hello,
I managed to deploy/download from https sites with client side
authentication following this guide:
http://maven.apache.org/guides/mini/guide-repository-ssl.html
Maybe you could provide more information on your configuration (pom +
settings) ?
Regards,
--
Arnaud Bailly, PhD
OQube - Software Engineering
http://www.oqube.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Remote repository with self signed cert
Posted by Todd Nine <to...@gmail.com>.
But that's the wagon that works. Its when maven attempts to download the
dependencies via an https:// (non-dav) connection it pukes.
On Jan 11, 2008 5:06 PM, Jeff MAURY <je...@jeffmaury.com> wrote:
> Which Wagon provider do you use ? If you use WebDAV, see this page :
> http://maven.apache.org/wagon/wagon-providers/wagon-webdav/
>
> Jeff
>
>
> On Jan 11, 2008 10:56 PM, Todd Nine <to...@gmail.com> wrote:
>
> > Unfortunately the stack trace I sent was with -X. Not very helpful is
> it
> > :)? What I don't understand, is if the dav deploy works with the self
> > signed cert in my kestore, why does the build process not trust the
> > certificate as well?
> >
> > On Jan 11, 2008 4:15 PM, Jeff MAURY <je...@jeffmaury.com> wrote:
> >
> > > I suppose wagon has trouble with your self signed certificate.
> > >
> > > Jeff
> > >
> > >
> > > On Jan 11, 2008 9:45 PM, Todd Nine <to...@gmail.com> wrote:
> > >
> > > > Just an FYI, it does work with http, however we need to use https
> for
> > > > security reasons, so our http repository will be shut off shortly.
> > > >
> > > > On Jan 11, 2008 3:38 PM, Todd Nine <to...@gmail.com> wrote:
> > > >
> > > > > Hi all,
> > > > > I have a repository that is DAV compatible. I can upload to it,
> > as
> > > > well
> > > > > as download from an http client. Only the upload requires a
> > password.
> > > > > However whenever I try to perform a build that requires me to
> > download
> > > > an
> > > > > artifact I receive the following stacktrace. If I go to the repo
> > with
> > > > my
> > > > > browser (firefox), the artifacts are located exactly where they
> > should
> > > > be.
> > > > > The repository uses a self signed certificate, however I have
> > > installed
> > > > the
> > > > > certificate into my keystore with the "keytool" command. I can
> > > > successfully
> > > > > release/deploy to the repository, but I can't download the
> released
> > > > > artifacts on another machine, or my own if I delete the built
> > > artifacts
> > > > from
> > > > > my local repo. Is this possibly an issue with the self signed
> cert?
> > > > Below
> > > > > is my stack trace, any help would be appreciated.
> > > > >
> > > > > Thanks,
> > > > > Todd
> > > > >
> > > > > from the specified remote repositories:
> > > > > central (http://repo1.maven.org/maven2),
> > > > > bnp-repo ( https://projects.bnpmedia.com/repository/)
> > > > > for project com.bnpmedia.standards:config
> > > > > at
> > > > >
> > > >
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > > > > (DefaultMavenProjectBuilder.java:571)
> > > > > at
> > > > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage
> > > > > (DefaultMavenProjectBuilder.java:1255)
> > > > > ... 17 more
> > > > > Caused by:
> > > org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> > > > > Unable to download the artifact from any repository
> > > > >
> > > > > com.bnpmedia.standards:config:pom:1.0.0
> > > > >
> > > > > from the specified remote repositories:
> > > > > central (http://repo1.maven.org/maven2),
> > > > > bnp-repo ( https://projects.bnpmedia.com/repository/)
> > > > >
> > > > > at
> > > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > > > DefaultArtifactResolver.java:206)
> > > > > at
> > > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > > > DefaultArtifactResolver.java:73)
> > > > > at
> > > > >
> > > >
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > > > > (DefaultMavenProjectBuilder.java:524)
> > > > > ... 18 more
> > > > > Caused by: org.apache.maven.wagon.ResourceDoesNotExistException :
> > > Unable
> > > > > to download the artifact from any repository
> > > > > at
> > > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
> > > > (
> > > > > DefaultWagonManager.java:324)
> > > > > at
> > > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > > > DefaultArtifactResolver.java:194)
> > > > > ... 20 more
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > La mélancolie c'est communiste
> > > Tout le monde y a droit de temps en temps
> > > La mélancolie n'est pas capitaliste
> > > C'est même gratuit pour les perdants
> > > La mélancolie c'est pacifiste
> > > On ne lui rentre jamais dedans
> > > La mélancolie oh tu sais ça existe
> > > Elle se prend même avec des gants
> > > La mélancolie c'est pour les syndicalistes
> > > Il faut juste sa carte de permanent
> > >
> > > Miossec (2006)
> > >
> > > http://www.jeffmaury.com
> > > http://riadiscuss.jeffmaury.com
> > >
> >
>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
>
Re: Remote repository with self signed cert
Posted by Jeff MAURY <je...@jeffmaury.com>.
Which Wagon provider do you use ? If you use WebDAV, see this page :
http://maven.apache.org/wagon/wagon-providers/wagon-webdav/
Jeff
On Jan 11, 2008 10:56 PM, Todd Nine <to...@gmail.com> wrote:
> Unfortunately the stack trace I sent was with -X. Not very helpful is it
> :)? What I don't understand, is if the dav deploy works with the self
> signed cert in my kestore, why does the build process not trust the
> certificate as well?
>
> On Jan 11, 2008 4:15 PM, Jeff MAURY <je...@jeffmaury.com> wrote:
>
> > I suppose wagon has trouble with your self signed certificate.
> >
> > Jeff
> >
> >
> > On Jan 11, 2008 9:45 PM, Todd Nine <to...@gmail.com> wrote:
> >
> > > Just an FYI, it does work with http, however we need to use https for
> > > security reasons, so our http repository will be shut off shortly.
> > >
> > > On Jan 11, 2008 3:38 PM, Todd Nine <to...@gmail.com> wrote:
> > >
> > > > Hi all,
> > > > I have a repository that is DAV compatible. I can upload to it,
> as
> > > well
> > > > as download from an http client. Only the upload requires a
> password.
> > > > However whenever I try to perform a build that requires me to
> download
> > > an
> > > > artifact I receive the following stacktrace. If I go to the repo
> with
> > > my
> > > > browser (firefox), the artifacts are located exactly where they
> should
> > > be.
> > > > The repository uses a self signed certificate, however I have
> > installed
> > > the
> > > > certificate into my keystore with the "keytool" command. I can
> > > successfully
> > > > release/deploy to the repository, but I can't download the released
> > > > artifacts on another machine, or my own if I delete the built
> > artifacts
> > > from
> > > > my local repo. Is this possibly an issue with the self signed cert?
> > > Below
> > > > is my stack trace, any help would be appreciated.
> > > >
> > > > Thanks,
> > > > Todd
> > > >
> > > > from the specified remote repositories:
> > > > central (http://repo1.maven.org/maven2),
> > > > bnp-repo ( https://projects.bnpmedia.com/repository/)
> > > > for project com.bnpmedia.standards:config
> > > > at
> > > >
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > > > (DefaultMavenProjectBuilder.java:571)
> > > > at
> > > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage
> > > > (DefaultMavenProjectBuilder.java:1255)
> > > > ... 17 more
> > > > Caused by:
> > org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> > > > Unable to download the artifact from any repository
> > > >
> > > > com.bnpmedia.standards:config:pom:1.0.0
> > > >
> > > > from the specified remote repositories:
> > > > central (http://repo1.maven.org/maven2),
> > > > bnp-repo ( https://projects.bnpmedia.com/repository/)
> > > >
> > > > at
> > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > > DefaultArtifactResolver.java:206)
> > > > at
> > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > > DefaultArtifactResolver.java:73)
> > > > at
> > > >
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > > > (DefaultMavenProjectBuilder.java:524)
> > > > ... 18 more
> > > > Caused by: org.apache.maven.wagon.ResourceDoesNotExistException :
> > Unable
> > > > to download the artifact from any repository
> > > > at
> > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
> > > (
> > > > DefaultWagonManager.java:324)
> > > > at
> > > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > > DefaultArtifactResolver.java:194)
> > > > ... 20 more
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > La mélancolie c'est communiste
> > Tout le monde y a droit de temps en temps
> > La mélancolie n'est pas capitaliste
> > C'est même gratuit pour les perdants
> > La mélancolie c'est pacifiste
> > On ne lui rentre jamais dedans
> > La mélancolie oh tu sais ça existe
> > Elle se prend même avec des gants
> > La mélancolie c'est pour les syndicalistes
> > Il faut juste sa carte de permanent
> >
> > Miossec (2006)
> >
> > http://www.jeffmaury.com
> > http://riadiscuss.jeffmaury.com
> >
>
--
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent
Miossec (2006)
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
Re: Remote repository with self signed cert
Posted by Todd Nine <to...@gmail.com>.
Unfortunately the stack trace I sent was with -X. Not very helpful is it
:)? What I don't understand, is if the dav deploy works with the self
signed cert in my kestore, why does the build process not trust the
certificate as well?
On Jan 11, 2008 4:15 PM, Jeff MAURY <je...@jeffmaury.com> wrote:
> I suppose wagon has trouble with your self signed certificate.
>
> Jeff
>
>
> On Jan 11, 2008 9:45 PM, Todd Nine <to...@gmail.com> wrote:
>
> > Just an FYI, it does work with http, however we need to use https for
> > security reasons, so our http repository will be shut off shortly.
> >
> > On Jan 11, 2008 3:38 PM, Todd Nine <to...@gmail.com> wrote:
> >
> > > Hi all,
> > > I have a repository that is DAV compatible. I can upload to it, as
> > well
> > > as download from an http client. Only the upload requires a password.
> > > However whenever I try to perform a build that requires me to download
> > an
> > > artifact I receive the following stacktrace. If I go to the repo with
> > my
> > > browser (firefox), the artifacts are located exactly where they should
> > be.
> > > The repository uses a self signed certificate, however I have
> installed
> > the
> > > certificate into my keystore with the "keytool" command. I can
> > successfully
> > > release/deploy to the repository, but I can't download the released
> > > artifacts on another machine, or my own if I delete the built
> artifacts
> > from
> > > my local repo. Is this possibly an issue with the self signed cert?
> > Below
> > > is my stack trace, any help would be appreciated.
> > >
> > > Thanks,
> > > Todd
> > >
> > > from the specified remote repositories:
> > > central (http://repo1.maven.org/maven2),
> > > bnp-repo ( https://projects.bnpmedia.com/repository/)
> > > for project com.bnpmedia.standards:config
> > > at
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > > (DefaultMavenProjectBuilder.java:571)
> > > at
> > org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage
> > > (DefaultMavenProjectBuilder.java:1255)
> > > ... 17 more
> > > Caused by:
> org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> > > Unable to download the artifact from any repository
> > >
> > > com.bnpmedia.standards:config:pom:1.0.0
> > >
> > > from the specified remote repositories:
> > > central (http://repo1.maven.org/maven2),
> > > bnp-repo ( https://projects.bnpmedia.com/repository/)
> > >
> > > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > DefaultArtifactResolver.java:206)
> > > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > DefaultArtifactResolver.java:73)
> > > at
> > >
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > > (DefaultMavenProjectBuilder.java:524)
> > > ... 18 more
> > > Caused by: org.apache.maven.wagon.ResourceDoesNotExistException :
> Unable
> > > to download the artifact from any repository
> > > at
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
> > (
> > > DefaultWagonManager.java:324)
> > > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > > DefaultArtifactResolver.java:194)
> > > ... 20 more
> > >
> > >
> >
>
>
>
> --
> La mélancolie c'est communiste
> Tout le monde y a droit de temps en temps
> La mélancolie n'est pas capitaliste
> C'est même gratuit pour les perdants
> La mélancolie c'est pacifiste
> On ne lui rentre jamais dedans
> La mélancolie oh tu sais ça existe
> Elle se prend même avec des gants
> La mélancolie c'est pour les syndicalistes
> Il faut juste sa carte de permanent
>
> Miossec (2006)
>
> http://www.jeffmaury.com
> http://riadiscuss.jeffmaury.com
>
Re: Remote repository with self signed cert
Posted by Jeff MAURY <je...@jeffmaury.com>.
I suppose wagon has trouble with your self signed certificate.
Jeff
On Jan 11, 2008 9:45 PM, Todd Nine <to...@gmail.com> wrote:
> Just an FYI, it does work with http, however we need to use https for
> security reasons, so our http repository will be shut off shortly.
>
> On Jan 11, 2008 3:38 PM, Todd Nine <to...@gmail.com> wrote:
>
> > Hi all,
> > I have a repository that is DAV compatible. I can upload to it, as
> well
> > as download from an http client. Only the upload requires a password.
> > However whenever I try to perform a build that requires me to download
> an
> > artifact I receive the following stacktrace. If I go to the repo with
> my
> > browser (firefox), the artifacts are located exactly where they should
> be.
> > The repository uses a self signed certificate, however I have installed
> the
> > certificate into my keystore with the "keytool" command. I can
> successfully
> > release/deploy to the repository, but I can't download the released
> > artifacts on another machine, or my own if I delete the built artifacts
> from
> > my local repo. Is this possibly an issue with the self signed cert?
> Below
> > is my stack trace, any help would be appreciated.
> >
> > Thanks,
> > Todd
> >
> > from the specified remote repositories:
> > central (http://repo1.maven.org/maven2),
> > bnp-repo ( https://projects.bnpmedia.com/repository/)
> > for project com.bnpmedia.standards:config
> > at
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > (DefaultMavenProjectBuilder.java:571)
> > at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage
> > (DefaultMavenProjectBuilder.java:1255)
> > ... 17 more
> > Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> > Unable to download the artifact from any repository
> >
> > com.bnpmedia.standards:config:pom:1.0.0
> >
> > from the specified remote repositories:
> > central (http://repo1.maven.org/maven2),
> > bnp-repo ( https://projects.bnpmedia.com/repository/)
> >
> > at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > DefaultArtifactResolver.java:206)
> > at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > DefaultArtifactResolver.java:73)
> > at
> >
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> > (DefaultMavenProjectBuilder.java:524)
> > ... 18 more
> > Caused by: org.apache.maven.wagon.ResourceDoesNotExistException : Unable
> > to download the artifact from any repository
> > at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact
> (
> > DefaultWagonManager.java:324)
> > at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> > DefaultArtifactResolver.java:194)
> > ... 20 more
> >
> >
>
--
La mélancolie c'est communiste
Tout le monde y a droit de temps en temps
La mélancolie n'est pas capitaliste
C'est même gratuit pour les perdants
La mélancolie c'est pacifiste
On ne lui rentre jamais dedans
La mélancolie oh tu sais ça existe
Elle se prend même avec des gants
La mélancolie c'est pour les syndicalistes
Il faut juste sa carte de permanent
Miossec (2006)
http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
Re: Remote repository with self signed cert
Posted by Todd Nine <to...@gmail.com>.
Just an FYI, it does work with http, however we need to use https for
security reasons, so our http repository will be shut off shortly.
On Jan 11, 2008 3:38 PM, Todd Nine <to...@gmail.com> wrote:
> Hi all,
> I have a repository that is DAV compatible. I can upload to it, as well
> as download from an http client. Only the upload requires a password.
> However whenever I try to perform a build that requires me to download an
> artifact I receive the following stacktrace. If I go to the repo with my
> browser (firefox), the artifacts are located exactly where they should be.
> The repository uses a self signed certificate, however I have installed the
> certificate into my keystore with the "keytool" command. I can successfully
> release/deploy to the repository, but I can't download the released
> artifacts on another machine, or my own if I delete the built artifacts from
> my local repo. Is this possibly an issue with the self signed cert? Below
> is my stack trace, any help would be appreciated.
>
> Thanks,
> Todd
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> bnp-repo ( https://projects.bnpmedia.com/repository/)
> for project com.bnpmedia.standards:config
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> (DefaultMavenProjectBuilder.java:571)
> at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage
> (DefaultMavenProjectBuilder.java:1255)
> ... 17 more
> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> Unable to download the artifact from any repository
>
> com.bnpmedia.standards:config:pom:1.0.0
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> bnp-repo ( https://projects.bnpmedia.com/repository/)
>
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:206)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:73)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository
> (DefaultMavenProjectBuilder.java:524)
> ... 18 more
> Caused by: org.apache.maven.wagon.ResourceDoesNotExistException : Unable
> to download the artifact from any repository
> at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(
> DefaultWagonManager.java:324)
> at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(
> DefaultArtifactResolver.java:194)
> ... 20 more
>
>