Re: [thredds] Unidata Maven repository upgrade

  • To: Christian Ward-Garrison <cwardgar@xxxxxxxx>
  • Subject: Re: [thredds] Unidata Maven repository upgrade
  • From: Ben Caradoc-Davies <ben@xxxxxxxxxxxx>
  • Date: Fri, 10 Nov 2017 12:01:06 +1300
Thanks, Christian. I am now getting a different exception:

:tds:compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all dependencies for configuration ':tds:compileClasspath'.
> Could not resolve uk.ac.rdg.resc:ncwms:1.2.tds.4.6.11-SNAPSHOT.
  Required by:
      project :tds
   > Could not resolve uk.ac.rdg.resc:ncwms:1.2.tds.4.6.11-SNAPSHOT.
> Unable to load Maven meta-data from https://artifacts.unidata.ucar.edu/content/repositories/unidata-3rdparty/uk/ac/rdg/resc/ncwms/1.2.tds.4.6.11-SNAPSHOT/maven-metadata.xml. > Could not GET 'https://artifacts.unidata.ucar.edu/content/repositories/unidata-3rdparty/uk/ac/rdg/resc/ncwms/1.2.tds.4.6.11-SNAPSHOT/maven-metadata.xml'. Received status code 400 from server: Repository version policy: RELEASE does not allow metadata in path: uk/ac/rdg/resc/ncwms/1.2.tds.4.6.11-SNAPSHOT/maven-metadata.xml
   > Could not resolve uk.ac.rdg.resc:ncwms:1.2.tds.4.6.11-SNAPSHOT.
> Unable to load Maven meta-data from https://artifacts.unidata.ucar.edu/content/repositories/unidata-3rdparty/uk/ac/rdg/resc/ncwms/1.2.tds.4.6.11-SNAPSHOT/maven-metadata.xml. > Could not GET 'https://artifacts.unidata.ucar.edu/content/repositories/unidata-3rdparty/uk/ac/rdg/resc/ncwms/1.2.tds.4.6.11-SNAPSHOT/maven-metadata.xml'. Received status code 400 from server: Repository version policy: RELEASE does not allow metadata in path: uk/ac/rdg/resc/ncwms/1.2.tds.4.6.11-SNAPSHOT/maven-metadata.xml
   > Could not resolve uk.ac.rdg.resc:ncwms:1.2.tds.4.6.11-SNAPSHOT.
> Unable to load Maven meta-data from https://artifacts.unidata.ucar.edu/content/repositories/unidata-3rdparty/uk/ac/rdg/resc/ncwms/1.2.tds.4.6.11-SNAPSHOT/maven-metadata.xml. > Could not GET 'https://artifacts.unidata.ucar.edu/content/repositories/unidata-3rdparty/uk/ac/rdg/resc/ncwms/1.2.tds.4.6.11-SNAPSHOT/maven-metadata.xml'. Received status code 400 from server: Repository version policy: RELEASE does not allow metadata in path: uk/ac/rdg/resc/ncwms/1.2.tds.4.6.11-SNAPSHOT/maven-metadata.xml
   > Could not resolve uk.ac.rdg.resc:ncwms:1.2.tds.4.6.11-SNAPSHOT.
> Unable to load Maven meta-data from https://artifacts.unidata.ucar.edu/content/repositories/unidata-3rdparty/uk/ac/rdg/resc/ncwms/1.2.tds.4.6.11-SNAPSHOT/maven-metadata.xml. > Could not GET 'https://artifacts.unidata.ucar.edu/content/repositories/unidata-3rdparty/uk/ac/rdg/resc/ncwms/1.2.tds.4.6.11-SNAPSHOT/maven-metadata.xml'. Received status code 400 from server: Repository version policy: RELEASE does not allow metadata in path: uk/ac/rdg/resc/ncwms/1.2.tds.4.6.11-SNAPSHOT/maven-metadata.xml


On 10/11/17 11:42, Christian Ward-Garrison wrote:
Hi Ben,

Yeah, sorry about the breakage. I've gone ahead and applied an Apache
rewrite rule that will automatically convert Nexus v2 URLs into v3 URLs on
the server-side.

So, that means that you don't need to change the repository URL in your
Maven build if you do not which to.

Cheers,
Christian

On Thu, Nov 9, 2017 at 3:39 PM, Ben Caradoc-Davies <ben@xxxxxxxxxxxx> wrote:

Thanks, Christian. This no doubt explains why my local THREDDS build
started failing today (unable to find ncwms SNAPSHOT). I will wait for the
build.gradle updates.

Kind regards,
Ben.


On 10/11/17 11:05, Christian Ward-Garrison wrote:

Hello all,

Today we made the switch from Nexus Repository Manager 2.14 to Nexus
Repository Manager 3.6. They are on different servers with different IP
addresses, so a DNS change was required. DNS changes can take up to 24
hours to propagate across the internet, so it may not have reached you
yet.

The format of the URLs in version 3 has changed slightly, which could
cause
disruption in software builds if that software downloads artifacts from
our
server. Previously, we recommended that you use the following URL:

https://artifacts.unidata.ucar.edu/content/repositories/unidata-releases/

We now need to use:

https://artifacts.unidata.ucar.edu/repository/unidata-releases/

Actually, 'unidata-all' is even better as it includes all of our snapshots
and third-party artifacts as well:

https://artifacts.unidata.ucar.edu/repository/unidata-all/

Full (updated) instructions for using NetCDF-Java as a build dependency
can
be found at
https://www.unidata.ucar.edu/software/thredds/current/netcdf
-java/reference/BuildDependencies.html

Thanks,
Christian



_______________________________________________
NOTE: All exchanges posted to Unidata maintained email lists are
recorded in the Unidata inquiry tracking system and made publicly
available through the web.  Users who post to any of the lists we
maintain are reminded to remove any personal information that they
do not want to be made public.


thredds mailing list
thredds@xxxxxxxxxxxxxxxx
For list information or to unsubscribe,  visit:
http://www.unidata.ucar.edu/mailing_lists/


--
Ben Caradoc-Davies <ben@xxxxxxxxxxxx>
Director
Transient Software Limited <http://transient.nz/>
New Zealand



--
Ben Caradoc-Davies <ben@xxxxxxxxxxxx>
Director
Transient Software Limited <http://transient.nz/>
New Zealand



  • 2017 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the thredds archives: