RE: Question about HTTP blocking WARN

2024-01-09 Thread Stefan CORDES 
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-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
>

RE: Question about HTTP blocking WARN

2024-01-04 Thread Stefan CORDES 
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

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 
> Subj

RE: Question about HTTP blocking WARN

2024-01-04 Thread Stefan CORDES 
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 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=vGmJxLiSHcBmf
> > ng
> > K9X2

RE: maven compiler plugin 3.12.0 and Kotlin project

2023-12-21 Thread Stefan CORDES 
Hi Hantsy,
that should be the same like
https://issues.apache.org/jira/browse/MCOMPILER-567
and fixed in 3.12.1

Workaround is to stay on 3.11.0 or use 
false

Gruß,
Stefan

-Original Message-
From: hantsy bai 
Sent: Friday, December 22, 2023 5:20 AM
To: Maven Users List 
Subject: maven compiler plugin 3.12.0 and Kotlin project

I tried to update Maven compiler plugin version to the latest 3.12.0 version, 
and got the error message like the following when compiling the
projects:

[INFO] --- compiler:3.12.0:compile (default-compile) @ mongodb-kotlin --- 
[INFO] Recompiling the module because of changed dependency.
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time:  02:12 min
[INFO] Finished at: 2023-12-22T12:14:43+08:00 [INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.12.0:compile
(default-compile) on project mongodb-kotlin: Fatal error compiling: basedir 
D:\hantsylabs\quarkus-sample\mongodb-kotlin\target\generated-sources\annotations
does not exist -> [Help 1]

I found the error only occurred in a Kotlin project, check an example of the 
updated pom.xml here, 
https://github.com/hantsy/quarkus-sandbox/blob/master/resteasy-kotlin-co/pom.xml
---

Regards,

*Hantsy Bai*

Self-employed consultant, fullstack developer, agile coach, freelancer/remote 
worker

GitHub: https://github.com/hantsy

Twitter: https://twitter.com/@hantsy
Medium: https://medium.com/@hantsy

C 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 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

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Fatal error compiling: basedir .../target/generated-sources/annotations does not exist

2023-12-20 Thread Stefan CORDES 
Hi,
I faced the similar error

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.12.0:testCompile 
(default-testCompile)
 Fatal error compiling:
basedir ...\target\generated-test-sources\test-annotations-java does not exist 
-> [Help 1]

and investigating I see it is not on all projects but only on these where the 
message
[INFO] --- maven-compiler-plugin:3.12.0:testCompile (default-testCompile) @ ... 
---
[INFO] Recompiling the module because of changed dependency.
above is printed.

Workaround for me was to add

false

to the maven-compiler-plugin-configuration.
Now same build prints
 [INFO] --- maven-compiler-plugin:3.12.0:testCompile (default-testCompile) @ 
... ---
 [INFO] Nothing to compile - all classes are up to date.

and no error comes up.

Gruß,
Stefan

-Original Message-
From: Slawomir Jaranowski 
Sent: Wednesday, December 20, 2023 9:41 AM
To: Maven Users List 
Subject: Re: Fatal error compiling: basedir 
.../target/generated-sources/annotations does not exist

Hi,

Thanks for the report ..

We are working on it, the new release should be in a few days.

https://issues.apache.org/jira/browse/MCOMPILER-567


śr., 20 gru 2023 o 08:09 Stanimir Stamenkov 
napisał(a):

> Following "Maven Compiler Plugin 3.12.0 Released" [1] I'm trying it
> out in a small project of mine [2].  After updating the
> maven-compiler-plugin 3.11.0 -> 3.12.0 I've noticed the following
> error occurring in my dirty(!) working copy:
>
> > mvn -V package
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: ...\apache-maven-3.9.6
> Java version: 21.0.1, vendor: Eclipse Adoptium, runtime: ...\jdk-21
> Default locale: en_US, platform encoding: UTF-8
> OS name: "windows 10", version: "10.0", arch: "amd64", family:
> "windows"
> ...
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.12.0:compile
> (java9-compile) on project xbrz-core: Fatal error compiling: basedir
> C:\...\xbrz-java\xbrz-core\target\generated-sources\annotations does
> not exist -> [Help 1]
>
> that doesn't occur with the compiler plugin 3.11.0.  The local change
> that appears to trigger the error with the compiler plugin 3.12.0 is
> I've deleted "module-info.java" sources:
>
> del /s module-info.java   # or with bash
>
> find -name module-info.java -print -delete
>
> Funny enough, if I restore "xbrz-core/src/main/java9/module-info.java"
> both of "xbrz-core" and "xbrz-awt" get built successfully, then
> "xbrz-tool" fails the same.
>
> Does this behavior appear a regression?  I've found a similar symptom
> fixed long time ago:
>
> *   https://issues.apache.org/jira/browse/MCOMPILER-379
>
> [1] https://lists.apache.org/thread/9x7p7k5n7vptopqrt55o7c2pg7pnznh2
> [2] https://github.com/stanio/xbrz-java
>
> Note, "xbrz-java" currently requires JDK 21 for building just for
> the javadoc generation.  One may edit .mvn/enforcer-extension.xml to
> relax this requirement for the purpose of `mvn package` alone.
>
> --
> Stanimir
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

--
Sławomir Jaranowski

C 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 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

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Question about HTTP blocking WARN

2023-12-13 Thread Stefan CORDES 
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 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=MSjyi1VB4cPbNJs
> glaLsboIIC2w3PxVFwT0C3b3tJjE==https://clicktime.symantec.com/15sM1Hv
> Lio6GkLoeSsGso?h=a4l_3miTQ9Jpp9kBhV4g1A6nK9z3Xc4ThYeLnyNM6NM==https:
> //github.com/apache/pulsar
>
> Thanks,
>
> Asaf
>
> This message

RE: how to disable http 100-continue with 3.9 http-transport ?

2023-11-02 Thread Stefan CORDES 
Hi Benjamin,
thanks for the hint, but still

mvn deploy -Daether.connector.basic.parallelPut=false
and
mvn deploy -Daether.connector.http.preemptivePutAuth=false
are failing as they send the
http-outgoing-0 >> Expect: 100-continue
header to our nexus(proxy)

Hi T,
> Is it documented somewhere that Nexus3 does not support http-continue?
There is nothing like that but our Nexus is listening on 8081 and we have some 
"http proxy" before on 443 which I now try to find out what proxy it is and 
what version.
(we have nexus+proxy self hosted)

Gruß,
Stefan

-Original Message-
From: Benjamin Marwell 
Sent: Friday, October 27, 2023 8:13 PM
To: Maven Users List 
Subject: Re: how to disable http 100-continue with 3.9 http-transport ?

Hi,

Disabling parallel put works for me.

https://maven.apache.org/resolver/configuration.html


On Fri, 27 Oct 2023, 20:08 Tamás Cservenák,  wrote:

> Howdy,
>
> Are you sure you have to disable use of http-continue? Isn't this
> something "legacy" or hack that you try to carry on maybe?
>
> Is it documented somewhere that Nexus3 does not support http-continue?
>
> If you have support contract, I'd ask your provider about this first...
>
> Thanks
> T
>
> On Fri, Oct 27, 2023, 18:37 Stefan CORDES  .invalid>
> wrote:
>
> > Hi,
> > we configured the 3.8 wagon transport to not send a http-continue as
> > this fails with our nexus3 to store the artifacts.
> >
> > Switching to maven 3.9 the new transport is taken where I cannot
> > find how to disable the http 100
> >
> >
> >
> https://github.com/apache/maven-resolver/blob/master/maven-resolver-tr
> ansport-http/src/main/java/org/eclipse/aether/transport/http/LocalStat
> e.java#L82
> >
> > How can I disable sending
> > [DEBUG] org.apache.http.headers - http-outgoing-0 >> Expect:
> > 100-continue while using mvn deploy?
> >
> > Gruß,
> > Stefan
> >
> > P.S.:
> > Nexus http response is 500 with http-continue and nexus.log shows
> >
> > 2023-10-27 18:19:57,155+0200 WARN  [qtp804177152-23427]  x
> > org.sonatype.nexus.repository.httpbridge.internal.ViewServlet -
> > Failure
> > servicing: PUT
> >
> /repository/Snapshots/com/canda/mule4/x-mule4-template/1.0.0-local-SNA
> PSHOT/x-mule4-template-1.0.0-local-20231027.161836-1-mule-application.
> jar
> > org.sonatype.nexus.blobstore.api.BlobStoreException: BlobId:
> > tmp$d7b33f72-f9be-4fc8-b444-73d98adde3f1, java.io.IOException:
> > java.util.concurrent.TimeoutException: Idle timeout expired:
> > 3/3 ms, Cause: java.util.concurrent.TimeoutException: Idle timeout 
> > expired:
> > 3/3 ms
> > at
> >
> org.sonatype.nexus.blobstore.file.FileBlobStore.tryCreate(FileBlobStor
> e.java:438)
> > at
> >
> org.sonatype.nexus.blobstore.file.FileBlobStore.create(FileBlobStore.j
> ava:368)
> > at
> >
> org.sonatype.nexus.blobstore.file.FileBlobStore.doCreate(FileBlobStore
> .java:348)
> > at
> >
> org.sonatype.nexus.blobstore.metrics.BlobStoreAnalyticsInterceptor.inv
> oke(BlobStoreAnalyticsInterceptor.java:60)
> > at
> >
> org.sonatype.nexus.blobstore.BlobStoreSupport.create(BlobStoreSupport.
> java:125)
> > at
> >
> org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(Method
> InvocationAction.java:39)
> > at
> >
> org.sonatype.nexus.common.stateguard.StateGuard$GuardImpl.run(StateGua
> rd.java:272)
> > at
> >
> org.sonatype.nexus.common.stateguard.GuardedInterceptor.invoke(Guarded
> Interceptor.java:54)
> > at
> >
> org.sonatype.nexus.blobstore.BlobStoreSupport.create(BlobStoreSupport.
> java:109)
> > at
> >
> org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(Method
> InvocationAction.java:39)
> > at
> >
> org.sonatype.nexus.common.stateguard.StateGuard$GuardImpl.run(StateGua
> rd.java:272)
> > at
> >
> org.sonatype.nexus.common.stateguard.GuardedInterceptor.invoke(Guarded
> Interceptor.java:54)
> > at
> >
> org.sonatype.nexus.repository.storage.StorageFacetImpl.createTempBlob(
> StorageFacetImpl.java:266)
> > at
> >
> org.sonatype.nexus.repository.storage.StorageFacetImpl.createTempBlob(
> StorageFacetImpl.java:277)
> >
> >
> > C Services GmbH & Co. OHG | Wanheimer Straße 70 | D-40468
> > Düsseldorf |
> > Sitz: Düsseldorf | Registergericht: Düsseldorf HRA 12655 | Tele

RE: how to log exact HTTP request and response maven sends over the wire?

2023-10-30 Thread Stefan CORDES 
Hi,
in your

MAVEN_HOME\conf\logging\simplelogger.properties

you can enable (set from off to debug)

org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient=debug
org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=debug

and

org.slf4j.simpleLogger.log.org.apache.http.headers=debug
org.slf4j.simpleLogger.log.org.apache.http.wire=debug

to see all http traffic header and body.

Gruß,
Stefan

-Original Message-
From: mark.yagnatin...@barclays.com.INVALID 

Sent: Monday, October 30, 2023 3:32 PM
To: users@maven.apache.org
Subject: RE: how to log exact HTTP request and response maven sends over the 
wire?

Maven 3.6.3 ... no overides

-Original Message-
From: Tamás Cservenák 
Sent: Monday, October 30, 2023 10:04 AM
To: Maven Users List 
Subject: Re: how to log exact HTTP request and response maven sends over the 
wire?


CAUTION: This email originated from outside our organisation - 
ta...@cservenak.net Do not click on links, open attachments, or respond unless 
you recognize the sender and can validate the content is safe.
Howdy,

for start we'd need:
- what Maven (best to just `mvn -v` and copy that)
- if you override transport, what you override transport to?

Thanks
T

On Mon, Oct 30, 2023 at 2:54 PM 
wrote:

> I'm getting HTTP 400 errors from a repo I'm trying to connect to and I
> don't understand why.
> Is there an easy way to get maven to show exactly what HTTP request
> gets sent over the wire and what comes back?
>
> 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/15t5z44MqsZDPQVLm81br?h=BrzHY6XfU_3PtXDVTfgozx94KdEjrdka42d0K8tf3ao==https://www.cib.barclays/disclosures/web-and-email-disclaimer.html.
>
> For important disclosures, please see:
> https://clicktime.symantec.com/15t5uDs5PFscyTfRDZcTE?h=ZCG-UUcnRQGU2WD
> 44hE5RxT2sotnkCDtp-MRqevDkp4==https://www.cib.barclays/disclosures/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/15t5ejHE1QpqjdBeatR1N?h=DkNaTHLjb8eqZ08
> gO5EjbAJk1H41HZcwrkQOGHmbSjg==https://www.cib.barclays/disclosures/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/15t5Zu5wYo9FKgMj3L1rk?h=AJ0ZI4oxSqFdQEGEQd-g03qCgsmtTNLkJBQJHsSCBTI==http://publicresearch.barclays.com.
> __
> 
>
> If you are incorporated or operating in Australia, read these
> important
> disclosures:
> https://clicktime.symantec.com/15t5jZUWU2WS9a1a8Sp9z?h=jq3kfLHvz1eyXO5
> 5VDKwe1rnJ6Z9_El5xwJfKSd4iek==https://www.cib.barclays/disclosures/i
> mportant-disclosures-asia-pacific.html
> .
>
> __
>  For more details about how we use personal information,
> see our privacy
> notice: 
> https://clicktime.symantec.com/15t5pPfnveC2ZWqVg1DJc?h=uYHykXL4S6qcxw0SK9tlahK-n0t6KWADPJKu7Tm2W7M==https://www.cib.barclays/disclosures/personal-information-use.html.
>
>
> __
> 

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.html 
regarding marketing commentary from Barclays Sales and/or Trading desks, who 
are active market participants; 
https://www.cib.barclays/disclosures/barclays-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: http://publicresearch.barclays.com.
__
If you are incorporated or operating in Australia, read these important 
disclosures:

how to disable http 100-continue with 3.9 http-transport ?

2023-10-27 Thread Stefan CORDES 
Hi,
we configured the 3.8 wagon transport to not send a http-continue as this fails 
with our nexus3 to store the artifacts.

Switching to maven 3.9 the new transport is taken where I cannot find how to 
disable the http 100

https://github.com/apache/maven-resolver/blob/master/maven-resolver-transport-http/src/main/java/org/eclipse/aether/transport/http/LocalState.java#L82

How can I disable sending
[DEBUG] org.apache.http.headers - http-outgoing-0 >> Expect: 100-continue
while using mvn deploy?

Gruß,
Stefan

P.S.:
Nexus http response is 500 with http-continue and nexus.log shows

2023-10-27 18:19:57,155+0200 WARN  [qtp804177152-23427]  x 
org.sonatype.nexus.repository.httpbridge.internal.ViewServlet - Failure 
servicing: PUT 
/repository/Snapshots/com/canda/mule4/x-mule4-template/1.0.0-local-SNAPSHOT/x-mule4-template-1.0.0-local-20231027.161836-1-mule-application.jar
org.sonatype.nexus.blobstore.api.BlobStoreException: BlobId: 
tmp$d7b33f72-f9be-4fc8-b444-73d98adde3f1, java.io.IOException: 
java.util.concurrent.TimeoutException: Idle timeout expired: 3/3 ms, 
Cause: java.util.concurrent.TimeoutException: Idle timeout expired: 3/3 
ms
at 
org.sonatype.nexus.blobstore.file.FileBlobStore.tryCreate(FileBlobStore.java:438)
at 
org.sonatype.nexus.blobstore.file.FileBlobStore.create(FileBlobStore.java:368)
at 
org.sonatype.nexus.blobstore.file.FileBlobStore.doCreate(FileBlobStore.java:348)
at 
org.sonatype.nexus.blobstore.metrics.BlobStoreAnalyticsInterceptor.invoke(BlobStoreAnalyticsInterceptor.java:60)
at 
org.sonatype.nexus.blobstore.BlobStoreSupport.create(BlobStoreSupport.java:125)
at 
org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
at 
org.sonatype.nexus.common.stateguard.StateGuard$GuardImpl.run(StateGuard.java:272)
at 
org.sonatype.nexus.common.stateguard.GuardedInterceptor.invoke(GuardedInterceptor.java:54)
at 
org.sonatype.nexus.blobstore.BlobStoreSupport.create(BlobStoreSupport.java:109)
at 
org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
at 
org.sonatype.nexus.common.stateguard.StateGuard$GuardImpl.run(StateGuard.java:272)
at 
org.sonatype.nexus.common.stateguard.GuardedInterceptor.invoke(GuardedInterceptor.java:54)
at 
org.sonatype.nexus.repository.storage.StorageFacetImpl.createTempBlob(StorageFacetImpl.java:266)
at 
org.sonatype.nexus.repository.storage.StorageFacetImpl.createTempBlob(StorageFacetImpl.java:277)


C 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 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

Re: Why does maven build on dos prompt keeps waiting for user to press enter?

2010-07-28 Thread Stefan Cordes 
Hi!
You may try -B option = Batch

Here is what we do:
tempFileWriter.write(call mvn release:prepare
+  -B  // Batch Mode
+  -Dresume=false  +  
-DreleaseVersion= + tempNextVersionNumber +  -DdevelopmentVersion=
+ tempNextVersionNumber + 
-SNAPSHOT  +  -Dtag= + tempCvsVersionTag +   + \r\n);

Gruß,
Stefan Cordes
 



 


P Please consider the environmental impact of needlessly printing this 
e-mail. 





Kannan Jayaprakasam kan...@arcot.com 
28.07.2010 09:52
Please respond to
Maven Users List users@maven.apache.org


To
users@maven.apache.org users@maven.apache.org
cc

Subject
Why does maven build on dos prompt keeps waiting for user to press  enter?






For my pom.xml based maven build, at multiple places it waits and keeps 
waiting until I press Enter. This is a huge time waster because for a big 
project I have to constantly monitor the window and keep pressing Enter. 
How to make it just proceed without waiting? Pressing a number of Enters 
beforehand doesn't help.



!DSPAM:4c4fe1c194471804284693!

Configuring Authentication: How to specify scm username/password in settings.xml instead of pom.xml

2010-07-23 Thread Stefan Cordes 
Hi!
On 
http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html
 

it is just stated that username/password can be stored in the pom.xml.

How to specify it in the settings.xml?


--
RSC Commercial Services OHG
Wanheimer Strasse 70, D-40468 Duesseldorf
Registergericht: Duesseldorf, HRA 12655