S things localised.
A comparitor class might also be valid though.
Maybe can be shared among the info classes with some magic superclass or interface additions.
Was a hot topic some 10 years ago, funny though, being talked about to date it seems: https://medium.com/better-programming/prefer-composition-over-inheritance-1602d5149ea1
public interface NamedCatalogInfo {
String getName();
default int compareByName(NamedCatalogInfo other) {
return getName().compareTo(other.getName()); // null handling missing here
}
would like to hear @jodygarnett opinion about this approach
although one might want to compare by qualified name too
that's why I tend to lean towards external comparators, there are so many ways comparisons can be done
Hi, I am trying to build and run a geoserver.war from current snapshots (with my community module code on top). My module runs into an Maps4HTML/geoserver#21. I would like to build and run a version of GeoServer from around the middle - end of last November, but is that possible, given the snapshots are generated (and thrown away?) each day? I would like to see if the problem is something I did or if it's a regression elsewhere. Thanks!
if you want the module to get better protection against these issues, you should consider applying for graduation, if/when that happens you'll get the test of the module run along with the build
Hi, I'm still in the process of building geoserver and I think I am getting close. I've switched to Intellij and find it much more user friendly. I've followed the steps in the developer manual and have gotten the following error when running a 'mvn clean install' on wcs1_1: Failure to transfer org.geoserver.security:gs-sec-jdbc:2.19-SNAPSHOT/maven-metadata.xml from https://maven.geo-solutions.it/ was cached in the local repository, resolution will not be reattempted until the update interval of geosolutions has elapsed or updates are forced. Original error: Could not transfer metadata org.geoserver.security:gs-sec-jdbc:2.19-SNAPSHOT/maven-metadata.xml from/to geosolutions (https://maven.geo-solutions.it/): Transfer failed for https://maven.geo-solutions.it/org/geoserver/security/gs-sec-jdbc/2.19-SNAPSHOT/maven-metadata.xml
Please let me know if there is a more appropriate place to ask this question.
PS When I go to https://maven.geo-solutions.it/org/geoserver/security/gs-sec-jdbc/2.19-SNAPSHOT/maven-metadata.xml in the browser I get a 404 error.
I believe maven is giving you an error based on the last repo it visited
Just to be sure, you're working on the master branch right?
@aime I built, tested and ran the changes in my community module's feature branch against the 2.18.1 tag, but I get the error described here Maps4HTML/geoserver#21 when trying to do the same on the 2.18.2 tag (I notice it's changing right up to today). I think the issue I'm having is related to GEOS-9800. I notice in that issue you suggest alternative setup possibilities (maybe instead of GWC.get()?). Do you have a link to descriptions of these alternatives? Thanks!
@al-tabb always happy to help a fellow developer
if you have at least 3 users and some time to put on it, I'd recomment pushing the module for extension status
it's going to avoid unpleasant suprises in the future (well, at least some!)
sounds like a "temporary situation" that became permanent