[SAC] [OSGeo] #2180: geotools maven repository missing?
OSGeo
trac_osgeo at osgeo.org
Fri Jul 6 10:41:34 PDT 2018
#2180: geotools maven repository missing?
---------------------------+-----------------------
Reporter: jive | Owner: sac@…
Type: task | Status: reopened
Priority: normal | Milestone:
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+-----------------------
Comment (by jive):
Replying to [comment:8 jef]:
> What ever is using this is constantly requesting non-existing stuff,
which get logged in download_error_log:
>
> {{{
> # head -1 /var/log/apache2/download_error_log
> [Thu Jul 05 09:39:01 2018] [error] [client X.X.X.X] File does not exist:
/osgeo/download/webdav/geotools/org/springframework/spring-core/2.0.5
> # wc -l /var/log/apache2/download_error_log
> 197851 /var/log/apache2/download_error_log
> # fgrep /osgeo/download/webdav/ /var/log/apache2/download_error_log | wc
-l
> 194565
> }}}
>
> ie. 197851 total errors in less than 24h - 194565 webdav requests.
>
The tool used is
The functionality is actually working as expected
1. For each project a number of repositories is configured.
2. Each dependency is represented by a "pom" (project object model) and
"jars", "javadocs", "source", etc... as required. The "pom" file describes
the dependency and what it needs in turn.
3. Maven uses this to build up a tree like a package manager and downloads
all the components needed as part of the build process.
4. For each dependency it asks each repository if they have it, and then
downloads from one of them.
{{{
Downloading from osgeo:
https://download.osgeo.org/webdav/geotools/org/codehaus/plexus/plexus-
io/2.0.3/plexus-io-2.0.3.pom
Downloading from boundless:
https://repo.boundlessgeo.com/snapshot/org/codehaus/plexus/plexus-io/2.0.3
/plexus-io-2.0.3.pom
Downloading from sonatype-snapshots:
https://oss.sonatype.org/content/repositories/snapshots/org/codehaus/plexus
/plexus-io/2.0.3/plexus-io-2.0.3.pom
Downloading from central:
https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.3
/plexus-io-2.0.3.pom
Downloaded from central:
https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.0.3
/plexus-io-2.0.3.pom (1.7 kB at 54 kB/s)
}}}
5. Because our repository is popular it is used by not only the geotools
build, but by all the projects that make use of geotools world wide. Each
of those projects is going to talk to us .. all the time.
There are two ways out:
a) Use a maven repository application (rather than web dev) for hosting
artifacts. Artififactory is used by boundless, Nexus is used by
LocationTech
b) Deploy on to "maven central" rather than out own repository.
The part of the maven infrastructure we are not making use of is called
"maven central", where each group responsible for a project can upload
their jars, which are then mirrored around the world.
My understanding is we are unable to unable to upload our jars because we
do not meet maven central policies ... our software depends on non open
source software ... Java Advanced Imaging.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2180#comment:10>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
More information about the Sac
mailing list