Since I could not understand what was happening, I rolled out another docker container, using the exact same image and did the deploy using the same file (the file is stored on nexus). This time everything worked fine.
The problem I have is, I need to be able to deploy the bundle on the first container which is on my production environment and it has all my repositories and configurations which I migrated from nexus 2.
Just a bit more information on the first installation, the /nexus-data folder is mapped to a volume which was created when we migrated from nexus2. If I am not mistaken, the first container we used was version 3.12. We have upgraded the container to version 3.21.2, by replacing the container but keeping the nexus-data volume.
Has anyone seen anything similar? Does anyone know how I can fix this or has any pointers to what I should be looking at?
Hi Bruno,
Were you using composer pre-kar or is this your first attempt at it?
I wonder if there was existing stuff in there if it’s now conflicting.
Just a random guess.
-Joe
Correct me if I am wrong, but altering the pom file would be an action I would take if I was developing a plugin for nexus or building nexus from source.
I am not sure what to do as the plugin I am using already builds into a kar file. The kar file that is built works on a clean nexus3 container, but it does not work on my existing production container, which had data migrated from a nexus2 repository and was upgrade from a previous version.
The plugin has to be built to match the Nexus Repo version you are running, you can’t count on a plugin built for a different version working. So you should modify the version in the pom to match your current version.