Re: Question about HTTP blocking WARN
For me, on some occasions, it stalls the build as each such "failed" lookup takes a long time hence my motivation to solve this problem. Regarding nifi: I looked at https://repo1.maven.org/maven2/org/apache/nifi/nifi-nar-maven-plugin/1.5.0/nifi-nar-maven-plugin-1.5.0.pom, and I didn't see any repository mentioned there. If I want to improve Maven, I need to change that WARN to include the repository URL instead of writing maven-default-http-blocker. Is it possible? On Tue, Jan 9, 2024 at 1:40 PM Stefan CORDES wrote: > Hi Asaf, > with > > mvn.cmd install -DskipTests -Dcheckstyle.skip=true -Dspotbugs.skip=true > -Dmaven.repo.local=c:\temp\m2-repo -s c:\temp\empty-settings.xml > > I receive the same warnings > > [INFO] --- nifi-nar:1.5.0:nar (default-nar) @ tiered-storage-jcloud --- > [INFO] Copying pulsar-common.jar to > C:\java\_head\pulsar\tiered-storage\jcloud\target\classes\META-INF\bundled-dependencies\pulsar-common-3.3.0-SNAPSHOT.jar > [INFO] Copying jclouds-shaded.jar to > C:\java\_head\pulsar\tiered-storage\jcloud\target\classes\META-INF\bundled-dependencies\jclouds-shaded-3.3.0-SNAPSHOT.jar > [INFO] Generating documentation for NiFi extensions in the NAR... > [WARNING] Could not transfer metadata > net.minidev:json-smart/maven-metadata.xml from/to > maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for > repositories: [glassfish-repository ( > http://download.java.net/maven/glassfish, default, releases+snapshots)] > > but build continues and finishes successfully. > > Seems to be in nifi-nar plugin. > > Gruß, > Stefan > > -Original Message- > From: Asaf Mesika > Sent: Sunday, January 7, 2024 12:22 PM > To: Maven Users List > Subject: Re: Question about HTTP blocking WARN > > Hi Stefan, > > Not sure I follow. Are you saying you ran the command with a local > temporary .m2 and didn't see any of the warnings I got? > > I looked at > > https://repo1.maven.org/maven2/org/apache/nifi/nifi-nar-maven-plugin/1.5.0/nifi-nar-maven-plugin-1.5.0.pom > , > and I didn't see any repository mentioned there. > > Is my only option for finding the root cause for this warning is altering > Maven's code to emit the repository, causing this message to appear? Or > does another option exist? > > > > On Thu, Jan 4, 2024 at 8:50 PM Stefan CORDES > wrote: > > > Hi Asaf, > > > > Ok, now I could build with > > mvn clean install -DskipTests -Dmaven.repo.local=c:\temp\m2-repo > > > > And even I do not have configured the apache.snapshot in > > $MAVEN_HOME\conf\settings.xml or ./.m2/settings.xml the > > > > Build is trying to download > > > > Downloading from apache.snapshots: > > http://repository.apache.org/snapshots/io/grpc/grpc-api/maven-metadata > > .xml > > apache.snapshot > > > > This is happening in the context of > > [INFO] org.apache.maven.cli.event.ExecutionEventLogger - --- > > nifi-nar-maven-plugin:1.5.0:nar (default-nar) @ tiered-storage-jcloud > > --- > > > > > > > > And so I guess the > > > > nifi-nar-maven-plugin > > > > has some "build-in" repositories which refer to http:// > > > > > > Gruß, > > Stefan > > > > Gruß, > > Stefan > > > > -Original Message- > > From: Asaf Mesika > > Sent: Thursday, January 4, 2024 5:06 PM > > To: Maven Users List > > Subject: Re: Question about HTTP blocking WARN > > > > I appreciate the help, Stefan. > > > > I tried deleting the directories you mentioned, but I still got the > > same warnings regarding "maven-default-http-blocker". > > > > I did the following for a clean slate: > > 1. git clone g...@github.com:apache/pulsar.git pulsar-mvn-issue 2. cd > > pulsar-mvn-issue 3. ./mvnw clean install -DskipTests > > -Dmaven.repo.local=/Users/asaf/streamnative/sandbox/temp-m2 > > > > This uses an empty .m2 directory. > > > > In less than a few minutes, I get the following warnings: > > > > Downloading from maven-default-http-blocker: > > http://0.0.0.0/io/grpc/grpc-api/maven-metadata.xml > > ... > > Downloaded from jcenter: > > https://jcenter.bintray.com/io/grpc/grpc-api/maven-metadata.xml (3.6 > > kB at > > 8.3 kB/s) > > Progress (1): 600 B > > > > Downloaded from sonatype-nexus-snapshots: > > > > https://oss.sonatype.org/content/repositories/snapshots/io/grpc/grpc-a > > pi/maven-metadata.xml > > (600 B at 525 B/s) > > [WARNING] Could not transfer metadata > > io.grpc:grpc-api/maven-metadata.xml > > from/to maven-default-http-blocke
Re: Question about HTTP blocking WARN
Hi Stefan, Not sure I follow. Are you saying you ran the command with a local temporary .m2 and didn't see any of the warnings I got? I looked at https://repo1.maven.org/maven2/org/apache/nifi/nifi-nar-maven-plugin/1.5.0/nifi-nar-maven-plugin-1.5.0.pom, and I didn't see any repository mentioned there. Is my only option for finding the root cause for this warning is altering Maven's code to emit the repository, causing this message to appear? Or does another option exist? On Thu, Jan 4, 2024 at 8:50 PM Stefan CORDES wrote: > Hi Asaf, > > Ok, now I could build with > mvn clean install -DskipTests -Dmaven.repo.local=c:\temp\m2-repo > > And even I do not have configured the apache.snapshot in > $MAVEN_HOME\conf\settings.xml or ./.m2/settings.xml the > > Build is trying to download > > Downloading from apache.snapshots: > http://repository.apache.org/snapshots/io/grpc/grpc-api/maven-metadata.xml > apache.snapshot > > This is happening in the context of > [INFO] org.apache.maven.cli.event.ExecutionEventLogger - --- > nifi-nar-maven-plugin:1.5.0:nar (default-nar) @ tiered-storage-jcloud --- > > > > And so I guess the > > nifi-nar-maven-plugin > > has some "build-in" repositories which refer to http:// > > > Gruß, > Stefan > > Gruß, > Stefan > > -Original Message- > From: Asaf Mesika > Sent: Thursday, January 4, 2024 5:06 PM > To: Maven Users List > Subject: Re: Question about HTTP blocking WARN > > I appreciate the help, Stefan. > > I tried deleting the directories you mentioned, but I still got the same > warnings regarding "maven-default-http-blocker". > > I did the following for a clean slate: > 1. git clone g...@github.com:apache/pulsar.git pulsar-mvn-issue 2. cd > pulsar-mvn-issue 3. ./mvnw clean install -DskipTests > -Dmaven.repo.local=/Users/asaf/streamnative/sandbox/temp-m2 > > This uses an empty .m2 directory. > > In less than a few minutes, I get the following warnings: > > Downloading from maven-default-http-blocker: > http://0.0.0.0/io/grpc/grpc-api/maven-metadata.xml > ... > Downloaded from jcenter: > https://jcenter.bintray.com/io/grpc/grpc-api/maven-metadata.xml (3.6 kB at > 8.3 kB/s) > Progress (1): 600 B > > Downloaded from sonatype-nexus-snapshots: > > https://oss.sonatype.org/content/repositories/snapshots/io/grpc/grpc-api/maven-metadata.xml > (600 B at 525 B/s) > [WARNING] Could not transfer metadata io.grpc:grpc-api/maven-metadata.xml > from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for > http://0.0.0.0/io/grpc/grpc-api/maven-metadata.xml > Downloading from central: > > https://repo.maven.apache.org/maven2/io/grpc/grpc-api/1.51.0/grpc-api-1.51.0.pom > Progress (1): 2.0 kB > > Downloaded from central: > > https://repo.maven.apache.org/maven2/io/grpc/grpc-api/1.51.0/grpc-api-1.51.0.pom > (2.0 kB at 13 kB/s) > Downloading from central: > > https://repo.maven.apache.org/maven2/io/grpc/grpc-context/1.51.0/grpc-context-1.51.0.pom > ... > Downloading from maven-default-http-blocker: > http://0.0.0.0/io/grpc/grpc-core/maven-metadata.xml > ... > Downloaded from sonatype-nexus-snapshots: > > https://oss.sonatype.org/content/repositories/snapshots/io/grpc/grpc-core/maven-metadata.xml > (906 B at 2.5 kB/s) > Downloaded from jcenter: > https://jcenter.bintray.com/io/grpc/grpc-core/maven-metadata.xml (5.2 kB > at > 12 kB/s) > [WARNING] Could not transfer metadata io.grpc:grpc-core/maven-metadata.xml > from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for > http://0.0.0.0/io/grpc/grpc-core/maven-metadata.xml > Downloading from central: > > https://repo.maven.apache.org/maven2/io/grpc/grpc-core/1.50.2/grpc-core-1.50.2.pom > Progress (1): 2.5 kB > > Downloaded from central: > > https://repo.maven.apache.org/maven2/io/grpc/grpc-core/1.50.2/grpc-core-1.50.2.pom > (2.5 kB at 17 kB/s) > [WARNING] io.grpc:grpc-api/maven-metadata.xmlfailed to transfer from > http://0.0.0.0/ during a previous attempt. This failure was cached in the > local repository and resolution will not be reattempted until the update > interval of maven-default-http-blocker has elapsed or updates are forced. > Original error: Could not transfer metadata > io.grpc:grpc-api/maven-metadata.xml from/to maven-default-http-blocker ( > http://0.0.0.0/): transfer failed for > http://0.0.0.0/io/grpc/grpc-api/maven-metadata.xml > Downloading from vertx-snapshots-repository: > > https://s01.oss.sonatype.org/content/repositories/snapshots/io/grpc/grpc-api/maven-metadata.xml > Downloading from central: > > https://repo.maven.apache.org/maven2/io/grpc/grpc-api/1.50.2/grpc-api-1.50.2.pom > Progress (1): 2.0 kB > > Downl
Re: Question about HTTP blocking WARN
I appreciate the help, Stefan. I tried deleting the directories you mentioned, but I still got the same warnings regarding "maven-default-http-blocker". I did the following for a clean slate: 1. git clone g...@github.com:apache/pulsar.git pulsar-mvn-issue 2. cd pulsar-mvn-issue 3. ./mvnw clean install -DskipTests -Dmaven.repo.local=/Users/asaf/streamnative/sandbox/temp-m2 This uses an empty .m2 directory. In less than a few minutes, I get the following warnings: Downloading from maven-default-http-blocker: http://0.0.0.0/io/grpc/grpc-api/maven-metadata.xml ... Downloaded from jcenter: https://jcenter.bintray.com/io/grpc/grpc-api/maven-metadata.xml (3.6 kB at 8.3 kB/s) Progress (1): 600 B Downloaded from sonatype-nexus-snapshots: https://oss.sonatype.org/content/repositories/snapshots/io/grpc/grpc-api/maven-metadata.xml (600 B at 525 B/s) [WARNING] Could not transfer metadata io.grpc:grpc-api/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/io/grpc/grpc-api/maven-metadata.xml Downloading from central: https://repo.maven.apache.org/maven2/io/grpc/grpc-api/1.51.0/grpc-api-1.51.0.pom Progress (1): 2.0 kB Downloaded from central: https://repo.maven.apache.org/maven2/io/grpc/grpc-api/1.51.0/grpc-api-1.51.0.pom (2.0 kB at 13 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/io/grpc/grpc-context/1.51.0/grpc-context-1.51.0.pom ... Downloading from maven-default-http-blocker: http://0.0.0.0/io/grpc/grpc-core/maven-metadata.xml ... Downloaded from sonatype-nexus-snapshots: https://oss.sonatype.org/content/repositories/snapshots/io/grpc/grpc-core/maven-metadata.xml (906 B at 2.5 kB/s) Downloaded from jcenter: https://jcenter.bintray.com/io/grpc/grpc-core/maven-metadata.xml (5.2 kB at 12 kB/s) [WARNING] Could not transfer metadata io.grpc:grpc-core/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/io/grpc/grpc-core/maven-metadata.xml Downloading from central: https://repo.maven.apache.org/maven2/io/grpc/grpc-core/1.50.2/grpc-core-1.50.2.pom Progress (1): 2.5 kB Downloaded from central: https://repo.maven.apache.org/maven2/io/grpc/grpc-core/1.50.2/grpc-core-1.50.2.pom (2.5 kB at 17 kB/s) [WARNING] io.grpc:grpc-api/maven-metadata.xmlfailed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata io.grpc:grpc-api/maven-metadata.xml from/to maven-default-http-blocker ( http://0.0.0.0/): transfer failed for http://0.0.0.0/io/grpc/grpc-api/maven-metadata.xml Downloading from vertx-snapshots-repository: https://s01.oss.sonatype.org/content/repositories/snapshots/io/grpc/grpc-api/maven-metadata.xml Downloading from central: https://repo.maven.apache.org/maven2/io/grpc/grpc-api/1.50.2/grpc-api-1.50.2.pom Progress (1): 2.0 kB Downloaded from central: https://repo.maven.apache.org/maven2/io/grpc/grpc-api/1.50.2/grpc-api-1.50.2.pom (2.0 kB at 13 kB/s) Downloading from central: https://repo.maven.apache.org/maven2/io/grpc/grpc-context/1.50.2/grpc-context-1.50.2.pom Progress (1): 1.2 kB Are you not getting those warnings? My main issue here is: How do I know which repository is blocked due to lack of https? Once I know, I can search for it in the pom.xml and change it, right? I know that I don't have any settings.xml personally that can affect it, so it must be in the pom.xml Thanks! Asaf On Thu, Jan 4, 2024 at 12:53 PM Stefan CORDES wrote: > Hi Asaf, > > my build (branch * master) works. > > Try deleting > ~/.m2/repository/org/mongodb/bson > and > ~/.m2/repository/org/testcontainers > > (Maybe in the past you had a sonatype-nexus-snapshots via "http://; in > one of your settings.xml or pom.xml) > > > Gruß, > Stefan > > -Original Message- > From: Asaf Mesika > Sent: Tuesday, January 2, 2024 1:25 PM > To: Maven Users List > Subject: Re: Question about HTTP blocking WARN > > Here is the content of the file you wrote: > > ➜ pulsar git:(pip-323-implementation) ✗ cat > ~/.m2/repository/org/mongodb/bson/4.4.2-SNAPSHOT/_remote.repositories > #NOTE: This is a Maven Resolver internal implementation file, its format > can be changed without prior notice. > #Wed Feb 08 16:24:48 IST 2023 > bson-4.4.2-20220207.232016-3.pom>sonatype-nexus-snapshots= > ➜ pulsar git:(pip-323-implementation) ✗ > > I don't have a MAVEN_HOME env variable > > ➜ pulsar git:(pip-323-implementation) ✗ echo $MAVEN_HOME > > ➜ pulsar git:(pip-323-implementation) ✗ > > Also no settings.xml file > > ➜ pulsar git:(pip-323-implementation) ✗ cat ~/.m2/settings.xml > cat: /Users/asaf/.m2/settings.xml: No such file or directory > > In my buil
Re: Question about HTTP blocking WARN
Here is the content of the file you wrote: ➜ pulsar git:(pip-323-implementation) ✗ cat ~/.m2/repository/org/mongodb/bson/4.4.2-SNAPSHOT/_remote.repositories #NOTE: This is a Maven Resolver internal implementation file, its format can be changed without prior notice. #Wed Feb 08 16:24:48 IST 2023 bson-4.4.2-20220207.232016-3.pom>sonatype-nexus-snapshots= ➜ pulsar git:(pip-323-implementation) ✗ I don't have a MAVEN_HOME env variable ➜ pulsar git:(pip-323-implementation) ✗ echo $MAVEN_HOME ➜ pulsar git:(pip-323-implementation) ✗ Also no settings.xml file ➜ pulsar git:(pip-323-implementation) ✗ cat ~/.m2/settings.xml cat: /Users/asaf/.m2/settings.xml: No such file or directory In my build output the module is: [INFO] --- maven-install-plugin:3.1.0:install (default-install) @ pulsar-io-rabbitmq --- [INFO] Installing /Users/asaf/streamnative/pulsar/pulsar-io/rabbitmq/pom.xml to /Users/asaf/.m2/repository/org/apache/pulsar/pulsar-io-rabbitmq/3.2.0-SNAPSHOT/pulsar-io-rabbitmq-3.2.0-SNAPSHOT.pom [INFO] Installing /Users/asaf/streamnative/pulsar/pulsar-io/rabbitmq/target/pulsar-io-rabbitmq-3.2.0-SNAPSHOT.nar to /Users/asaf/.m2/repository/org/apache/pulsar/pulsar-io-rabbitmq/3.2.0-SNAPSHOT/pulsar-io-rabbitmq-3.2.0-SNAPSHOT.jar [WARNING] Could not transfer metadata org.mongodb:bson:4.4.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/org/mongodb/bson/4.4.1-SNAPSHOT/maven-metadata.xml [WARNING] org.mongodb:bson:4.4.1-SNAPSHOT/maven-metadata.xmlfailed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata org.mongodb:bson:4.4.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/org/mongodb/bson/4.4.1-SNAPSHOT/maven-metadata.xml Downloading from maven-default-http-blocker: http://0.0.0.0/org/mongodb/bson/4.4.2-SNAPSHOT/maven-metadata.xml [WARNING] Could not transfer metadata org.mongodb:bson:4.4.2-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/org/mongodb/bson/4.4.2-SNAPSHOT/maven-metadata.xml I run it as `./mvnw clean install -DskipTests` On Wed, Dec 13, 2023 at 9:24 PM Stefan CORDES wrote: > Hi Asaf, > normally you should not unblock http:// repositories as all artifacts are > (should be) available via https:// > > I build latest master from g...@github.com:apache/pulsar.git and up to > module > Building Pulsar IO :: Canal 3.2.0-SNAPSHOT [75/134] > (later it failed locally) > > I did not see maven-default-http-blocker here. > > Maybe in your local repository > ~/.m2/repository/org/mongodb/bson/4.4.2-SNAPSHOT > the _remote.repositories file contains outdated http:// repository > references? > > Additionally you can check your personal ~/.m2/settings.xml and > maven_home/conf/settings.xml > not having any with http:// and not any with http:// > > If still facing maven-default-http-blocker: which module of pulsar build > tries to download ? > > Gruß, > Stefan > > -Original Message- > From: Asaf Mesika > Sent: Wednesday, December 13, 2023 7:41 PM > To: Maven Users List > Subject: Re: Question about HTTP blocking WARN > > How do I unblock ? I searched in .mvn directory and found nothing. I don’t > have a settings file > > On Wed, 13 Dec 2023 at 17:50 > wrote: > > > Sorry, I failed to read your email carefully enough. > > Idea: try un-blocking HTTP, and see where it ends up downloading > > things from. > > > > -Original Message- > > From: mark.yagnatin...@barclays.com.INVALID > > > > Sent: Wednesday, December 13, 2023 10:47 AM > > To: users@maven.apache.org > > Subject: RE: Question about HTTP blocking WARN > > > > > > CAUTION: This email originated from outside our organisation - > > mark.yagnatin...@barclays.com.INVALID Do not click on links, open > > attachments, or respond unless you recognize the sender and can > > validate the content is safe. > > See release notes for 3.8.1: > > > > https://clicktime.symantec.com/15sM687dBQmsAHdZzRg2R?h=vGmJxLiSHcBmfng > > K9X2tEIMgJvGX3EQZ2p_ZA8IE8vo==https://maven.apache.org/docs/3.8.1/re > > lease-notes.html > > > > -Original Message- > > From: Asaf Mesika > > Sent: Wednesday, December 13, 2023 6:07 AM > > To: users@maven.apache.org > > Subject: Question about HTTP blocking WARN > > > > > > CAUTION: This email originated from outside our organisation - > > asaf.mes...@gmail.com Do no
Re: Question about HTTP blocking WARN
How do I unblock ? I searched in .mvn directory and found nothing. I don’t have a settings file On Wed, 13 Dec 2023 at 17:50 wrote: > Sorry, I failed to read your email carefully enough. > Idea: try un-blocking HTTP, and see where it ends up downloading things > from. > > -Original Message- > From: mark.yagnatin...@barclays.com.INVALID > > Sent: Wednesday, December 13, 2023 10:47 AM > To: users@maven.apache.org > Subject: RE: Question about HTTP blocking WARN > > > CAUTION: This email originated from outside our organisation - > mark.yagnatin...@barclays.com.INVALID Do not click on links, open > attachments, or respond unless you recognize the sender and can validate > the content is safe. > See release notes for 3.8.1: > > https://clicktime.symantec.com/15sM687dBQmsAHdZzRg2R?h=vGmJxLiSHcBmfngK9X2tEIMgJvGX3EQZ2p_ZA8IE8vo==https://maven.apache.org/docs/3.8.1/release-notes.html > > -Original Message- > From: Asaf Mesika > Sent: Wednesday, December 13, 2023 6:07 AM > To: users@maven.apache.org > Subject: Question about HTTP blocking WARN > > > CAUTION: This email originated from outside our organisation - > asaf.mes...@gmail.com Do not click on links, open attachments, or respond > unless you recognize the sender and can validate the content is safe. > Hi, > > I'm running Apache Maven 3.8.5 (using Maven Wrapper) for building Apache > Pulsar. > > I get the following WARN: > > [WARNING] Could not transfer metadata > org.mongodb:bson:4.4.1-SNAPSHOT/maven-metadata.xml from/to > maven-default-http-blocker (http://0.0.0.0/): transfer failed for > http://0.0.0.0/org/mongodb/bson/4.4.1-SNAPSHOT/maven-metadata.xml > [WARNING] org.mongodb:bson:4.4.1-SNAPSHOT/maven-metadata.xmlfailed to > transfer from http://0.0.0.0/ during a previous attempt. This failure was > cached in the local repository and resolution will not be reattempted until > the update interval of maven-default-http-blocker has elapsed or updates > are forced. Original error: Could not transfer metadata > org.mongodb:bson:4.4.1-SNAPSHOT/maven-metadata.xml from/to > maven-default-http-blocker (http://0.0.0.0/): transfer failed for > http://0.0.0.0/org/mongodb/bson/4.4.1-SNAPSHOT/maven-metadata.xml > Downloading from maven-default-http-blocker: > http://0.0.0.0/org/mongodb/bson/4.4.2-SNAPSHOT/maven-metadata.xml > [WARNING] Could not transfer metadata > org.mongodb:bson:4.4.2-SNAPSHOT/maven-metadata.xml from/to > maven-default-http-blocker (http://0.0.0.0/): transfer failed for > http://0.0.0.0/org/mongodb/bson/4.4.2-SNAPSHOT/maven-metadata.xml > [WARNING] org.mongodb:bson:4.4.2-SNAPSHOT/maven-metadata.xmlfailed to > transfer from http://0.0.0.0/ during a previous attempt. This failure was > cached in the local repository and resolution will not be reattempted until > the update interval of maven-default-http-blocker has elapsed or updates > are forced. Original error: Could not transfer metadata > org.mongodb:bson:4.4.2-SNAPSHOT/maven-metadata.xml from/to > maven-default-http-blocker (http://0.0.0.0/): transfer failed for > http://0.0.0.0/org/mongodb/bson/4.4.2-SNAPSHOT/maven-metadata.xml > Downloading from maven-default-http-blocker: > http://0.0.0.0/org/mongodb/bson/4.5.0-SNAPSHOT/maven-metadata.xml > [WARNING] Could not transfer metadata > org.mongodb:bson:4.4.2-SNAPSHOT/maven-metadata.xml from/to > maven-default-http-blocker (http://0.0.0.0/): transfer failed for > http://0.0.0.0/org/mongodb/bson/4.4.2-SNAPSHOT/maven-metadata.xml > [ > > I can't understand how to understand which repository in my pom.xml has an > http and not https repository based on this WARN message. > > I searched for over any pom.xml file and didn't find any > http repository. > > Any help would be greatly appreciated. This is the latest master branch of > pulsar: > https://clicktime.symantec.com/15sLvTizaiLPdE4JXAvu7?h=MSjyi1VB4cPbNJsglaLsboIIC2w3PxVFwT0C3b3tJjE==https://clicktime.symantec.com/15sM1HvLio6GkLoeSsGso?h=a4l_3miTQ9Jpp9kBhV4g1A6nK9z3Xc4ThYeLnyNM6NM==https://github.com/apache/pulsar > > Thanks, > > Asaf > > This message is for information purposes only. It is not a recommendation, > advice, offer or solicitation to buy or sell a product or service, nor an > official confirmation of any transaction. It is directed at persons who are > professionals and is intended for the recipient(s) only. It is not directed > at retail customers. This message is subject to the terms at: > https://clicktime.symantec.com/15sMWH63UVBqE1mBiDfmX?h=DIqE4zifGAeQprKQUyrnrW7RczY3fI3DZ9CksSTeo3A==https://www.cib.barclays/disclosures/web-and-email-disclaimer.html. > > > For important disclosures, please see: > https://clicktime.symantec.com/15sMRStm1sWEp4wGAfGcu?h=
Question about HTTP blocking WARN
Hi, I'm running Apache Maven 3.8.5 (using Maven Wrapper) for building Apache Pulsar. I get the following WARN: [WARNING] Could not transfer metadata org.mongodb:bson:4.4.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/org/mongodb/bson/4.4.1-SNAPSHOT/maven-metadata.xml [WARNING] org.mongodb:bson:4.4.1-SNAPSHOT/maven-metadata.xmlfailed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata org.mongodb:bson:4.4.1-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/org/mongodb/bson/4.4.1-SNAPSHOT/maven-metadata.xml Downloading from maven-default-http-blocker: http://0.0.0.0/org/mongodb/bson/4.4.2-SNAPSHOT/maven-metadata.xml [WARNING] Could not transfer metadata org.mongodb:bson:4.4.2-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/org/mongodb/bson/4.4.2-SNAPSHOT/maven-metadata.xml [WARNING] org.mongodb:bson:4.4.2-SNAPSHOT/maven-metadata.xmlfailed to transfer from http://0.0.0.0/ during a previous attempt. This failure was cached in the local repository and resolution will not be reattempted until the update interval of maven-default-http-blocker has elapsed or updates are forced. Original error: Could not transfer metadata org.mongodb:bson:4.4.2-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/org/mongodb/bson/4.4.2-SNAPSHOT/maven-metadata.xml Downloading from maven-default-http-blocker: http://0.0.0.0/org/mongodb/bson/4.5.0-SNAPSHOT/maven-metadata.xml [WARNING] Could not transfer metadata org.mongodb:bson:4.4.2-SNAPSHOT/maven-metadata.xml from/to maven-default-http-blocker (http://0.0.0.0/): transfer failed for http://0.0.0.0/org/mongodb/bson/4.4.2-SNAPSHOT/maven-metadata.xml [ I can't understand how to understand which repository in my pom.xml has an http and not https repository based on this WARN message. I searched for over any pom.xml file and didn't find any http repository. Any help would be greatly appreciated. This is the latest master branch of pulsar: https://github.com/apache/pulsar Thanks, Asaf
Re: [m2e-users] Maven, Eclipse, Nexus, Perforce, Team City, Oh My!
Cool article. You are correct: Maven has a very steep learning curve. M2E makes it easier only partially, but still requires an advance Maven Admin on the team/organization. I wonder: Was the Sonatype book helpful? When I first started, it didn't exist yet and I had to learn only from another person who installed Maven for a living. Regarding you setup depicted in the article, here are a few comments: Why did you put your Maven repository under P:\supercool\Maven\repository and not stick with the convention of ~/.m2/repository (I don't remember the similar path in Windows, but it should be under the User Profile directory)? Why did you not put your settings file as convention goes: ~/.m2/settings.xml? In our team, we softlinked ~/.m2/settings.xml to a source controlled directory everyone has: ~/work/acme/build, thus spreading a new company configuration easily. Regarding Perforce - Why not git? Git is free, amazingly fast, awfully intuitive, and has integration in all IDEs (Unfortunately best integration is in IntelliJ). In my professional life I've used many tools: CA's CCC/Harvest, IBM's ClearCase, Subversion, Mercurial, and git. The best tool I've found was git. One of my favorite feature is the merge - simply outstanding compared to any other tool. -- Asaf Mesika Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On יום שישי 5 אוגוסט 2011 at 08:35, Eric Kolotyluk wrote: OK, this is my meager first attempt to give something back to the community... http://docs.codehaus.org/display/MAVENUSER/Maven%2C+Eclipse%2C+Nexus%2C+Perforce%2C+Team+City%2C+Oh+My! http://docs.codehaus.org/display/MAVENUSER/Maven%2C+Eclipse%2C+Nexus%2C+Perforce%2C+Team+City%2C+Oh+My%21 Send e-mail to my personal address, or flame/commend me in the mailing lists - I'm thick skinned, but receptive of praise. The point is, I really love Maven, but I want to see it improve, and this is my way of going about it. I hope hope to add more experience to this in the future, so comments and criticism are appreciated. Cheers, Eric ___ m2e-users mailing list m2e-us...@eclipse.org (mailto:m2e-us...@eclipse.org) https://dev.eclipse.org/mailman/listinfo/m2e-users
Lack of documentation for Maven 2.x
Hi, The project I'm working on currently using ANT for build deployment. I'm currently reviewing Maven as a better alternative for this tasks. I find it extermely difficult to answer a simple question: What Maven gives you which ANT, coupled with WSAD (Web Sphere Application Developer) , does not? The reason is that I can't find what each maven plugin does exactly and there's no one central user guide for Maven. The documentation is scattered all across the internet. Thank you, Asaf
