The plugin itself also has lots of dependencies. $ mvn dependency:resolve-plugins -DincludeArtifactIds=nifi-nar-maven-plugin
org.apache.nifi:nifi-nar-maven-plugin:maven-plugin:1.5.0:runtime org.apache.nifi:nifi-nar-maven-plugin:jar:1.5.0 org.apache.maven:maven-archiver:jar:3.6.0 org.codehaus.plexus:plexus-io:jar:3.4.0 javax.inject:javax.inject:jar:1 org.codehaus.plexus:plexus-archiver:jar:4.4.0 org.apache.commons:commons-compress:jar:1.21 org.iq80.snappy:snappy:jar:0.4 org.tukaani:xz:jar:1.9 org.codehaus.plexus:plexus-utils:jar:3.4.2 org.codehaus.plexus:plexus-interpolation:jar:1.26 org.apache.maven:maven-plugin-api:jar:3.9.0 org.apache.maven:maven-model:jar:3.9.0 org.eclipse.sisu:org.eclipse.sisu.plexus:jar:0.3.5 javax.annotation:javax.annotation-api:jar:1.2 org.eclipse.sisu:org.eclipse.sisu.inject:jar:0.3.5 org.codehaus.plexus:plexus-classworlds:jar:2.6.0 org.apache.maven:maven-artifact:jar:3.9.0 org.apache.commons:commons-lang3:jar:3.8.1 org.apache.maven:maven-compat:jar:3.9.0 org.apache.maven:maven-model-builder:jar:3.9.0 org.apache.maven:maven-builder-support:jar:3.9.0 org.apache.maven:maven-settings:jar:3.9.0 org.apache.maven:maven-settings-builder:jar:3.9.0 org.codehaus.plexus:plexus-sec-dispatcher:jar:2.0 org.codehaus.plexus:plexus-cipher:jar:2.0 org.apache.maven:maven-core:jar:3.9.0 org.apache.maven.resolver:maven-resolver-spi:jar:1.9.4 com.google.inject:guice:jar:5.1.0 aopalliance:aopalliance:jar:1.0 com.google.guava:guava:jar:30.1-jre com.google.guava:failureaccess:jar:1.0.1 org.apache.maven:maven-resolver-provider:jar:3.9.0 org.apache.maven:maven-repository-metadata:jar:3.9.0 org.apache.maven.resolver:maven-resolver-api:jar:1.9.4 org.apache.maven.resolver:maven-resolver-util:jar:1.9.4 org.apache.maven.resolver:maven-resolver-impl:jar:1.9.4 org.apache.maven.resolver:maven-resolver-named-locks:jar:1.9.4 org.codehaus.plexus:plexus-component-annotations:jar:2.1.0 org.apache.maven.wagon:wagon-provider-api:jar:3.5.3 org.apache.maven.plugins:maven-dependency-plugin:maven-plugin:3.5.0 commons-io:commons-io:jar:2.11.0 org.apache.maven.shared:maven-dependency-analyzer:jar:1.13.0 org.ow2.asm:asm:jar:9.3 org.apache.maven.shared:maven-common-artifact-filters:jar:3.3.2 org.apache.maven.shared:maven-artifact-transfer:jar:0.13.1 org.apache.maven.shared:maven-shared-utils:jar:3.3.4 org.apache.commons:commons-collections4:jar:4.2 org.sonatype.plexus:plexus-build-api:jar:0.0.7 org.apache.maven.shared:maven-dependency-tree:jar:3.2.1 org.eclipse.aether:aether-util:jar:1.0.0.v20140518 org.eclipse.aether:aether-api:jar:1.0.0.v20140518 org.slf4j:slf4j-api:jar:1.7.36 org.apache.maven.plugins:maven-jar-plugin:jar:3.3.0 org.apache.maven.shared:file-management:jar:3.1.0 -- Alexander Kriegisch https://scrum-master.de Asaf Mesika schrieb am 10.01.2024 02:48 (GMT +07:00): > 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 > <stefan.cor...@canda.com.invalid> 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 <asaf.mes...@gmail.com> >> Sent: Sunday, January 7, 2024 12:22 PM >> To: Maven Users List <users@maven.apache.org> >> 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 >> <stefan.cor...@canda.com.invalid> >> 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 <asaf.mes...@gmail.com> >> > Sent: Thursday, January 4, 2024 5:06 PM >> > To: Maven Users List <users@maven.apache.org> >> > 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-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-c >> > ore/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-cor >> > e-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-cor >> > e-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/gr >> > pc-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 >> > <stefan.cor...@canda.com.invalid> >> > 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 <asaf.mes...@gmail.com> >> > > Sent: Tuesday, January 2, 2024 1:25 PM >> > > To: Maven Users List <users@maven.apache.org> >> > > 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.repositorie >> > > s >> > > #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- >> > > ra >> > > bbitmq-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 >> > > <stefan.cor...@canda.com.invalid> >> > > 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 <repository> with >> > > > http:// and not any <mirror> with http:// >> > > > >> > > > If still facing maven-default-http-blocker: which module of pulsar >> > > > build tries to download ? >> > > > >> > > > Gruß, >> > > > Stefan >> > > > >> > > > -----Original Message----- >> > > > From: Asaf Mesika <asaf.mes...@gmail.com> >> > > > Sent: Wednesday, December 13, 2023 7:41 PM >> > > > To: Maven Users List <users@maven.apache.org> >> > > > 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 >> > > > <mark.yagnatin...@barclays.com.invalid> >> > > > 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 >> > > > > <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=vGmJxLiSH >> > > > > cB >> > > > > mf >> > > > > ng >> > > > > K9X2tEIMgJvGX3EQZ2p_ZA8IE8vo=&u=https://maven.apache.org/docs/3.8. >> > > > > 1/ >> > > > > re >> > > > > lease-notes.html >> > > > > >> > > > > -----Original Message----- >> > > > > From: Asaf Mesika <asaf.mes...@gmail.com> >> > > > > 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.xm >> > > > > l [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.xm >> > > > > l Downloading from maven-default-http-blocker: >> > > > > http://0.0.0.0/org/mongodb/bson/4.4.2-SNAPSHOT/maven-metadata.xm >> > > > > l [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.xm >> > > > > l [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.xm >> > > > > l Downloading from maven-default-http-blocker: >> > > > > http://0.0.0.0/org/mongodb/bson/4.5.0-SNAPSHOT/maven-metadata.xm >> > > > > l [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.xm >> > > > > l >> > > > > [ >> > > > > >> > > > > 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 <repositories> 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=MSjyi1VB4 >> > > > > cP >> > > > > bN >> > > > > Js >> > > > > glaLsboIIC2w3PxVFwT0C3b3tJjE=&u=https://clicktime.symantec.com/1 >> > > > > 5s >> > > > > M1 >> > > > > Hv >> > > > > >> > Lio6GkLoeSsGso?h=a4l_3miTQ9Jpp9kBhV4g1A6nK9z3Xc4ThYeLnyNM6NM=&u=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=DIqE4zifGAe >> > > > Qp >> > > > rK >> > > > QUyrnrW7RczY3fI3DZ9CksSTeo3A=&u=https://www.cib.barclays/disclosur >> > > > es >> > > > /w >> > > > eb-and-email-disclaimer.html >> > > > . >> > > > > >> > > > > >> > > > > For important disclosures, please see: >> > > > > https://clicktime.symantec.com/15sMRStm1sWEp4wGAfGcu?h=o9osYrwRO >> > > > > 8N >> > > > > k9 >> > > > > pR >> > > > > hDXC5l0HduDMhhY22d5g2I2QVwuc=&u=https://www.cib.barclays/disclos >> > > > > ur es /s ales-and-trading-disclaimer.html regarding marketing >> > > > > commentary from Barclays Sales and/or Trading desks, who are >> > > > > active market participants; >> > > > > https://clicktime.symantec.com/15sMAxJue2TTaETVXz5B3?h=_YvyWi2Jt >> > > > > vO >> > > > > 3g >> > > > > Sg >> > > > > RRKCpC0ImVYSd52rWl07eYNFwfaY=&u=https://www.cib.barclays/disclos >> > > > > ur es /b arclays-global-markets-disclosures.html >> > > > > regarding our standard terms for Barclays Corporate and >> > > > > Investment Bank where we trade with you in >> > > > > principal-to-principal wholesale markets transactions; and in >> > > > > respect to Barclays Research, including disclosures relating to >> specific issuers, see: >> > > > > https://clicktime.symantec.com/15sLvTj4GBQgLPyiuJsjB?h=pn27ZplPa >> > > > > d4 >> > > > > fD >> > > > > kL >> > > > > _Y-vhW5C-UZY3p3ndCdE2f_AAXOY=&u=http://publicresearch.barclays.c >> > > > > om >> > > > > . >> > > > > ________________________________________________________________ >> > > > > __ >> > > > > __ >> > > > > __ >> > > > > ____________ >> > > > > >> > > > > If you are incorporated or operating in Australia, read these >> > > > > important >> > > > > disclosures: >> > > > > https://clicktime.symantec.com/15sMFnWC6e93zBHR5YUKf?h=i4IUmiJ2N >> > > > > lz >> > > > > Fe >> > > > > ly >> > > > > lA6v1tNqtBTACpar8CD5q9c1kTys=&u=https://www.cib.barclays/disclos >> > > > > ur es /i mportant-disclosures-asia-pacific.html >> > > > > . >> > > > > >> > > > > ________________________________________________________________ >> > > > > __ __ __ ____________ For more details about how we use personal >> > > > > information, see our privacy >> > > > > notice: >> > > > > >> > > > https://clicktime.symantec.com/15sMLchUZFpeQ87Ld6sUH?h=KQNjiUfwPYD >> > > > Xx >> > > > 8r >> > > > v0cECSsVrfzUJEdSh5qAIPibF__E=&u=https://www.cib.barclays/disclosur >> > > > es >> > > > /p >> > > > ersonal-information-use.html >> > > > . >> > > > > >> > > > > >> > > > > ________________________________________________________________ >> > > > > __ >> > > > > __ >> > > > > __ >> > > > > ____________ >> > > > > B >> > > > > KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK >> > > > > KK >> > > > > KK >> > > > > CB >> > > > > [ X ܚX K K[XZ[ >> > > > > \ \ ][ X ܚX P X] [ \ X K ܙ B ܈ Y ] [ۘ[ [X[ K[XZ[ >> > > > > \ \ Z [ X] [ \ X K ܙ B >> > > > > >> > > > > 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://www.cib.barclays/disclosures/web-and-email-disclaimer.html >> . >> > > > > >> > > > > For important disclosures, please see: >> > > > > https://www.cib.barclays/disclosures/sales-and-trading-disclaimer. >> > > > > ht ml regarding marketing commentary from Barclays Sales and/or >> > > > > Trading desks, who are active market participants; >> > > > > https://www.cib.barclays/disclosures/barclays-global-markets-dis >> > > > > cl os ur es.html regarding our standard terms for Barclays >> > > > > Corporate and Investment Bank where we trade with you in >> > > > > principal-to-principal wholesale markets transactions; and in >> > > > > respect to Barclays Research, including disclosures relating to >> > > > > specific issuers, see: >> > > > > http://publicresearch.barclays.com. >> > > > > ________________________________________________________________ >> > > > > __ >> > > > > __ >> > > > > __ >> > > > > ____________ >> > > > > >> > > > > If you are incorporated or operating in Australia, read these >> > > > > important >> > > > > disclosures: >> > > > > https://www.cib.barclays/disclosures/important-disclosures-asia- >> > > > > pa >> > > > > ci >> > > > > fi >> > > > > c.html >> > > > > . >> > > > > >> > > > > ________________________________________________________________ >> > > > > __ __ __ ____________ For more details about how we use personal >> > > > > information, see our privacy >> > > > > notice: >> > > > https://www.cib.barclays/disclosures/personal-information-use.html. >> > > > > >> > > > > >> > > > > ________________________________________________________________ >> > > > > __ >> > > > > __ >> > > > > __ >> > > > > ____________ >> > > > > >> > > > > ---------------------------------------------------------------- >> > > > > -- >> > > > > -- >> > > > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > > > > For additional commands, e-mail: users-h...@maven.apache.org >> > > > > >> > > > >> > > > C&A Services GmbH & Co. OHG | Wanheimer Straße 70 | D-40468 >> > > > Düsseldorf >> > > > | >> > > > Sitz: Düsseldorf | Registergericht: Düsseldorf HRA 12655 | Telefon: >> > > > +49 >> > > > (211) 9872-01 >> > > > Persönlich haftende Gesellschafter: C&A Retail GmbH | Sitz: >> > > > Baar/Schweiz | >> > > > UID: CHE-116.290.471 >> > > > Geschäftsführung: Giny Boer, Christoph Hammer FRM Participations S.A. >> > > > | Sitz: Strassen/Luxemburg | Handels- und Firmenregister Luxemburg: >> > > > | B >> > > > 58158 >> > > > Verwaltungsratsmitglieder: Dr. Christian Bank, Remco Gerlof, Dr. >> > > > Franz-Josef Leuchtenberg >> > > > Hinweise zur Verarbeitung Ihrer Daten finden Sie unter: >> > > > www.c-a.com/GDPR< http://www.c-a.com/GDPR> >> > > > >> > > >> > > C&A Services GmbH & Co. OHG | Wanheimer Straße 70 | D-40468 >> > > Düsseldorf >> > > | >> > > Sitz: Düsseldorf | Registergericht: Düsseldorf HRA 12655 | Telefon: >> > > +49 >> > > (211) 9872-01 >> > > Persönlich haftende Gesellschafter: C&A Retail GmbH | Sitz: >> > > Baar/Schweiz | >> > > UID: CHE-116.290.471 >> > > Geschäftsführung: Giny Boer, Christoph Hammer FRM Participations S.A. >> > > | Sitz: Strassen/Luxemburg | Handels- und Firmenregister Luxemburg: >> > > | B >> > > 58158 >> > > Verwaltungsratsmitglieder: Dr. Christian Bank, Remco Gerlof, Dr. >> > > Franz-Josef Leuchtenberg >> > > Hinweise zur Verarbeitung Ihrer Daten finden Sie unter: >> > > www.c-a.com/GDPR< http://www.c-a.com/GDPR> >> > > >> > >> > C&A Services GmbH & Co. OHG | Wanheimer Straße 70 | D-40468 Düsseldorf >> > | >> > Sitz: Düsseldorf | Registergericht: Düsseldorf HRA 12655 | Telefon: >> > +49 >> > (211) 9872-01 >> > Persönlich haftende Gesellschafter: C&A Retail GmbH | Sitz: >> > Baar/Schweiz | >> > UID: CHE-116.290.471 >> > Geschäftsführung: Giny Boer, Christoph Hammer FRM Participations S.A. >> > | Sitz: Strassen/Luxemburg | Handels- und Firmenregister Luxemburg: B >> > 58158 >> > Verwaltungsratsmitglieder: Dr. Christian Bank, Remco Gerlof, Dr. >> > Franz-Josef Leuchtenberg >> > Hinweise zur Verarbeitung Ihrer Daten finden Sie unter: >> > www.c-a.com/GDPR< http://www.c-a.com/GDPR> >> > >> >> C&A Services GmbH & Co. OHG | Wanheimer Straße 70 | D-40468 Düsseldorf | >> Sitz: Düsseldorf | Registergericht: Düsseldorf HRA 12655 | Telefon: +49 >> (211) 9872-01 >> Persönlich haftende Gesellschafter: C&A Retail GmbH | Sitz: Baar/Schweiz | >> UID: CHE-116.290.471 >> Geschäftsführung: Giny Boer, Christoph Hammer >> FRM Participations S.A. | Sitz: Strassen/Luxemburg | Handels- und >> Firmenregister Luxemburg: B 58158 >> Verwaltungsratsmitglieder: Dr. Christian Bank, Remco Gerlof, Dr. >> Franz-Josef Leuchtenberg >> Hinweise zur Verarbeitung Ihrer Daten finden Sie unter: www.c-a.com/GDPR< >> http://www.c-a.com/GDPR> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
