No, that is the Mojo project. Here's Wagon's jira: http://jira.codehaus.org/browse/Wagon
Wayne On Tue, Sep 16, 2008 at 12:02 PM, Ryan de Laplante <[EMAIL PROTECTED]> wrote: > Is this where I file an issue? > > http://jira.codehaus.org/browse/MOJO > > Which component do I choose? > > > Thanks, > Ryan > > > Wayne Fay wrote: >> >> It might not be Maven but rather the Wagon that needs fixing so it >> will properly report the issue with the SSL cert. >> >> Perhaps you could file an issue against the Wagon project at Codehaus >> about this? >> >> Wayne >> >> On Tue, Sep 16, 2008 at 10:49 AM, Ryan de Laplante <[EMAIL PROTECTED]> wrote: >> >>> >>> Thank you. It turns out the problem was related to using https instead >>> of >>> http. Our SSL certificate is self signed, so Java didn't like it. It >>> would >>> have been nice if Maven told me that there was a problem with the SSL >>> certificate which would have given me a clue. >>> >>> >>> Thanks, >>> Ryan >>> >>> >>> Edelson, Justin wrote: >>> >>>> >>>> FWIW, I frequently find that using an HTTP debugger like Charles helps >>>> in >>>> tracking down this type of issue. >>>> >>>> Justin >>>> >>>> ----- Original Message ----- >>>> From: Ryan de Laplante <[EMAIL PROTECTED]> >>>> To: Maven Users List <[email protected]> >>>> Sent: Tue Sep 16 13:35:16 2008 >>>> Subject: Can't find dependency that I know is there >>>> >>>> Hi, >>>> >>>> I deployed an artifact into our new private Archiva repository. On our >>>> continuous build server I run "mvn compile" for a project that depends >>>> on >>>> that artifact. It is already configured to use the private repo. For >>>> some >>>> reason it keeps telling me that it was unable to load the dependency, >>>> but I >>>> am able to browse the repository with a web browser and download the >>>> required .jar without any problems. >>>> >>>> Any idea what the problem might be? Does having a dash in the >>>> artifactId >>>> cause problems? "SomeLibrary-api" >>>> >>>> >>>> Thanks, >>>> Ryan >>>> >>>> >>>> >>>>> >>>>> Missing: >>>>> ---------- >>>>> 1) com.mycompany.product:SomeLibrary-api:jar:1.2-SNAPSHOT >>>>> >>>>> Try downloading the file manually from the project website. >>>>> >>>>> Then, install it using the command: >>>>> .. >>>>> >>>>> Alternatively, if you host your own repository you can deploy the file >>>>> there: >>>>> ... >>>>> >>>>> Path to dependency: >>>>> 1) com.mycompany.anotherproduct:AnotherProduct:war:4.0-SNAPSHOT >>>>> 2) com.mycompany.product:SomeLibrary-api:jar:1.2-SNAPSHOT >>>>> >>>>> ---------- >>>>> 1 required artifact is missing. >>>>> >>>>> for artifact: >>>>> com.mycompany.anotherproduct:AnotherProduct:war:4.0-SNAPSHOT >>>>> >>>>> from the specified remote repositories: >>>>> snapshots >>>>> (https://dev.city.company.local/archiva/repository/snapshots), >>>>> internal (https://dev.city.company.local/archiva/repository/internal), >>>>> central (http://repo1.maven.org/maven2) >>>>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
