Re: Maven return code 502, ReasonPhrase:notresolvable
Hi Karl, I will see what happens with the version change from 1.3 of maven-antrun-plugin, I will try to take a look into that and see if I can make those changes. Looking in the POM file there is no version specified for it explicitly. I'll have to see where that is coming from. "Return code is: 502 , ReasonPhrase:notresolvable." is the error Maven provides and looking at: http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException which is the link provided in the exception thrown by Maven, I have tried the suggestions provided there to no avail. We do not have anything else between Maven and Nexus. There is no Apache HTTP server in between, it is a direct connection to Nexus, so its Nexus OSS plain. The artefacts I listed in the original email below, are the only artefacts that are affected. All other artefacts are downloaded just fine. No Nexus changes have been made, I have already checked that. BEGIN settings.xml -- http corp-proxy-server.mycorp.com 80 *.oldcorp.com|*.mycorp*.com releases Internal Nexus Releases http://nexusoss.mycorp.com:8081/nexus/content/groups/releases central configure-snapshot-repository true snapshots Internal Nexus Snapshots http://nexusoss.mycorp.com:8081/nexus/content/groups/snapshots false true always releases Internal Nexus Releases http://nexusoss.mycorp.com:8081/nexus/content/groups/releases/ true false always snapshots Internal Nexus Snapshots http://nexusoss.mycorp.com:8081/nexus/content/groups/snapshots false true always releases Internal Nexus Releases http://nexusoss.mycorp.com:8081/nexus/content/groups/releases/ true false always override-properties true use-maven-central remote-central http://repo1.maven.org/maven2 remote-central http://repo2.maven.org/maven2 suborg-snapshots 664 775 nightly some-password suborg-releases 664 775 nightly some-password - END settings.xml - On Sun, Aug 13, 2017 at 12:56 PM, Karl Heinz Marbaise wrote: > Hi, > > first recommendation I can give is upgrade the plugin versions cause 1.3 > from 2008 ...is really old... > > furthermore error code 502 is "Bad Gateway"...do you have an Apache http > server between you and the Nexus ? Or do you use Nexus plain...? Sounds > like an issue on network level...Or bad configuration of Nexus etc.. > > How does your settings.xml look like? > > Kind regards > Karl Heinz Marbaise > > On 13/08/17 18:29, Mehul Sanghvi wrote: > >> I upgraded my Nexus OSS server to version 2.14.5-02, and I still see the >> same issue. All new builds that I have >> get affected by this, unless I manually copy the artefacts from an >> existing >> local maven repository. >> >> I have rebuilt the metadata, re-built the indexes, etc. as well. Still >> the >> same result. >> >> Anyone have any thoughts/suggestions/pointers ? >> >> cheers, >> >> mehul >> >> >> On Wed, Jul 26, 2017 at 9:21 AM, Mehul Sanghvi >> wrote: >> >> Maven version: 3.3.3 >>> Nexus version: OSS 2.14.o-1 >>> >>> Starting this past Monday, I have been seeing the following: >>> >>> >>> build
Re: Maven return code 502, ReasonPhrase:notresolvable
Hi, first recommendation I can give is upgrade the plugin versions cause 1.3 from 2008 ...is really old... furthermore error code 502 is "Bad Gateway"...do you have an Apache http server between you and the Nexus ? Or do you use Nexus plain...? Sounds like an issue on network level...Or bad configuration of Nexus etc.. How does your settings.xml look like? Kind regards Karl Heinz Marbaise On 13/08/17 18:29, Mehul Sanghvi wrote: I upgraded my Nexus OSS server to version 2.14.5-02, and I still see the same issue. All new builds that I have get affected by this, unless I manually copy the artefacts from an existing local maven repository. I have rebuilt the metadata, re-built the indexes, etc. as well. Still the same result. Anyone have any thoughts/suggestions/pointers ? cheers, mehul On Wed, Jul 26, 2017 at 9:21 AM, Mehul Sanghvi wrote: Maven version: 3.3.3 Nexus version: OSS 2.14.o-1 Starting this past Monday, I have been seeing the following: build 25-Jul-2017 20:27:16 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.3:run (default) on project xml2jsonMigration: Execution default of goal org.apache.maven.plugins:maven-antrun-plugin:1.3:run failed: Plugin org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven:maven-plugin-api:jar:2.0.4, org.apache.maven:maven-project:jar:2.0.4, org.apache.maven:maven-settings:jar:2.0.4, org.apache.maven:maven-profile:jar:2.0.4, org.apache.maven:maven-model:jar:2.0.4, org.apache.maven:maven-artifact-manager:jar:2.0.4, org.apache.maven:maven-repository-metadata:jar:2.0.4, org.apache.maven:maven-artifact:jar:2.0.4, org.codehaus.plexus:plexus-utils:jar:1.5.6: Could not transfer artifact org.apache.maven:maven-plugin-api:jar:2.0.4 from/to releases (http://nexus.myorg.com:8081/nexus/content/groups/releases/): Failed to transfer file: http://nexus.myorg.com:8081/nexus/content/groups/releases/ org/apache/maven/maven-plugin-api/2.0.4/maven-plugin-api-2.0.4.jar. Return code is: 502 , ReasonPhrase:notresolvable. At first it was for an artefact that was located in an internal corporate Artifactory repository, which I was able to get past by modifying the proxy settings in the settings.xml file. It used to be: *.myorg.com and I changed it to *.myorg.com|*.mycorp.com The error above that I am getting though, is for something that was working. And the artefacts are accessible via the web browser. From a network standpoint, the Nexus server is one hop away (based on traceroute information). This used to work. There have been no network changes, not VM changes, no updates to Maven. We did change the version number of our product by removing the -SNAPSHOT, but that should not cause this error that we are seeing. I have tried using the -U command line option, as well as just pointing maven.repo.local to a new location and avoiding any cacheing issues. Any pointers/suggestions/thoughts ? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven return code 502, ReasonPhrase:notresolvable
I upgraded my Nexus OSS server to version 2.14.5-02, and I still see the same issue. All new builds that I have get affected by this, unless I manually copy the artefacts from an existing local maven repository. I have rebuilt the metadata, re-built the indexes, etc. as well. Still the same result. Anyone have any thoughts/suggestions/pointers ? cheers, mehul On Wed, Jul 26, 2017 at 9:21 AM, Mehul Sanghvi wrote: > Maven version: 3.3.3 > Nexus version: OSS 2.14.o-1 > > Starting this past Monday, I have been seeing the following: > > > build 25-Jul-2017 20:27:16 [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-antrun-plugin:1.3:run (default) on project > xml2jsonMigration: Execution default of goal > org.apache.maven.plugins:maven-antrun-plugin:1.3:run failed: Plugin > org.apache.maven.plugins:maven-antrun-plugin:1.3 or one of its > dependencies > could not be resolved: The following artifacts could not be resolved: > org.apache.maven:maven-plugin-api:jar:2.0.4, > org.apache.maven:maven-project:jar:2.0.4, > org.apache.maven:maven-settings:jar:2.0.4, > org.apache.maven:maven-profile:jar:2.0.4, > org.apache.maven:maven-model:jar:2.0.4, > org.apache.maven:maven-artifact-manager:jar:2.0.4, > org.apache.maven:maven-repository-metadata:jar:2.0.4, > org.apache.maven:maven-artifact:jar:2.0.4, > org.codehaus.plexus:plexus-utils:jar:1.5.6: Could not transfer artifact > org.apache.maven:maven-plugin-api:jar:2.0.4 from/to releases > (http://nexus.myorg.com:8081/nexus/content/groups/releases/): Failed to > transfer file: > http://nexus.myorg.com:8081/nexus/content/groups/releases/ > org/apache/maven/maven-plugin-api/2.0.4/maven-plugin-api-2.0.4.jar. > Return code is: 502 , > ReasonPhrase:notresolvable. > > > At first it was for an artefact that was located in an internal corporate > Artifactory repository, which I was able to get past by modifying the proxy > settings in the settings.xml file. It used to be: > > *.myorg.com > > and I changed it to > > *.myorg.com|*.mycorp.com > > > > The error above that I am getting though, is for something that was > working. And the artefacts are accessible via the web browser. From a > network standpoint, the Nexus server is one hop away (based on traceroute > information). > > This used to work. There have been no network changes, not VM changes, > no updates to Maven. We did change the version number of our product by > removing the -SNAPSHOT, but that should not cause this error that we are > seeing. > > I have tried using the -U command line option, as well as just pointing > maven.repo.local to a new location and avoiding any cacheing issues. > > > Any pointers/suggestions/thoughts ? > > -- > Mehul N. Sanghvi > email: mehul.sang...@gmail.com > -- Mehul N. Sanghvi email: mehul.sang...@gmail.com
[ANN] Apache Maven Shared Component: Maven Archiver Version 3.2.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Archiver Version 3.2.0 https://maven.apache.org/shared/maven-archiver/ You should specify the version in your project: org.apache.maven.shared maven-archiver 3.2.0 Important Note: * Maven 3.X minimum * JDK 7 minimum requirement. You can download the appropriate sources etc. from the download page: https://maven.apache.org/shared/maven-archiver/download.cgi Release Notes Maven Archiver 3.2.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12336743 Bug: * [MSHARED-601] - Update examples with "Archiver-Version" manifest entry Improvements: * [MSHARED-578] - Upgrade maven-shared-utils to 3.1.0 * [MSHARED-579] - Upgrade to plexus-archiver 3.4 * [MSHARED-643] - Upgrade to maven-shared-utils 3.2.0 * [MSHARED-644] - Removed prerequisites for none maven-plugin project * [MSHARED-653] - Upgrade to plexus-archiver 3.5 Enjos, -The Apache Maven team Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org