[SAC] [OSGeo] #2445: Issue with Maven OSGEO (repo.osgeo.org) - no remote packages available
OSGeo
trac_osgeo at osgeo.org
Sun Jun 14 23:03:30 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):
Hello Jive,
We stil have issues with it, but you can close this one.
The problem is within Artifactory.
The answer I got from Jfrog support was:
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.
Best regards,
John Wright
JFrog Support
We have tested the 2 step way to get the right information but that's not
working for us.
So we use the native repo url in our software.
Thanks for your support
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2445#comment:30>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
More information about the Sac
mailing list