Re: pvn package command dependencies error
Hey Mark, I just browsed through the commits (git show :/block). You can easily redirect to http like so as mirrors are not blocked: maven-snapshots-https maven-snapshots-https https://oss.sonatype.org/content/repositories/snapshots maven-snapshots maven-restlet-https maven-restlet-https https://maven.restlet.org maven-restlet apache.snapshots-https apache.snapshots-https https://repository.apache.org/snapshots apache.snapshots It works… Kinda. The certificate of https://maven.restlet.org is expired. But other than that, this is how you bypass the http block. HTH Am Di., 4. Mai 2021 um 15:42 Uhr schrieb Mark H. Wood : > > On Tue, May 04, 2021 at 12:29:20PM +0200, Benjamin Marwell wrote: > > you need to use https URLs in your repositories. http URLs are now > > blocked by default. > > That should resolve the issue you are having. > > He can't. The problem is with a transitive dependency of Solr 4.10.4 > and is in Solr's POM. This is a known problem for DSpace: > > https://stackoverflow.com/q/66962265/2916377 > > It was activated by a recent Maven upgrade which blocks unencrypted > repository accesses by default. > > > You should take a look at your $HOME/.m2/settings.xml, as well as > > potential occurrences of repository tags in your pom.xml files. > > That won't help in this case, since the problem lies in a necessarily > ancient version of a third-party dependency. One could either > override the block in .m2/settings.xml or manually acquire a copy of > the restlet artifact and install it in one's local repository (perhaps > using 'mvn install:install-file'). > > There are breaking changes in newer releases of Solr which won't be > accounted for in DSpace until the next major release (which should > come soon). Moving to a newer Solr release is a rather involved > process due to those changes, and I don't know of anyone who has done > it with a released version of DSpace. > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University - Purdue University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 > www.ulib.iupui.edu - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to make maven not use the first proxy in settings.xml?
Am 2021-04-25 um 10:14 schrieb Rodolphe Gohard:
Hello,
Maven allows multiple proxies to be defined:
proxy_gcp
true
http
app-proxy.gcp.acme.fr
80
proxy_aws
false
http
app-proxy.aws.acme.fr
80
As stipulated in the default settings.xml, Unless otherwise specified (by
system property or command-line switch), the first proxy specification in
this list marked as active will be used.
But I couldn't find any direction on how to specify otherwise by system
property or command-line switch.
How can I tell maven to use the second proxy in the list (command line, or
with properties) ?
Precision: I'm not looking for the -Dhttp.proxyPort=
-Dhttp.nonProxyHosts= options, i'm looking for a switch
between the different defined proxies.
This is a bit of problematic topic. There is no switch for proxy
enable/disable. I don't know where this comes from. You may try
> ${FOO}
and -DFOO=...
The sytem property or CLI switch only refer to -Dhttp.proxy.. and
-Dhttps.proxy...
Note that this is a problematic solution which I don't like. This will
only work with Wagon Apache HTTP Client because we enable this. I am
included to remove this support in the next major for various reasons
and all HttpURLConnection based stuff running in the same JVM.
Everything else shall use settings.xml.
Is this sufficient as an answer? I guess am currently most skilled one
in Maven space to answer this question. If still now clear, let me know.
Michael
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: pvn package command dependencies error
On Tue, May 04, 2021 at 12:29:20PM +0200, Benjamin Marwell wrote: > you need to use https URLs in your repositories. http URLs are now > blocked by default. > That should resolve the issue you are having. He can't. The problem is with a transitive dependency of Solr 4.10.4 and is in Solr's POM. This is a known problem for DSpace: https://stackoverflow.com/q/66962265/2916377 It was activated by a recent Maven upgrade which blocks unencrypted repository accesses by default. > You should take a look at your $HOME/.m2/settings.xml, as well as > potential occurrences of repository tags in your pom.xml files. That won't help in this case, since the problem lies in a necessarily ancient version of a third-party dependency. One could either override the block in .m2/settings.xml or manually acquire a copy of the restlet artifact and install it in one's local repository (perhaps using 'mvn install:install-file'). There are breaking changes in newer releases of Solr which won't be accounted for in DSpace until the next major release (which should come soon). Moving to a newer Solr release is a rather involved process due to those changes, and I don't know of anyone who has done it with a released version of DSpace. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu signature.asc Description: PGP signature
Re: Maven 3.8.1 + maven-deploy-plugin 3.0.0-M1 and still no SHA256/SHA512
Am 2021-04-30 um 07:29 schrieb David Milet: I figured it out... With Maven 3.8.1 and maven-deploy-plugin 3.0.0-M1, need to pass -Daether.checksums.algorithms="SHA256,SHA512" to the maven options Please note that this won't pass Maven Central upload validation. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: pvn package command dependencies error
Hi, you need to use https URLs in your repositories. http URLs are now blocked by default. That should resolve the issue you are having. You should take a look at your $HOME/.m2/settings.xml, as well as potential occurrences of repository tags in your pom.xml files. Best regards, Ben Am Mo., 3. Mai 2021 um 22:43 Uhr schrieb Compte Messagerie : > > hello, > i try to install dspace 6.3 on centos8 with apache-maven-3.8.1 and > openjdk11 > where i execute $mvn package -X//for debug > it ends with: > > [INFO] --< org.dspace.modules:solr > >--- > [INFO] Building DSpace SOLR :: Local Customizations 6.3 > [9/11] > [INFO] [ war > ]- > [INFO] > > [INFO] Reactor Summary for DSpace Assembly and Configuration 6.3: > [INFO] > [INFO] DSpace Addon Modules ... SUCCESS [ > 0.612 s] > [INFO] DSpace Kernel :: Additions and Local Customizations SUCCESS [ > 3.153 s] > [INFO] DSpace XML-UI (Manakin) :: Local Customizations SUCCESS [03:51 > min] > [INFO] DSpace JSP-UI :: Local Customizations .. SUCCESS [02:12 > min] > [INFO] DSpace RDF :: Local Customizations . SUCCESS [03:20 > min] > [INFO] DSpace REST :: Local Customizations SUCCESS [02:22 > min] > [INFO] DSpace SWORD :: Local Customizations ... SUCCESS [03:08 > min] > [INFO] DSpace SWORD v2 :: Local Customizations SUCCESS [02:56 > min] > [INFO] DSpace SOLR :: Local Customizations FAILURE [ > 0.209 s] > [INFO] DSpace OAI-PMH :: Local Customizations . SKIPPED > [INFO] DSpace Assembly and Configuration .. SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 17:56 min > [INFO] Finished at: 2021-05-03T14:36:24+01:00 > [INFO] > > > [ERROR] Failed to execute goal on project solr: Could not resolve > dependencies for project org.dspace.modules:solr:war:6.3: Failed to collect > dependencies at org.dspace:dspace-solr:jar:classes:6.3 -> > org.apache.solr:solr-core:jar:4.10.4 -> > org.restlet.jee:org.restlet:jar:2.1.1: Failed to read artifact descriptor > for org.restlet.jee:org.restlet:jar:2.1.1: Could not transfer artifact > org.restlet.jee:org.restlet:pom:2.1.1 from/to maven-default-http-blocker ( > http://0.0.0.0/): Blocked mirror for repositories: [maven-snapshots ( > http://oss.sonatype.org/content/repositories/snapshots, default, > snapshots), maven-restlet (http://maven.restlet.org, default, > releases+snapshots), apache.snapshots ( > http://repository.apache.org/snapshots, default, disabled)] -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal on project solr: Could not resolve dependencies for project > org.dspace.modules:solr:war:6.3: Failed to collect dependencies at > org.dspace:dspace-solr:jar:classes:6.3 -> > org.apache.solr:solr-core:jar:4.10.4 -> > org.restlet.jee:org.restlet:jar:2.1.1 > at > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies > (LifecycleDependencyResolver.java:269) > at > org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies > (LifecycleDependencyResolver.java:147) > at > org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved > (MojoExecutor.java:248) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:202) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute > (MojoExecutor.java:148) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:117) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject > (LifecycleModuleBuilder.java:81) > at > org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build > (SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute > (LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957) > at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289) > at org.apache.maven.cli.MavenCli.main (MavenCli.java:193) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) > at jdk.internal.reflect.NativeMethodAccessorImpl.invoke >
