[SAC] [OSGeo] #2445: Issue with Maven OSGEO (repo.osgeo.org) - no remote packages available
OSGeo
trac_osgeo at osgeo.org
Fri May 8 00:59:58 PDT 2020
#2445: Issue with Maven OSGEO (repo.osgeo.org) - no remote packages available
---------------------------+------------------------
Reporter: robe | Owner: jive
Type: task | Status: assigned
Priority: normal | Milestone: Unplanned
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+------------------------
Comment (by meedel):
Jive,
I have an answer from support from Jfrog. ( Artifactory )
They say the following:
Hello Bert,
**It looks like Nexus 3.x doesn't offer an HTML Directory structure
through the URL the Artifacts need to be resolved from**. As you've
encountered, you can still resolve Artifacts but you won't be able to use
the Artifact browser.
If you would like to partially use the Artifact browser, use the following
setup:
1. Remote repository pointing to
https://repo.osgeo.org/repository/release/
2. Remote repository pointing to
https://repo.osgeo.org/service/rest/repository/browse/release/
3. Virtual repository containing both remote repositories.
This will allow you to view the directory structures of the Artifacts
before resolving through your build. You will not be able to download via
the UI as the files do not exist in the /service/ context. For example, if
you navigate to
https://repo.osgeo.org/service/rest/repository/browse/release/commons-
beanutils/commons-beanutils/, the folders maintain the /service/rest/
context, but the files switch to the /repository/release/ context.
To resolve the artifacts in a 2 step way is not an option for us.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2445#comment:24>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
More information about the Sac
mailing list