Return-Path: X-Original-To: apmail-maven-users-archive@www.apache.org Delivered-To: apmail-maven-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2802C10B03 for ; Wed, 23 Oct 2013 18:12:46 +0000 (UTC) Received: (qmail 44388 invoked by uid 500); 23 Oct 2013 18:10:34 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 44206 invoked by uid 500); 23 Oct 2013 18:10:32 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 44112 invoked by uid 99); 23 Oct 2013 18:10:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Oct 2013 18:10:30 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ziga.gregoric@gmail.com designates 74.125.82.181 as permitted sender) Received: from [74.125.82.181] (HELO mail-we0-f181.google.com) (74.125.82.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Oct 2013 18:10:26 +0000 Received: by mail-we0-f181.google.com with SMTP id t60so1198327wes.40 for ; Wed, 23 Oct 2013 11:10:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=Ijvmwr1ztz2wwvTWik2pw/KPPABM0EbbilUyM6Y81Gk=; b=k3cqVSSl8U4i726AW1kPftLiMqvd5Z7YMqcaJpkCnKm+ey9YDtiuwzulAJUhfyk9Oh mNrTgu6PkRQ3LG01e2yIOx1RwrQvIDlK2HFE8Wdx+qgSaaxuFGZOGy9NQHqK4XQHYtld vPnZFF+9vGnAJqoIXK1B7XP2OQbna0/DrxA/GTGZ4hoBGTh+pTu6COmgwEqAhohg4w17 mOxVR/0CY2IuxF0o45SJ6Oa4OILhaHjLs7B7bNID39fNtABMZwfEpdy0hty9ERZ8llm/ Edg8GAXgPSIIx3BmbaL9NPFd90KiUBisl8qfoTxYBYSwyWQ7lkGN6DYrfV9QgKBtil2f aYKQ== X-Received: by 10.180.72.195 with SMTP id f3mr2604429wiv.51.1382551804585; Wed, 23 Oct 2013 11:10:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.184.136 with HTTP; Wed, 23 Oct 2013 11:09:44 -0700 (PDT) In-Reply-To: <52680EF8.9070106@t-sciences.com> References: <52674A2B.9090203@t-sciences.com> <30BD106F-B30A-4A01-822E-CA5488FFFFCA@gold-family.us> <52675727.9060908@t-sciences.com> <41C7FC52-9BF2-4D36-A681-99F7A346D41A@gold-family.us> <52680EF8.9070106@t-sciences.com> From: Ziga GREGORIC Date: Wed, 23 Oct 2013 20:09:44 +0200 Message-ID: Subject: Re: Blacklisting during Dependency Location To: Maven Users List Content-Type: multipart/alternative; boundary=f46d043c7b8c322d4c04e96c6df6 X-Virus-Checked: Checked by ClamAV on apache.org --f46d043c7b8c322d4c04e96c6df6 Content-Type: text/plain; charset=UTF-8 Hi Robert, long time ago, I had similar issue. Try adding this snipplet to your pom.xml The version of the plugin might not be the latest, but it worked for me (back then): maven-project-info-reports-plugin 2.2 false Cheers, Ziga Gregoric On Wed, Oct 23, 2013 at 8:01 PM, Robert Kuropkat wrote: > > So it is even weirder than I thought. I cleared the .m2 cache and typed > mvn compile install, then mvn site and it worked! Then I typed mvn site > again and it failed (blacklisted to repo). That doesn't even make sense to > me. If I clear the m2 cache and do a mvn install again, it repopulates the > .m2 cache and typing mvn site then works. Typing mvn site again fails. So > far it seems for all the world like I have to clear the .m2 cache everytime > in order to run mvn site. > > Trying hard to make that makes sense, so any other thoughts would be > appreciated... > > Robert Kuropkat > > > > On 10/23/2013 08:23 AM, Stephen Connolly wrote: > >> Our corporate internal repo needs a login for read access, and we have no >> issues when people use the settings.xml that I tell them to use! >> >> >> On 23 October 2013 13:19, Russell Gold wrote: >> >> Hi Robert, >>> >>> In all of the repositories I've seen, you never had to login to see >>> dependencies. They were always publicly readable; logging in was always >>> just to control who could upload. I suspect that your repository is >>> misconfigured. >>> >>> - Russ >>> >>> On Oct 23, 2013, at 12:57 AM, Robert Kuropkat >>> wrote: >>> >>> Must login to see the dependencies. So in the settings.xml we have a >>>> >>> section to define the repository location and a >>> section to match the repository id with a username and password. >>> >>>> Robert >>>> >>>> >>>> On 10/23/2013 12:06 AM, Russell Gold wrote: >>>> >>>>> Are you saying that it takes a login to see the dependencies? So once >>>>> >>>> you login, you are presented with a set of directories? >>> >>>> Or possibly you are pointing to the control address rather than the >>>>> >>>> dependency address? >>> >>>> - Russ >>>>> >>>>> On Oct 23, 2013, at 12:01 AM, Robert Kuropkat < >>>>> rkuropkat@t-sciences.com> >>>>> >>>> wrote: >>> >>>> I am trying to use the site goal but some of our internal repositories >>>>>> >>>>> are getting blacklisted as being "invalid." There are no network >>> issues, I >>> can access the repository just fine and it downloads dependencies as >>> needed. I don't want to disable this feature. How do I actually make it >>> work? >>> >>>> I have two internal nexus repositories, one works, the other doesn't. >>>>>> >>>>>> repo1 (works) - on my local laptop, mega default setup. >>>>>> >>>>>> repo2 (blacklisted) - corporate network, connected via VPN, setup like >>>>>> >>>>> a real repository. Requires login. >>> >>>> Everything in the output of mvn -e -X site seems to look fine clear up >>>>>> >>>>> until it says the repo is invalid and blacklisted. The site report is >>> completed. Going to the Dependency Location web page and clicking on the >>> link provided for the blacklisted repo pops up the exected login prompt >>> and >>> then displays the repository. >>> >>>> I suspect, the reason repo2 gets blacklisted by the dependency >>>>>> >>>>> location part of the site goal is because it requires a login and is >>> not >>> using the server information in the settings.xml. >>> >>>> While I know there is no network issue, I would not rule out repo2 >>>>>> >>>>> being malconfigured. I just can't figure out where to start looking. >>> >>>> As I said, I really want this feature to work so disabling it with >>>>>> >>>>> -Ddependency.locations.**enabled=false is "uninteresting." >>> >>>> Robert Kuropkat >>>>>> >>>>>> >>>>>> ------------------------------**------------------------------** >>>>>> --------- >>>>>> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org >>>>>> For additional commands, e-mail: users-help@maven.apache.org >>>>>> >>>>>> ----------------- >>>>> Author, Getting Started with Apache Maven < >>>>> >>>> http://www.packtpub.com/**getting-started-with-apache-**maven/video >>> > >>> >>>> Come read my webnovel, Take a Lemon , >>>>> and listen to the Misfile radio play < >>>>> >>>> http://www.fuzzyfacetheater.**com/misfile/ >>> >! >>> >>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> ------------------------------**------------------------------** >>>> --------- >>>> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org >>>> For additional commands, e-mail: users-help@maven.apache.org >>>> >>>> ----------------- >>> Author, Getting Started with Apache Maven < >>> http://www.packtpub.com/**getting-started-with-apache-**maven/video >>> > >>> >>> Come read my webnovel, Take a Lemon , >>> and listen to the Misfile radio play < >>> http://www.fuzzyfacetheater.**com/misfile/ >>> >! >>> >>> >>> >>> >>> >>> >>> >>> >>> > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org > For additional commands, e-mail: users-help@maven.apache.org > > --f46d043c7b8c322d4c04e96c6df6--