-
-
Notifications
You must be signed in to change notification settings - Fork 489
Bolsena 2020
Link to the event: Bolsena Code Sprint 2020
- Timezone Planner
- 9:30 CEST: Australia/Europe
- 14:00 CEST: Europe/America
Day | Time | Topic | Chair | Participants |
---|---|---|---|---|
Monday | 9:30 CEST - 10:00 | Kick off | ||
16:00 CEST - 17:00 | Maven Build | |||
Tuesday | ||||
16:00 CEST - 17:00 | Java 11 Compatibility | |||
Wednesday | ||||
Thursday | ||||
Friday | ||||
Ideas:
- Date handling Improvement https://github.com/geonetwork/core-geonetwork/issues/1970
- Roadmap and Financial Planning
A recent proposal to use osgeo nexus repository has highlighted several areas where our build system is non-standard and there are opportunities to improve.
-
Consistent use of maven
jar
andzip
artifacts (rather than copying files between folders) will allow core-geonetwork artifacts and metadata101 schema plugins to be deployed to the nexus repository. See #4701. -
Use of maven war overlay allows the
webbapp
war to be smoothly reused, rather than forked, for those maintaining a custom configuration. -
A critical point of discussion in the use of
3.7
for the version number ofschema
,schema-core
and the handling of transitive dependencies by schema plugins. See discussion. -
Jody will provide a presentations on these topics on Monday.
The result of this activity should be build independence (checkout and build any directory), a faster development cycle for developers, and a better approach to managing schema plugins and custom WARs.
With master now making use of GeoTools 23.x we are no-longer blocked from pursuing Java 11 compatibility.
- This activity will evaluate Java 11 compatibility, with the goal of determining how much work is required
- The bulk of the work will be identifying dependencies that require updating or replacing
- There are a couple dependencies we use that are no longer maintained (we have our own fork of saxxon) which are a priority to review
The result of this activity is a plan of activities and dependencies to update.
Anyone available to update the current version 3.2.1 before 2 July. See
- https://docs.google.com/spreadsheets/d/1Q5BaEgQtgw4O1bXyeWMlM8XtAOhUgcjZ7Y2O0FZc2H0/edit#gid=430477653
- https://git.osgeo.org/gitea/osgeolive/OSGeoLive/src/branch/master/app-conf/geonetwork
- https://github.com/geonetwork/core-geonetwork/issues/4727
- Upgrade javascript platform / Generate typescript client / Use landing-page URL inside SPA
- OGC API Records / Serving and Querying records as HTML, JSON and XML
- Search / Boost series over member of a series / Boost matches on keyword/title
- Home / Custom facet on home page (https://taskman.eionet.europa.eu/issues/118112). Requires custom translations loaded from db (https://github.com/geonetwork/core-geonetwork/pull/4756)
- Finalize Spring5/JPA2 migration
If you have some comments, start a discussion, raise an issue or use one of our other communication channels to talk to us.