#23716 closed defect (fixed)
JOSM Nexus upgrade to version 3
Reported by: | taylor.smock | Owned by: | stoecker |
---|---|---|---|
Priority: | normal | Milestone: | 25.04 |
Component: | Trac | Version: | |
Keywords: | Cc: | stoecker |
Description
Hopefully this was a planned outage. If not, I hope it wasn't due to me fiddling with maven pom files (or maybe that would be better?).
Attachments (0)
Change History (39)
comment:1 by , 14 months ago
comment:2 by , 14 months ago
Summary: | JOSM Nexus is down → JOSM Nexus upgrade to version 3 |
---|
Doesn't start with java 11 as is. Maybe an update to version 3 is necessary.
follow-up: 4 comment:3 by , 14 months ago
It would probably be a good idea to do so -- I just looked at the release notes for 2.15.1 (2022-03-23), and it indicates that v2 will be EOL on 2025-06-30 (a bit over a year from now). Although it is probably EOL from a practical standpoint right now.
It looks like you got the nexus running again -- I assume it is by pointing it at a Java 8 JDK.
comment:4 by , 14 months ago
Replying to taylor.smock:
It looks like you got the nexus running again -- I assume it is by pointing it at a Java 8 JDK.
How do you know? ;-)
comment:5 by , 5 months ago
Beep beep boop, Sonatype will officially sunset its Nexus Repository 2 product on June 30, 2025.
Maybe add a milestone?
comment:6 by , 5 months ago
Milestone: | → 25.03 |
---|
comment:8 by , 5 months ago
comment:9 by , 4 months ago
Well, upgrade wizard is not available in the current install nexus-unix-x86-64-3.78.2-04.tar.gz ...
Wouldn't it be nice when sometimes the admin stuff would be easy?
comment:10 by , 4 months ago
I got nexus3 to work. Seems I will have to drop the old repo and start from scratch.
Probably anyway a good idea ;-)
comment:11 by , 4 months ago
Now Plugin build fails,
https://github.com/JOSM/continuos-download/actions/runs/14140337344/job/39630343512
because it can't find "SNAPSHOT", which is now named "1.5-SNAPSHOT". Any idea where I can find the place where that is specified?
comment:12 by , 4 months ago
Yep. Look for the pom.xml version
elements. I'll do a quick change on my computer and start a local build.
comment:13 by , 4 months ago
Actually, it is the <repo>
urls that changed. AFAICT anyway. Not the versioning (although changing that at the same time probably wouldn't be a bad idea -- maven doesn't like non-versioned snapshots).
comment:14 by , 4 months ago
The repo URL's I did change yesterday already (thought maybe I overlooked some places...)
But as I couldn't get deployment to work for SNAPSHOT I switched to 1.5-SNAPSHOT as well, which now causes issues (Note that 1.5 is still the official JOSM version :-)
It's repository/public/ or repository/releases/ or repository/snapshots/ BTW, whereas the first contains the later two.
With direct access via nexus it is nexus3/, but that should not be used.
comment:15 by , 4 months ago
OK. I didn't see 1.5-SNAPSHOT when I was looking through the nexus repository. But I was looking at the nexus2 instead of nexus3 endpoint.
EDIT: This should be enough:
-
plugins/pom.xml
36 36 <manifest.unixoid>MANIFEST-unixoid</manifest.unixoid> 37 37 <manifest.windows>MANIFEST-windows</manifest.windows> 38 38 <manifest.osx>MANIFEST-osx</manifest.osx> 39 <plugin.compile.version> SNAPSHOT</plugin.compile.version>39 <plugin.compile.version>1.5-SNAPSHOT</plugin.compile.version> 40 40 <plugin.jar>${project.name}.jar</plugin.jar> 41 41 <plugin.unixoid.jar>${project.name}-unixoid.jar</plugin.unixoid.jar> 42 42 <plugin.windows.jar>${project.name}-windows.jar</plugin.windows.jar>
I'll drop OsmInspectorPlugin
, sumoconvert
, and trustosm
from the module list and add markseen
.
comment:16 by , 4 months ago
See r36418/osm. Did the later already, but seems I catched the wrong line with the snapshot...
follow-up: 20 comment:19 by , 4 months ago
@stoecker: Did you update https://josm.openstreetmap.de/jenkins/job/Nexus-JOSM-Plugins/ to publish to 1.0-SNAPSHOT
instead of SNAPSHOT
?
If so, I'm currently going through and updating dependencies in pom.xml to use 1.0-SNAPSHOT
instead of just SNAPSHOT
.
comment:20 by , 4 months ago
Replying to taylor.smock:
@stoecker: Did you update https://josm.openstreetmap.de/jenkins/job/Nexus-JOSM-Plugins/ to publish to
1.0-SNAPSHOT
instead ofSNAPSHOT
?
Yes.
If so, I'm currently going through and updating dependencies in pom.xml to use
1.0-SNAPSHOT
instead of justSNAPSHOT
.
Wonderful.
I hope "continuos-download" will finally build. My ideas for useful changes to trigger rebuilds gets low... ;-)
follow-up: 32 comment:21 by , 4 months ago
Milestone: | 25.03 → 25.04 |
---|
Ok. "continuos-download" did build. Yeah.
Current status:
- nexus3 repo seems to work properly.
- I dropped all proxy handling and old repos from nexus2
- nexus2 keeps the old snapshots and release repositories for now.
- There is a proxy for the old JOSM releases repo in nexus3
(needed for JMapViewer)
- There is a proxy for the old JOSM releases repo in nexus3
- pushing artifacts has been changed to nexus3
nexus3 is currently missing a single JOSM release (will be fixed tomorrow)nexus3 is missing JMapViewer (I'll probably do a bit code cleanup to get a new release :-)JMapViewer-2.24 imported into nexus3- jmockit-1.49a imported into nexus3
I don't plan to import the old releases into the new instance.
I'll turn off nexus2 next month dropping old releases and snapshots.
follow-up: 26 comment:25 by , 4 months ago
continuous-download builds have been fixed. We might have to manually trigger some builds (but probably not; only thing that changed for most of the plugins was the build scripts).
comment:26 by , 4 months ago
Replying to taylor.smock:
continuous-download builds have been fixed. We might have to manually trigger some builds (but probably not; only thing that changed for most of the plugins was the build scripts).
I will do that middle of next week with the I18n update (Greek language approaches 100% coverage for plugins as well). That should be enough.
comment:27 by , 4 months ago
Can you please update the nexus link here? There is already a report #24241.
comment:28 by , 4 months ago
Can you verify if https://josm.openstreetmap.de/repository/public/
is correct as value?
comment:30 by , 4 months ago
Yup, manually putting https://josm.openstreetmap.de/repository/public/
in the imageio.nexus.url
key makes it work, I see no more exceptions.
2025-03-31 12:19:20.780 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/imageio/imageio-webp/maven-metadata.xml -> HTTP/1.1 200 (773 ms; 805 B) 2025-03-31 12:19:21.138 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/imageio/imageio-webp/3.12.0/imageio-webp-3.12.0.pom -> HTTP/1.1 200 (254 ms; 1,81 kB) 2025-03-31 12:19:21.498 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/imageio/imageio-core/maven-metadata.xml -> HTTP/1.1 200 (258 ms; 1,44 kB) 2025-03-31 12:19:21.845 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/imageio/imageio-core/3.12.0/imageio-core-3.12.0.pom -> HTTP/1.1 200 (244 ms; 1,76 kB) 2025-03-31 12:19:22.203 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/common/common-lang/maven-metadata.xml -> HTTP/1.1 200 (256 ms; 1,44 kB) 2025-03-31 12:19:22.549 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/common/common-lang/3.12.0/common-lang-3.12.0.pom -> HTTP/1.1 200 (243 ms; 998 B) 2025-03-31 12:19:22.911 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/common/common-io/maven-metadata.xml -> HTTP/1.1 200 (260 ms; 1,44 kB) 2025-03-31 12:19:23.256 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/common/common-io/3.12.0/common-io-3.12.0.pom -> HTTP/1.1 200 (242 ms; 1,33 kB) 2025-03-31 12:19:23.619 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/common/common-image/maven-metadata.xml -> HTTP/1.1 200 (259 ms; 1,44 kB) 2025-03-31 12:19:23.964 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/common/common-image/3.12.0/common-image-3.12.0.pom -> HTTP/1.1 200 (243 ms; 1,28 kB) 2025-03-31 12:19:24.329 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/imageio/imageio-metadata/maven-metadata.xml -> HTTP/1.1 200 (261 ms; 1,45 kB) 2025-03-31 12:19:24.678 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/imageio/imageio-metadata/3.12.0/imageio-metadata-3.12.0.pom -> HTTP/1.1 200 (247 ms; 1,34 kB) 2025-03-31 12:19:25.031 INFO: HEAD https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/common/common-image/3.12.0/common-image-3.12.0.jar -> HTTP/1.1 200 (245 ms; 77,8 kB) 2025-03-31 12:19:25.172 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/common/common-image/3.12.0/common-image-3.12.0.jar -> HTTP/1.1 200 (40 ms; 77,8 kB) 2025-03-31 12:19:25.681 INFO: HEAD https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/common/common-io/3.12.0/common-io-3.12.0.jar -> HTTP/1.1 200 (326 ms; 90,2 kB) 2025-03-31 12:19:25.822 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/common/common-io/3.12.0/common-io-3.12.0.jar -> HTTP/1.1 200 (40 ms; 90,2 kB) 2025-03-31 12:19:26.324 INFO: HEAD https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/common/common-lang/3.12.0/common-lang-3.12.0.jar -> HTTP/1.1 200 (324 ms; 119 kB) 2025-03-31 12:19:26.466 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/common/common-lang/3.12.0/common-lang-3.12.0.jar -> HTTP/1.1 200 (40 ms; 119 kB) 2025-03-31 12:19:27.002 INFO: HEAD https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/imageio/imageio-core/3.12.0/imageio-core-3.12.0.jar -> HTTP/1.1 200 (321 ms; 117 kB) 2025-03-31 12:19:27.142 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/imageio/imageio-core/3.12.0/imageio-core-3.12.0.jar -> HTTP/1.1 200 (39 ms; 117 kB) 2025-03-31 12:19:27.680 INFO: HEAD https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/imageio/imageio-metadata/3.12.0/imageio-metadata-3.12.0.jar -> HTTP/1.1 200 (325 ms; 81,7 kB) 2025-03-31 12:19:27.821 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/imageio/imageio-metadata/3.12.0/imageio-metadata-3.12.0.jar -> HTTP/1.1 200 (40 ms; 81,7 kB) 2025-03-31 12:19:28.322 INFO: HEAD https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/imageio/imageio-webp/3.12.0/imageio-webp-3.12.0.jar -> HTTP/1.1 200 (323 ms; 77,8 kB) 2025-03-31 12:19:28.464 INFO: GET https://josm.openstreetmap.de/repository/public/com/twelvemonkeys/imageio/imageio-webp/3.12.0/imageio-webp-3.12.0.jar -> HTTP/1.1 200 (40 ms; 77,8 kB)
comment:32 by , 4 months ago
Replying to stoecker:
I don't plan to import the old releases into the new instance.
I'll turn off nexus2 next month dropping old releases and snapshots.
Can I ask you to keep them for at least a bit longer? It may be overhead now, but for checking old tickets and for plugin development it is very useful to have these old snapshots like we have today. For example, in the JOSM gradle plugin, I can write the release number and it will compile with that JOSM version. If there won't be any old releases, it will break :(
Sure, I can compile them manually if I'm really into (I'm not). If you decide to remove them anyway, that's fine, I can accept it, but it might be worth giving the external plugin developers some more time to adapt their code.
comment:33 by , 4 months ago
I will not keep the old instance. That would make the whole update idea useless.
All the nightly builds are available via download/ or download/Archiv.
If you can convince me, that it is life-critical that we somehow provide these via nexus we probably can find a way, but I think it should be possible to use them as they are.
comment:34 by , 4 months ago
IIRC, the gradle plugin uses the /download/Archiv and /download pages for JOSM, and it parses the /plugin page for plugins. So gradle plugin users probably won't be affected.
EDIT: Documentation: https://gitlab.com/JOSM/gradle-josm-plugin/-/blob/main/plugin/src/main/kotlin/org/openstreetmap/josm/gradle/plugin/config/JosmPluginExtension.kt#L223-229
follow-up: 36 comment:35 by , 4 months ago
Yeah, it falls back to non Nexus sources if it cannot find it there. That's okay, but one leg shot down ;)
If the download/ remains there as it is, then it's perfectly fine. I initially thought that it's somehow connected to Nexus, but seems not, which is good.
comment:36 by , 4 months ago
Replying to gaben:
Yeah, it falls back to non Nexus sources if it cannot find it there. That's okay, but one leg shot down ;)
Nah. The new nexus again has the same data and the very old stuff get's less and less important each day :-)
Simply like an auto-delete gone amok...
If the download/ remains there as it is, then it's perfectly fine. I initially thought that it's somehow connected to Nexus, but seems not, which is good.
These are the nightly builds. I manually move the older ones to Archiv from time to time.
comment:37 by , 4 months ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Upgrade finished. I hope we can stay below the 200000 hits/day which the community version allows.
comment:38 by , 4 months ago
Thanks for your effort! Do you have some spare energy to start looking at #24164? Let me know if I can assist somehow.
comment:39 by , 4 months ago
It's the next task I'll start. But first I hope to have at least one weekend where I can ride my motorbike without freezing my ass off. ;-)
If it is up and running I'll appreciate any help with fine tuning configuration and fixing imported data...
Didn't survive restart. I'll have a look what's wrong. Systemd service thinks its working ;-)