sonatype / nexus-public Goto Github PK

Sonatype Nexus Repository Open-source codebase mirror

Home Page: https://www.sonatype.com/products/repository-oss-download

License: Eclipse Public License 1.0

Java 52.49% Shell 0.08% Batchfile 0.08% HTML 0.27% Groovy 4.26% CSS 4.44% JavaScript 37.84% Ruby 0.01% XSLT 0.01% SCSS 0.53%

repository repository-management

nexus-public's Introduction

Sonatype Nexus Repository Open Source Codebase

Downloadable Bundles

See: https://www.sonatype.com/download-oss-sonatype

Support

Using Sonatype Nexus Repository OSS and need to report an issue? Open an issue here

Sonatype Nexus Repository Pro customers can use https://support.sonatype.com/.

Build Requirements

Builds use Apache Maven and require Java 8. Apache Maven wrapper scripts are included in the source tree.

All release versioned dependencies should be available from the Central repository.

For SNAPSHOT sources, SNAPSHOT versioned dependencies may only be available from https://repository.sonatype.org/content/groups/sonatype-public-grid repository.

Configuring Maven for SNAPSHOT Dependencies

Following best practices, the nexus-public POM does not include any root <repositories> elements.

Instead you are advised to configure Apache Maven to point at single repository mirror URL that is a group repository containing both Central proxy repository with Release version policy and sonatype-public-grid with a SNAPSHOT version policy. You can use a repository manager to set up a group repository that contains both of these remotes.

Alternately, add a custom profile to a settings.xml for repository manager development that includes both repositories.

Building From Source

Released versions are tagged and branched using a name of the form release-{version}. For example: release-3.29.2-02

To build a tagged release, first fetch all tags:

git fetch --tags

Then checkout the remote branch you want. For example:

git checkout -b release-3.29.2-02 origin/release-3.29.2-02 --

Then build using the included Maven wrapper script. For example:

./mvnw clean install

For building SNAPSHOT versions, follow the same process, except your build may require access to Sonatype Public Grid to successfully resolve dependencies.

Running

To run Nexus Repository, after building, unzip the assembly and start the server:

unzip -d target assemblies/nexus-base-template/target/nexus-base-template-*.zip
./target/nexus-base-template-*/bin/nexus console

The nexus-base-template assembly is used as the basis for the official Sonatype Nexus Repository distributions.

License

This project is licensed under the Eclipse Public License - v 1.0, you can read the full text here

Getting help

Looking to contribute to our code but need some help? There's a few ways to get information or our attention:

Check out the Nexus3 tag on Stack Overflow
Check out the Nexus Repository User List
Connect with @sonatypeDev on Twitter

nexus-public's People

Contributors

Stargazers

Watchers

Forkers

simonzhao biliroy lchcoming feng-zh lifan3333 sim-liu leichunxin linbercsu criteo-forks wpbird007 prikkeldraad sunatthegilddotcom dskarthick louisburton nafeger layer3switch googlezhang thiagogarciaalves carlosmanoel hey-xico kettas pombredanne cstamas flatwhite idstein qiankunshe th3architect dweomer patrickcrocker ericdcobb amazon kreuz ironpinguin sis-tools amberfan nitin-tiwari mkutter muyun12 dejan2609 331520 ian4hu javascriptextjs dawuid jiapei100 hubspot zhoffice kazuki43zoo antonini walmartlabs hbenamara timperry1994 jred1989 sunyuyangg123 kurtdegreeff ahirata aimwts zhongyitech motias sghill talend mattlk13 r351574nc3 sesuncedu lhfbalance chenqiangzhishen xiaomuqiao niaiwoya doug-wade peng1916 leima-hit jcruzcruz mihua682 samitp12 yangyimeng gitter-badger mykelalvis mkristian huanle0610 roman-blinkov fxbonnet wqn09003 rvsoni qiuweiwen onpex mbenson nongfenqi nikai1006 belgacom-ics albertoesteva88 robertzsiak dataman-caiwanli tneer adrian-galbenus inversogmbh yinjian6931 xiaodu1993 chipson04 micombs27 ischindl yuanman

nexus-public's Issues

[NEXUS-36614] The "dockerProxy.useTrustStoreForIndexAccess" field is missing in the REST API for proxied Docker repositories

(Manually copied from https://issues.sonatype.org/browse/NEXUS-36614 as that JIRA is going to be shut down but the issue is not resolved yet)

The /v1/repositories/docker/proxy/{repositoryName} endpoint in Sonatype Nexus does not return the useTrustStoreForIndexAccess field under dockerProxy.

How to reproduce:

Create a docker proxy repository
Ensure the second "Use the Nexus Repository truststore:" option is checked
Request the endpoint through the API (in my example it's named docker.io):

curl -X 'GET' \
 'http://your_ip:8081/service/rest/v1/repositories/docker/proxy/docker.io' \
 -H 'accept: application/json'

Observe there is only a single truststore related entry in the output and it is false

{
  "name": "docker.io",
  "url": "http://your_ip:8081/repository/docker.io",
  "online": true,
  "storage": {
    "blobStoreName": "default",
    "strictContentTypeValidation": true,
    "writePolicy": "ALLOW"
  },
  "cleanup": null,
  "docker": {
    "v1Enabled": true,
    "forceBasicAuth": true,
    "httpPort": null,
    "httpsPort": null,
    "subdomain": null
  },
  "dockerProxy": {
    "indexType": "HUB",
    "indexUrl": null,
    "cacheForeignLayers": false,
    "foreignLayerUrlWhitelist": []
  },
  "proxy": {
    "remoteUrl": "https://registry-1.docker.io",
    "contentMaxAge": 1440,
    "metadataMaxAge": 1440
  },
  "negativeCache": {
    "enabled": true,
    "timeToLive": 1440
  },
  "httpClient": {
    "blocked": false,
    "autoBlock": false,
    "connection": {
      "retries": null,
      "userAgentSuffix": null,
      "timeout": null,
      "enableCircularRedirects": false,
      "enableCookies": false,
      "useTrustStore": false
    },
    "authentication": null
  },
  "routingRuleName": null,
  "format": "docker",
  "type": "proxy"
}

Note: the relevant HTML element for the checkbox contains the following:

name="attributes.dockerProxy.useTrustStoreForIndexAccess"

It is also impossible to update this value through the API, as sending the dockerProxy.useTrustStoreForIndexAccess key will not change the setting (and thus updating the settings through the API will always uncheck this checkbox). This makes it impossible to use the API safely for Docker proxy repositories that need this setting.

[NEXUS-26809] Unclear documentation regarding repository health checks

Nexus version OSS 3.34.1-01

When I look at the list of repositories, I see this:

When I hover over the RHC of maven-central, I see this:

Now when I click the "What should I do with this report?" link, I'm taken to https://blog.sonatype.com/is-manual-remediation-with-repository-health-check-as-good-as-it-gets which looks greatly different and for example shows which libraries have vulnerabilities.

The blog post says, that with Pro you can also see which vulnerabilities there are, but with OSS you can at least see which components have issues.

Did this change?
Can you now only see the overall summary and for more information you need Pro?
If so, the help link should be removed, or updated to some more recent documentation or the blog post updated.

And if this information is still available, then it should be better documented where to see it.
That blog post doesn't mention anything or I missed it and the documentation is also pretty sparse regarding that.

NEXUS-37899: yum proxy repo fails when rpms are on different base url

You can proxy a yum repo. But when the repodata xml points to a different base url for the rpm files, that base url is removed by Nexus from the repodata, and the download fails.

e.g. for https://aquasecurity.github.io/trivy-repo/ we can add a proxy that maps [https://aquasecurity.github.io/trivy-repo/] to [https://nexus-url/repository/trivy-repo/]. We can use

[trivy]
 name=Trivy repository
baseurl=https://nexus-url/repository/trivy-repo/rpm/releases/$releasever/$basearch/
 gpgcheck=0
enabled=1

The repodata [https://aquasecurity.github.io/trivy-repo/rpm/releases/7/x86_64/repodata/repomd.xml] will list the primary lists.
But the lists (e.g. 52e23160ff9262f84dac766497b7dddf98632d05958bf719f06d87461bae2fbd-primary.xml) then will list the RPMs as:
<location xml:base="https://github.com/aquasecurity/trivy/releases/download/" href="v0.41.0/trivy-0.32.0.el7.x86_64.rpm"/>
(notice the absolute URL).

When you download the same xml via Nexus, the base= part is gone. It just says <location href="v0.41.0/trivy-0.32.0.el7.x86_64.rpm"></location>

This results in a 404 when doing yum install:

Downloading packages:
https://nexus-url/repository/trivy-repo/rpm/releases/7/x86_64/v0.41.0/trivy_0.41.0_Linux-64bit.rpm: [Errno 14] HTTPS Error 404 - Not Found

Do you have a workaround you are using at present?
I can make it work by proxying https://github.com/aquasecurity/trivy/releases/download/ AND https://aquasecurity.github.io/trivy-repo/rpm/releases/7/x86_64 (note that I have to include version and architecture here, to make relative paths match) and use a group repo to combine the two. But this is very ugly.
What feature or behavior is this required for?
proxying yum repos
How could we solve this issue? (Not knowing is okay!)
make Nexus proxy the given base urls too
Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?
Nexus OSS 3.53.1-02
Anything else?
https://issues.sonatype.org/browse/NEXUS-37899 is a duplicate.

[NEXUS-28906] Updating or creating a repository with non-existent routing rule via REST does not fail

Nexus version OSS 3.33.0

I update or create repositories via REST API.
While doing so, I also configure routing rules.
If you update or create a repository with a non-existing routing rule,
the request is simply successful without a routing rule being set.
Instead I'd have exepcted the call to fail.

Permission Error after restarting Nexus on K8s

What problem are you trying to solve?
Nexus not starting with current error output

Defaulted container "nexus" out of: nexus, volume-mount-hack (init)
^[[A2023-05-24 15:59:42,373+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.pax.logging.NexusLogActivator - start
2023-05-24 15:59:42,553+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.log)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.log.cfg
2023-05-24 15:59:42,575+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=jmx.acl)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/jmx.acl.cfg
2023-05-24 15:59:42,597+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.ops4j.pax.url.mvn)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.ops4j.pax.url.mvn.cfg
2023-05-24 15:59:42,613+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.features)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.features.cfg
2023-05-24 15:59:42,637+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=profile)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/profile.cfg
2023-05-24 15:59:42,652+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.felix.fileinstall~deploy)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.felix.fileinstall-deploy.cfg
2023-05-24 15:59:42,668+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.kar)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.kar.cfg
2023-05-24 15:59:42,684+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.shell)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.shell.cfg
2023-05-24 15:59:42,702+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.service.acl.command)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.service.acl.command.cfg
2023-05-24 15:59:42,717+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.management)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.management.cfg
2023-05-24 15:59:42,732+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.apache.karaf.jaas)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.apache.karaf.jaas.cfg
2023-05-24 15:59:42,742+0000 WARN  [CM Event Dispatcher (Fire ConfigurationEvent: pid=org.ops4j.pax.logging)] *SYSTEM org.apache.felix.fileinstall - File is not writeable: file:/opt/sonatype/nexus/etc/karaf/org.ops4j.pax.logging.cfg
2023-05-24 15:59:43,078+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.features.internal.FeaturesWrapper - Fast FeaturesService starting
2023-05-24 15:59:44,731+0000 INFO  [FelixStartLevel] *SYSTEM ROOT - bundle org.apache.felix.scr:2.1.30 (57) Starting with globalExtender setting: false
2023-05-24 15:59:44,740+0000 INFO  [FelixStartLevel] *SYSTEM ROOT - bundle org.apache.felix.scr:2.1.30 (57)  Version = 2.1.30
2023-05-24 15:59:45,168+0000 WARN  [FelixStartLevel] *SYSTEM uk.org.lidalia.sysoutslf4j.context.SysOutOverSLF4JInitialiser - Your logging framework class org.ops4j.pax.logging.slf4j.Slf4jLogger is not known - if it needs access to the standard println methods on the console you will need to register it by calling registerLoggingSystemPackage
2023-05-24 15:59:45,178+0000 INFO  [FelixStartLevel] *SYSTEM uk.org.lidalia.sysoutslf4j.context.SysOutOverSLF4J - Package org.ops4j.pax.logging.slf4j registered; all classes within it or subpackages of it will be allowed to print to System.out and System.err
2023-05-24 15:59:45,187+0000 INFO  [FelixStartLevel] *SYSTEM uk.org.lidalia.sysoutslf4j.context.SysOutOverSLF4J - Replaced standard System.out and System.err PrintStreams with SLF4JPrintStreams
2023-05-24 15:59:45,191+0000 INFO  [FelixStartLevel] *SYSTEM uk.org.lidalia.sysoutslf4j.context.SysOutOverSLF4J - Redirected System.out and System.err to SLF4J for this context
2023-05-24 15:59:45,202+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder - Properties:
2023-05-24 15:59:45,203+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   application-host='0.0.0.0'
2023-05-24 15:59:45,204+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   application-port='8081'
2023-05-24 15:59:45,204+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   fabric.etc='/opt/sonatype/nexus/etc/fabric'
2023-05-24 15:59:45,206+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   jetty.etc='/opt/sonatype/nexus/etc/jetty'
2023-05-24 15:59:45,206+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   karaf.base='/opt/sonatype/nexus'
2023-05-24 15:59:45,207+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   karaf.data='/nexus-data'
2023-05-24 15:59:45,212+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   karaf.etc='/opt/sonatype/nexus/etc/karaf'
2023-05-24 15:59:45,213+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   karaf.home='/opt/sonatype/nexus'
2023-05-24 15:59:45,214+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   karaf.instances='/nexus-data/instances'
2023-05-24 15:59:45,215+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   logback.etc='/opt/sonatype/nexus/etc/logback'
2023-05-24 15:59:45,215+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   nexus-args='/opt/sonatype/nexus/etc/jetty/jetty.xml,/opt/sonatype/nexus/etc/jetty/jetty-http.xml,/opt/sonatype/nexus/etc/jetty/jetty-requestlog.xml'
2023-05-24 15:59:45,216+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   nexus-context-path='/'
2023-05-24 15:59:45,218+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   nexus-edition='nexus-pro-edition'
2023-05-24 15:59:45,219+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   nexus-features='nexus-pro-feature'
2023-05-24 15:59:45,219+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   nexus.hazelcast.discovery.isEnabled='true'
2023-05-24 15:59:45,220+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.ConfigurationBuilder -   ssl.etc='/opt/sonatype/nexus/etc/ssl'
2023-05-24 15:59:45,221+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.Launcher - Java: 1.8.0_372, OpenJDK 64-Bit Server VM, Red Hat, Inc., 25.372-b07
2023-05-24 15:59:45,223+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.Launcher - OS: Linux, 6.0.0-5-amd64, amd64
2023-05-24 15:59:45,223+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.Launcher - User: nexus, en, /opt/sonatype/nexus
2023-05-24 15:59:45,223+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.Launcher - CWD: /opt/sonatype/nexus
2023-05-24 15:59:45,229+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.Launcher - TMP: /nexus-data/tmp
2023-05-24 15:59:45,233+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.jetty.JettyServer - Starting
2023-05-24 15:59:45,241+0000 INFO  [FelixStartLevel] *SYSTEM org.eclipse.jetty.util.log - Logging initialized @5983ms to org.eclipse.jetty.util.log.Slf4jLog
2023-05-24 15:59:45,247+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.jetty.JettyServer - Applying configuration: file:/opt/sonatype/nexus/etc/jetty/jetty.xml
2023-05-24 15:59:45,482+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.jetty.JettyServer - Applying configuration: file:/opt/sonatype/nexus/etc/jetty/jetty-http.xml
2023-05-24 15:59:45,541+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.bootstrap.jetty.JettyServer - Applying configuration: file:/opt/sonatype/nexus/etc/jetty/jetty-requestlog.xml
2023-05-24 15:59:45,561+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.bootstrap.jetty.JettyServer - Starting: Server@5168050c{STOPPED}[9.4.51.v20230217]
2023-05-24 15:59:45,573+0000 INFO  [jetty-main-1] *SYSTEM org.eclipse.jetty.server.Server - jetty-9.4.51.v20230217; built: 2023-02-17T08:19:37.309Z; git: b45c405e4544384de066f814ed42ae3dceacdd49; jvm 1.8.0_372-b07
2023-05-24 15:59:45,661+0000 INFO  [jetty-main-1] *SYSTEM org.eclipse.jetty.server.session - DefaultSessionIdManager workerName=node0
2023-05-24 15:59:45,663+0000 INFO  [jetty-main-1] *SYSTEM org.eclipse.jetty.server.session - No SessionScavenger set, using defaults
2023-05-24 15:59:45,665+0000 INFO  [jetty-main-1] *SYSTEM org.eclipse.jetty.server.session - node0 Scavenging every 660000ms
2023-05-24 15:59:45,674+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.bootstrap.osgi.BootstrapListener - Initializing
2023-05-24 15:59:45,684+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.bootstrap.osgi.BootstrapListener - Loading OSS Edition
2023-05-24 15:59:45,687+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.bootstrap.osgi.BootstrapListener - Installing: nexus-oss-edition/3.54.1.01 (nexus-orient/3.54.1.01)
2023-05-24 15:59:49,516+0000 INFO  [jetty-main-1] *SYSTEM org.ehcache.core.osgi.EhcacheActivator - Detected OSGi Environment (core is in bundle: org.ehcache [137]): Using OSGi Based Service Loading
2023-05-24 15:59:50,188+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.bootstrap.osgi.BootstrapListener - Installed: nexus-oss-edition/3.54.1.01 (nexus-orient/3.54.1.01)
2023-05-24 15:59:50,791+0000 INFO  [jetty-main-1] *SYSTEM org.apache.shiro.nexus.NexusWebSessionManager - Global session timeout: 1800000 ms
2023-05-24 15:59:50,793+0000 INFO  [jetty-main-1] *SYSTEM org.apache.shiro.nexus.NexusWebSessionManager - Session-cookie prototype: name=NXSESSIONID
2023-05-24 15:59:50,880+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.common [3.54.1.01]
2023-05-24 15:59:51,063+0000 INFO  [jetty-main-1] *SYSTEM org.hibernate.validator.internal.util.Version - HV000001: Hibernate Validator 6.2.0.Final
2023-05-24 15:59:51,303+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.common [3.54.1.01]
2023-05-24 15:59:51,305+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.hibernate.validator [6.2.0.Final]
2023-05-24 15:59:51,336+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.hibernate.validator [6.2.0.Final]
2023-05-24 15:59:51,338+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.cache [3.54.1.01]
2023-05-24 15:59:51,392+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.cache [3.54.1.01]
2023-05-24 15:59:51,396+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.supportzip-api [3.54.1.01]
2023-05-24 15:59:51,463+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.supportzip-api [3.54.1.01]
2023-05-24 15:59:51,468+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.crypto [3.54.1.01]
2023-05-24 15:59:51,634+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.crypto [3.54.1.01]
2023-05-24 15:59:51,636+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.security [3.54.1.01]
2023-05-24 15:59:52,166+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.security [3.54.1.01]
2023-05-24 15:59:52,166+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.thread [3.54.1.01]
2023-05-24 15:59:52,189+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.thread [3.54.1.01]
2023-05-24 15:59:52,190+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.scheduling [3.54.1.01]
2023-05-24 15:59:52,262+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.scheduling [3.54.1.01]
2023-05-24 15:59:52,263+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.blobstore [3.54.1.01]
2023-05-24 15:59:52,340+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.blobstore [3.54.1.01]
2023-05-24 15:59:52,340+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.apache.tika.core [1.28.4]
2023-05-24 15:59:52,372+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.apache.tika.core [1.28.4]
2023-05-24 15:59:52,374+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.jmx [3.54.1.01]
2023-05-24 15:59:52,402+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.jmx [3.54.1.01]
2023-05-24 15:59:52,404+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.datastore [3.54.1.01]
2023-05-24 15:59:52,446+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.datastore [3.54.1.01]
2023-05-24 15:59:52,447+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.orient [3.54.1.01]
2023-05-24 15:59:52,553+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.orient [3.54.1.01]
2023-05-24 15:59:52,553+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.upgrade [3.54.1.01]
2023-05-24 15:59:52,584+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.upgrade [3.54.1.01]
2023-05-24 15:59:52,584+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.blobstore-file [3.54.1.01]
2023-05-24 15:59:52,666+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.blobstore-file [3.54.1.01]
2023-05-24 15:59:52,668+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.capability [3.54.1.01]
2023-05-24 15:59:52,706+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.capability [3.54.1.01]
2023-05-24 15:59:52,709+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.commands [3.54.1.01]
2023-05-24 15:59:52,733+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.commands [3.54.1.01]
2023-05-24 15:59:52,733+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.email [3.54.1.01]
2023-05-24 15:59:52,754+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.email [3.54.1.01]
2023-05-24 15:59:52,756+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.httpclient [3.54.1.01]
2023-05-24 15:59:52,784+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.httpclient [3.54.1.01]
2023-05-24 15:59:52,786+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.servlet [3.54.1.01]
2023-05-24 15:59:52,805+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.servlet [3.54.1.01]
2023-05-24 15:59:52,806+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.ssl [3.54.1.01]
2023-05-24 15:59:52,821+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.ssl [3.54.1.01]
2023-05-24 15:59:52,822+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.base [3.54.1.01]
2023-05-24 15:59:53,005+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.internal.metrics.MetricsModule - Metrics support configured
2023-05-24 15:59:53,046+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.internal.metrics.MetricsModule - Metrics support configured
2023-05-24 15:59:53,723+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.base [3.54.1.01]
2023-05-24 15:59:53,724+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.extdirect [3.54.1.01]
2023-05-24 15:59:53,827+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.extdirect [3.54.1.01]
2023-05-24 15:59:53,830+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.siesta [3.54.1.01]
2023-05-24 15:59:53,951+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.siesta [3.54.1.01]
2023-05-24 15:59:53,953+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.rest-jackson2 [3.54.1.01]
2023-05-24 15:59:53,977+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.rest-jackson2 [3.54.1.01]
2023-05-24 15:59:53,979+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.swagger [3.54.1.01]
2023-05-24 15:59:54,029+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.swagger [3.54.1.01]
2023-05-24 15:59:54,031+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.rapture [3.54.1.01]
2023-05-24 15:59:54,225+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.rapture [3.54.1.01]
2023-05-24 15:59:54,228+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.datastore-mybatis [3.54.1.01]
2023-05-24 15:59:54,284+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.datastore-mybatis [3.54.1.01]
2023-05-24 15:59:54,285+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.quartz [3.54.1.01]
2023-05-24 15:59:54,382+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.quartz [3.54.1.01]
2023-05-24 15:59:54,384+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.oss-edition [3.54.1.01]
2023-05-24 15:59:54,417+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.oss-edition [3.54.1.01]
2023-05-24 15:59:54,422+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusContextListener - Running lifecycle phases [KERNEL, STORAGE, RESTORE, UPGRADE, SCHEMAS, EVENTS, SECURITY, SERVICES, CAPABILITIES, TASKS]
2023-05-24 15:59:54,426+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusLifecycleManager - Start KERNEL
2023-05-24 15:59:54,430+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.internal.log.overrides.file.LogbackLoggerOverrides - File: /nexus-data/etc/logback/logback-overrides.xml
2023-05-24 15:59:54,436+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.internal.log.LogbackLogManager - Configuring
2023-05-24 15:59:54,472+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusContextListener - Installing: [nexus-oss-feature/3.54.1.01, nexus-cma-extra/3.54.1.01, nexus-ossindex-plugin/3.54.1.01]
2023-05-24 16:00:09,745+0000 INFO  [jetty-main-1] *SYSTEM org.sonatype.nexus.extender.NexusContextListener - Installed: [nexus-oss-feature/3.54.1.01, nexus-cma-extra/3.54.1.01, nexus-ossindex-plugin/3.54.1.01]
2023-05-24 16:00:10,035+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.plugins.nexus-audit-plugin [3.54.1.01]
2023-05-24 16:00:10,524+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.plugins.nexus-audit-plugin [3.54.1.01]
2023-05-24 16:00:10,723+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.plugins.nexus-ssl-plugin [3.54.1.01]
2023-05-24 16:00:10,792+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.plugins.nexus-ssl-plugin [3.54.1.01]
2023-05-24 16:00:11,370+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.selector [3.54.1.01]
2023-05-24 16:00:11,415+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.selector [3.54.1.01]
2023-05-24 16:00:11,418+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.elasticsearch [3.54.1.01]
2023-05-24 16:00:11,456+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.elasticsearch [3.54.1.01]
2023-05-24 16:00:11,462+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.repository-content [3.54.1.01]
2023-05-24 16:00:12,017+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.repository-content [3.54.1.01]
2023-05-24 16:00:12,020+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.repository-config [3.54.1.01]
2023-05-24 16:00:12,114+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.repository-config [3.54.1.01]
2023-05-24 16:00:12,117+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.plugins.nexus-coreui-plugin [3.54.1.01]
2023-05-24 16:00:12,341+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.plugins.nexus-coreui-plugin [3.54.1.01]
2023-05-24 16:00:12,366+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.plugins.nexus-repository-httpbridge [3.54.1.01]
2023-05-24 16:00:12,416+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.plugins.nexus-repository-httpbridge [3.54.1.01]
2023-05-24 16:00:12,563+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.plugins.nexus-blobstore-tasks [3.54.1.01]
2023-05-24 16:00:12,596+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.plugins.nexus-blobstore-tasks [3.54.1.01]
2023-05-24 16:00:12,598+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.cleanup-config [3.54.1.01]
2023-05-24 16:00:12,638+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.cleanup-config [3.54.1.01]
2023-05-24 16:00:12,639+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.plugins.nexus-repository-maven [3.54.1.01]
2023-05-24 16:00:12,836+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.plugins.nexus-repository-maven [3.54.1.01]
2023-05-24 16:00:12,837+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.plugins.nexus-script-plugin [3.54.1.01]
2023-05-24 16:00:12,891+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.plugins.nexus-script-plugin [3.54.1.01]
2023-05-24 16:00:12,900+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.plugins.nexus-task-log-cleanup [3.54.1.01]
2023-05-24 16:00:12,929+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.plugins.nexus-task-log-cleanup [3.54.1.01]
2023-05-24 16:00:13,035+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.plugins.nexus-blobstore-s3 [3.54.1.01]
2023-05-24 16:00:13,541+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.plugins.nexus-blobstore-s3 [3.54.1.01]
2023-05-24 16:00:13,556+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.plugins.nexus-onboarding-plugin [3.54.1.01]
2023-05-24 16:00:13,584+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.plugins.nexus-onboarding-plugin [3.54.1.01]
2023-05-24 16:00:13,592+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.plugins.nexus-default-role-plugin [3.54.1.01]
2023-05-24 16:00:13,615+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.plugins.nexus-default-role-plugin [3.54.1.01]
2023-05-24 16:00:13,653+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.plugins.nexus-repository-apt [3.54.1.01]
2023-05-24 16:00:13,770+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.plugins.nexus-repository-apt [3.54.1.01]
2023-05-24 16:00:13,880+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.plugins.nexus-repository-raw [3.54.1.01]
2023-05-24 16:00:13,949+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.plugins.nexus-repository-raw [3.54.1.01]
2023-05-24 16:00:13,968+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.cleanup [3.54.1.01]
2023-05-24 16:00:14,004+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.cleanup [3.54.1.01]
2023-05-24 16:00:14,183+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.core [3.54.1.01]
2023-05-24 16:00:14,460+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.core [3.54.1.01]
2023-05-24 16:00:14,467+0000 ERROR [Thread-73] *SYSTEM org.sonatype.nexus.internal.node.orient.OrientLocalNodeAccess - Failed to determine hostname, using nodeId instead.
2023-05-24 16:00:14,537+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-ldap-plugin [3.54.1.01]
2023-05-24 16:00:14,600+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-ldap-plugin [3.54.1.01]
2023-05-24 16:00:14,675+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-proui-plugin [3.54.1.01]
2023-05-24 16:00:14,696+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-proui-plugin [3.54.1.01]
2023-05-24 16:00:14,704+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-proximanova-plugin [3.54.1.01]
2023-05-24 16:00:14,716+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-proximanova-plugin [3.54.1.01]
2023-05-24 16:00:14,851+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING wrap_file_system_com_sonatype_insight_scan_insight-scanner-core_2.33.6-01_insight-scanner-core-2.33.6-01.jar [0.0.0]
2023-05-24 16:00:14,873+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED wrap_file_system_com_sonatype_insight_scan_insight-scanner-core_2.33.6-01_insight-scanner-core-2.33.6-01.jar [0.0.0]
2023-05-24 16:00:14,875+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING wrap_file_system_com_sonatype_insight_scan_insight-scanner-model-io_2.33.6-01_insight-scanner-model-io-2.33.6-01.jar [0.0.0]
2023-05-24 16:00:14,895+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED wrap_file_system_com_sonatype_insight_scan_insight-scanner-model-io_2.33.6-01_insight-scanner-model-io-2.33.6-01.jar [0.0.0]
2023-05-24 16:00:14,898+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-healthcheck-base [3.54.1.01]
2023-05-24 16:00:15,465+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-healthcheck-base [3.54.1.01]
2023-05-24 16:00:15,467+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING wrap_file_system_com_sonatype_licensing_license-bundle_1.6.0_license-bundle-1.6.0.jar [0.0.0]
2023-05-24 16:00:15,537+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED wrap_file_system_com_sonatype_licensing_license-bundle_1.6.0_license-bundle-1.6.0.jar [0.0.0]
2023-05-24 16:00:15,538+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.licensing-extension [3.54.1.01]
2023-05-24 16:00:15,579+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.licensing-extension [3.54.1.01]
2023-05-24 16:00:15,580+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-analytics-plugin [3.54.1.01]
2023-05-24 16:00:15,644+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-analytics-plugin [3.54.1.01]
2023-05-24 16:00:15,646+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-licensing-plugin [3.54.1.01]
2023-05-24 16:00:15,675+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-licensing-plugin [3.54.1.01]
2023-05-24 16:00:15,775+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-npm [3.54.1.01]
2023-05-24 16:00:15,954+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-npm [3.54.1.01]
2023-05-24 16:00:15,955+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-nuget [3.54.1.01]
2023-05-24 16:00:16,180+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-nuget [3.54.1.01]
2023-05-24 16:00:16,183+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-rubygems [3.54.1.01]
2023-05-24 16:00:16,280+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-rubygems [3.54.1.01]
2023-05-24 16:00:16,282+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING org.sonatype.nexus.rest-client [3.54.1.01]
2023-05-24 16:00:16,301+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED org.sonatype.nexus.rest-client [3.54.1.01]
2023-05-24 16:00:16,304+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-migration-plugin [3.54.1.01]
2023-05-24 16:00:16,455+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-migration-plugin [3.54.1.01]
2023-05-24 16:00:16,504+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-vulnerability-plugin [3.54.1.01]
2023-05-24 16:00:16,559+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-vulnerability-plugin [3.54.1.01]
2023-05-24 16:00:16,562+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-outreach-plugin [3.54.1.01]
2023-05-24 16:00:16,600+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-outreach-plugin [3.54.1.01]
2023-05-24 16:00:16,609+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-rutauth-plugin [3.54.1.01]
2023-05-24 16:00:16,630+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-rutauth-plugin [3.54.1.01]
2023-05-24 16:00:16,675+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-clm-oss-plugin [3.54.1.01]
2023-05-24 16:00:16,691+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-clm-oss-plugin [3.54.1.01]
2023-05-24 16:00:16,733+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-docker [3.54.1.01]
2023-05-24 16:00:16,955+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-docker [3.54.1.01]
2023-05-24 16:00:17,002+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-yum [3.54.1.01]
2023-05-24 16:00:17,130+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-yum [3.54.1.01]
2023-05-24 16:00:17,194+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING nexus-blobstore-azure-cloud [3.54.1.01]
2023-05-24 16:00:17,246+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED nexus-blobstore-azure-cloud [3.54.1.01]
2023-05-24 16:00:17,312+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-ahc-plugin [3.54.1.01]
2023-05-24 16:00:17,346+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-ahc-plugin [3.54.1.01]
2023-05-24 16:00:17,406+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-helm [3.54.1.01]
2023-05-24 16:00:17,470+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-helm [3.54.1.01]
2023-05-24 16:00:17,488+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-gitlfs [3.54.1.01]
2023-05-24 16:00:17,532+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-gitlfs [3.54.1.01]
2023-05-24 16:00:17,571+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-pypi [3.54.1.01]
2023-05-24 16:00:17,681+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-pypi [3.54.1.01]
2023-05-24 16:00:17,699+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-conda [3.54.1.01]
2023-05-24 16:00:17,735+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-conda [3.54.1.01]
2023-05-24 16:00:17,752+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-conan [3.54.1.01]
2023-05-24 16:00:17,830+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-conan [3.54.1.01]
2023-05-24 16:00:17,850+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-r [3.54.1.01]
2023-05-24 16:00:17,912+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-r [3.54.1.01]
2023-05-24 16:00:17,929+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-cocoapods [3.54.1.01]
2023-05-24 16:00:17,968+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-cocoapods [3.54.1.01]
2023-05-24 16:00:17,989+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-golang [3.54.1.01]
2023-05-24 16:00:18,041+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-golang [3.54.1.01]
2023-05-24 16:00:18,065+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-p2 [3.54.1.01]
2023-05-24 16:00:18,124+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-p2 [3.54.1.01]
2023-05-24 16:00:18,141+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-repository-bower [3.54.1.01]
2023-05-24 16:00:18,195+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-repository-bower [3.54.1.01]
2023-05-24 16:00:18,226+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATING com.sonatype.nexus.plugins.nexus-ossindex-plugin [3.54.1.01]
2023-05-24 16:00:18,319+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusBundleTracker - ACTIVATED com.sonatype.nexus.plugins.nexus-ossindex-plugin [3.54.1.01]
2023-05-24 16:00:18,364+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.extender.NexusLifecycleManager - Start STORAGE
2023-05-24 16:00:18,389+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.internal.node.orient.OrientLocalNodeAccess - ID: 90127B79-7FCECC8A-61EF662A-11B2824A-8BF863D4
2023-05-24 16:00:18,752+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.internal.orient.DatabaseServerImpl - OrientDB version: 2.2.37 (build a7541e7ceeabf592dd9a7b2928b6c023cbc73193, branch 2.2.x)
2023-05-24 16:00:18,771+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.internal.orient.DatabaseServerImpl$1 - OrientDB Server v2.2.37 (build a7541e7ceeabf592dd9a7b2928b6c023cbc73193, branch 2.2.x) is starting up...
2023-05-24 16:00:18,776+0000 INFO  [FelixStartLevel] *SYSTEM org.sonatype.nexus.internal.orient.DatabaseServerImpl$1 - Databases directory: /nexus-data/db
2023-05-24 16:00:19,074+0000 INFO  [FelixStartLevel] *SYSTEM com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer - Configuration of usage of soft references inside of containers of results of SQL execution
2023-05-24 16:00:19,075+0000 INFO  [FelixStartLevel] *SYSTEM com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer - Initial and maximum values of heap memory usage are equal, containers of results of SQL executors will use soft references by default
2023-05-24 16:00:19,076+0000 INFO  [FelixStartLevel] *SYSTEM com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer - Auto configuration of disk cache size.
2023-05-24 16:00:19,098+0000 WARN  [FelixStartLevel] *SYSTEM com.sun.jna.Native - JNA Warning: IOException removing temporary files
java.io.IOException: JNA temporary directory '../sonatype-work/nexus3/tmp' is not writable
	at com.sun.jna.Native.getTempDir(Native.java:1360)
	at com.sun.jna.Native.removeTemporaryFiles(Native.java:1367)
	at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:946)
	at com.sun.jna.Native.<clinit>(Native.java:221)
	at com.orientechnologies.common.jna.ONative.instance(ONative.java:31)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.configureDefaultDiskCacheSize(OMemoryAndLocalPaginatedEnginesInitializer.java:167)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.configureDefaults(OMemoryAndLocalPaginatedEnginesInitializer.java:77)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.initialize(OMemoryAndLocalPaginatedEnginesInitializer.java:62)
	at com.orientechnologies.orient.core.engine.local.OEngineLocalPaginated.startup(OEngineLocalPaginated.java:56)
	at com.orientechnologies.orient.core.Orient.startEngine(Orient.java:930)
	at com.orientechnologies.orient.core.Orient.loadStorage(Orient.java:523)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.<init>(ODatabaseDocumentTx.java:173)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.<init>(ODatabaseDocumentTx.java:154)
	at com.orientechnologies.orient.server.OSystemDatabase.init(OSystemDatabase.java:151)
	at com.orientechnologies.orient.server.OSystemDatabase.<init>(OSystemDatabase.java:44)
	at com.orientechnologies.orient.server.OServer.initSystemDatabase(OServer.java:1309)
	at com.orientechnologies.orient.server.OServer.activate(OServer.java:367)
	at org.sonatype.nexus.internal.orient.DatabaseServerImpl.doStart(DatabaseServerImpl.java:196)
	at org.sonatype.nexus.common.stateguard.StateGuardLifecycleSupport.start(StateGuardLifecycleSupport.java:69)
	at org.sonatype.nexus.internal.orient.DatabaseServerImpl$$EnhancerByGuice$$250961246.GUICE$TRAMPOLINE(<generated>)
	at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:74)
	at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
	at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:193)
	at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:57)
	at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75)
	at com.google.inject.internal.InterceptorStackCallback.invoke(InterceptorStackCallback.java:55)
	at org.sonatype.nexus.internal.orient.DatabaseServerImpl$$EnhancerByGuice$$250961246.start(<generated>)
	at org.sonatype.nexus.internal.orient.OrientBootstrap.doStart(OrientBootstrap.java:71)
	at org.sonatype.nexus.common.stateguard.StateGuardLifecycleSupport.start(StateGuardLifecycleSupport.java:69)
	at org.sonatype.nexus.internal.orient.OrientBootstrap$$EnhancerByGuice$$254872721.GUICE$TRAMPOLINE(<generated>)
	at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:74)
	at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
	at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:193)
	at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:57)
	at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75)
	at com.google.inject.internal.InterceptorStackCallback.invoke(InterceptorStackCallback.java:55)
	at org.sonatype.nexus.internal.orient.OrientBootstrap$$EnhancerByGuice$$254872721.start(<generated>)
	at org.sonatype.nexus.extender.NexusLifecycleManager.startComponent(NexusLifecycleManager.java:199)
	at org.sonatype.nexus.extender.NexusLifecycleManager.to(NexusLifecycleManager.java:111)
	at org.sonatype.nexus.extender.NexusContextListener.moveToPhase(NexusContextListener.java:319)
	at org.sonatype.nexus.extender.NexusContextListener.frameworkEvent(NexusContextListener.java:216)
	at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1597)
	at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
	at java.lang.Thread.run(Thread.java:750)
2023-05-24 16:00:19,100+0000 ERROR [FelixStartLevel] *SYSTEM org.sonatype.nexus.internal.orient.DatabaseServerImpl - Failed transition: NEW -> STARTED
java.lang.reflect.InvocationTargetException: null
	at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:45)
	at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:193)
	at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:57)
	at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75)
	at com.google.inject.internal.InterceptorStackCallback.invoke(InterceptorStackCallback.java:55)
	at org.sonatype.nexus.internal.orient.DatabaseServerImpl$$EnhancerByGuice$$250961246.start(<generated>)
	at org.sonatype.nexus.internal.orient.OrientBootstrap.doStart(OrientBootstrap.java:71)
	at org.sonatype.nexus.common.stateguard.StateGuardLifecycleSupport.start(StateGuardLifecycleSupport.java:69)
	at org.sonatype.nexus.internal.orient.OrientBootstrap$$EnhancerByGuice$$254872721.GUICE$TRAMPOLINE(<generated>)
	at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:74)
	at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
	at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:193)
	at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:57)
	at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75)
	at com.google.inject.internal.InterceptorStackCallback.invoke(InterceptorStackCallback.java:55)
	at org.sonatype.nexus.internal.orient.OrientBootstrap$$EnhancerByGuice$$254872721.start(<generated>)
	at org.sonatype.nexus.extender.NexusLifecycleManager.startComponent(NexusLifecycleManager.java:199)
	at org.sonatype.nexus.extender.NexusLifecycleManager.to(NexusLifecycleManager.java:111)
	at org.sonatype.nexus.extender.NexusContextListener.moveToPhase(NexusContextListener.java:319)
	at org.sonatype.nexus.extender.NexusContextListener.frameworkEvent(NexusContextListener.java:216)
	at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1597)
	at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
	at java.lang.Thread.run(Thread.java:750)
Caused by: java.lang.UnsatisfiedLinkError: Failed to create temporary file for /com/sun/jna/linux-x86-64/libjnidispatch.so library: JNA temporary directory '../sonatype-work/nexus3/tmp' is not writable
	at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:1059)
	at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:1015)
	at com.sun.jna.Native.<clinit>(Native.java:221)
	at com.orientechnologies.common.jna.ONative.instance(ONative.java:31)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.configureDefaultDiskCacheSize(OMemoryAndLocalPaginatedEnginesInitializer.java:167)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.configureDefaults(OMemoryAndLocalPaginatedEnginesInitializer.java:77)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.initialize(OMemoryAndLocalPaginatedEnginesInitializer.java:62)
	at com.orientechnologies.orient.core.engine.local.OEngineLocalPaginated.startup(OEngineLocalPaginated.java:56)
	at com.orientechnologies.orient.core.Orient.startEngine(Orient.java:930)
	at com.orientechnologies.orient.core.Orient.loadStorage(Orient.java:523)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.<init>(ODatabaseDocumentTx.java:173)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.<init>(ODatabaseDocumentTx.java:154)
	at com.orientechnologies.orient.server.OSystemDatabase.init(OSystemDatabase.java:151)
	at com.orientechnologies.orient.server.OSystemDatabase.<init>(OSystemDatabase.java:44)
	at com.orientechnologies.orient.server.OServer.initSystemDatabase(OServer.java:1309)
	at com.orientechnologies.orient.server.OServer.activate(OServer.java:367)
	at org.sonatype.nexus.internal.orient.DatabaseServerImpl.doStart(DatabaseServerImpl.java:196)
	at org.sonatype.nexus.common.stateguard.StateGuardLifecycleSupport.start(StateGuardLifecycleSupport.java:69)
	at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
	at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:193)
	at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:57)
	at org.sonatype.nexus.internal.orient.OrientBootstrap.doStart(OrientBootstrap.java:71)
	at org.sonatype.nexus.common.stateguard.StateGuardLifecycleSupport.start(StateGuardLifecycleSupport.java:69)
	at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
	at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:193)
	at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:57)
	... 7 common frames omitted
2023-05-24 16:00:19,107+0000 ERROR [FelixStartLevel] *SYSTEM org.sonatype.nexus.internal.orient.OrientBootstrap - Failed transition: NEW -> STARTED
java.lang.reflect.InvocationTargetException: null
	at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:45)
	at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:193)
	at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:57)
	at com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75)
	at com.google.inject.internal.InterceptorStackCallback.invoke(InterceptorStackCallback.java:55)
	at org.sonatype.nexus.internal.orient.OrientBootstrap$$EnhancerByGuice$$254872721.start(<generated>)
	at org.sonatype.nexus.extender.NexusLifecycleManager.startComponent(NexusLifecycleManager.java:199)
	at org.sonatype.nexus.extender.NexusLifecycleManager.to(NexusLifecycleManager.java:111)
	at org.sonatype.nexus.extender.NexusContextListener.moveToPhase(NexusContextListener.java:319)
	at org.sonatype.nexus.extender.NexusContextListener.frameworkEvent(NexusContextListener.java:216)
	at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1597)
	at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
	at java.lang.Thread.run(Thread.java:750)
Caused by: java.lang.UnsatisfiedLinkError: Failed to create temporary file for /com/sun/jna/linux-x86-64/libjnidispatch.so library: JNA temporary directory '../sonatype-work/nexus3/tmp' is not writable
	at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:1059)
	at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:1015)
	at com.sun.jna.Native.<clinit>(Native.java:221)
	at com.orientechnologies.common.jna.ONative.instance(ONative.java:31)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.configureDefaultDiskCacheSize(OMemoryAndLocalPaginatedEnginesInitializer.java:167)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.configureDefaults(OMemoryAndLocalPaginatedEnginesInitializer.java:77)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.initialize(OMemoryAndLocalPaginatedEnginesInitializer.java:62)
	at com.orientechnologies.orient.core.engine.local.OEngineLocalPaginated.startup(OEngineLocalPaginated.java:56)
	at com.orientechnologies.orient.core.Orient.startEngine(Orient.java:930)
	at com.orientechnologies.orient.core.Orient.loadStorage(Orient.java:523)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.<init>(ODatabaseDocumentTx.java:173)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.<init>(ODatabaseDocumentTx.java:154)
	at com.orientechnologies.orient.server.OSystemDatabase.init(OSystemDatabase.java:151)
	at com.orientechnologies.orient.server.OSystemDatabase.<init>(OSystemDatabase.java:44)
	at com.orientechnologies.orient.server.OServer.initSystemDatabase(OServer.java:1309)
	at com.orientechnologies.orient.server.OServer.activate(OServer.java:367)
	at org.sonatype.nexus.internal.orient.DatabaseServerImpl.doStart(DatabaseServerImpl.java:196)
	at org.sonatype.nexus.common.stateguard.StateGuardLifecycleSupport.start(StateGuardLifecycleSupport.java:69)
	at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
	at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:193)
	at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:57)
	at org.sonatype.nexus.internal.orient.OrientBootstrap.doStart(OrientBootstrap.java:71)
	at org.sonatype.nexus.common.stateguard.StateGuardLifecycleSupport.start(StateGuardLifecycleSupport.java:69)
	at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
	at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:193)
	at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:57)
	... 7 common frames omitted
2023-05-24 16:00:19,113+0000 ERROR [FelixStartLevel] *SYSTEM Felix - Framework listener delivery error.
java.lang.UnsatisfiedLinkError: Failed to create temporary file for /com/sun/jna/linux-x86-64/libjnidispatch.so library: JNA temporary directory '../sonatype-work/nexus3/tmp' is not writable
	at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:1059)
	at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:1015)
	at com.sun.jna.Native.<clinit>(Native.java:221)
	at com.orientechnologies.common.jna.ONative.instance(ONative.java:31)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.configureDefaultDiskCacheSize(OMemoryAndLocalPaginatedEnginesInitializer.java:167)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.configureDefaults(OMemoryAndLocalPaginatedEnginesInitializer.java:77)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.initialize(OMemoryAndLocalPaginatedEnginesInitializer.java:62)
	at com.orientechnologies.orient.core.engine.local.OEngineLocalPaginated.startup(OEngineLocalPaginated.java:56)
	at com.orientechnologies.orient.core.Orient.startEngine(Orient.java:930)
	at com.orientechnologies.orient.core.Orient.loadStorage(Orient.java:523)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.<init>(ODatabaseDocumentTx.java:173)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.<init>(ODatabaseDocumentTx.java:154)
	at com.orientechnologies.orient.server.OSystemDatabase.init(OSystemDatabase.java:151)
	at com.orientechnologies.orient.server.OSystemDatabase.<init>(OSystemDatabase.java:44)
	at com.orientechnologies.orient.server.OServer.initSystemDatabase(OServer.java:1309)
	at com.orientechnologies.orient.server.OServer.activate(OServer.java:367)
	at org.sonatype.nexus.internal.orient.DatabaseServerImpl.doStart(DatabaseServerImpl.java:196)
	at org.sonatype.nexus.common.stateguard.StateGuardLifecycleSupport.start(StateGuardLifecycleSupport.java:69)
	at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
	at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:193)
	at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:57)
	at org.sonatype.nexus.internal.orient.OrientBootstrap.doStart(OrientBootstrap.java:71)
	at org.sonatype.nexus.common.stateguard.StateGuardLifecycleSupport.start(StateGuardLifecycleSupport.java:69)
	at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
	at org.sonatype.nexus.common.stateguard.StateGuard$TransitionImpl.run(StateGuard.java:193)
	at org.sonatype.nexus.common.stateguard.TransitionsInterceptor.invoke(TransitionsInterceptor.java:57)
	at org.sonatype.nexus.extender.NexusLifecycleManager.startComponent(NexusLifecycleManager.java:199)
	at org.sonatype.nexus.extender.NexusLifecycleManager.to(NexusLifecycleManager.java:111)
	at org.sonatype.nexus.extender.NexusContextListener.moveToPhase(NexusContextListener.java:319)
	at org.sonatype.nexus.extender.NexusContextListener.frameworkEvent(NexusContextListener.java:216)
	at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1597)
	at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
	at java.lang.Thread.run(Thread.java:750)

Do you have a workaround you are using at present?
No
What feature or behavior is this required for?
Basic usage
How could we solve this issue? (Not knowing is okay!)
help to troubleshoot fix
Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?
Version: 3.54.1
Running in Kubernetes

Anything else?
Error ocurred after adding the following env var but no longer starts even after removing it.

env:
- name: INSTALL4J_ADD_VM_PARAMS
  value: "-Xms2703m -Xmx2703m -XX:MaxDirectMemorySize=2703m -Djava.util.prefs.userRoot=/nexus-data/javaprefs -Dcom.sun.jndi.ldap.connect.pool.timeout=300000"

NEXUS-27088 Refactor logging for AbstractMetadataRebuilder

Migrated from https://issues.sonatype.org/browse/NEXUS-27088 originally reported by Hardeep Nagra.

Further to adding support for sha256 and sha512 checksums for Maven artifacts in NXRM 3.29.0, when a maven-metadata rebuild takes place (where checksums are rebuilt), the nexus.log can be spammed with the following WARN logging:

2021-03-22 05:50:59,537+0100 WARN [quartz-11-thread-7] *SYSTEM org.sonatype.nexus.repository.maven.internal.orient.OrientMetadataRebuilder$Worker - Asset with path MavenPath{path=‘[...].jar’, fileName=‘[...].jar’, hashType=null} lacks checksum SHA512

2021-03-22 05:50:59,539+0100 WARN [quartz-11-thread-7] *SYSTEM org.sonatype.nexus.repository.maven.internal.orient.OrientMetadataRebuilder$Worker - Asset with path MavenPath{path=‘[...].pom’, fileName=‘[...].pom’, hashType=null} lacks checksum SHA256

This logging originates from org.sonatype.nexus.repository.maven.internal.hosted.metadata.AbstractMetadataRebuilder. It can occur for artifacts that were uploaded pre NXRM 3.29 and did not have a sha256/sha512 checksum generated for them.

Expected:

As this logging can potentially occur for hundreds if not thousands of artifacts, it should be moved to a more granular log level of TRACE.

[NEXUS-28979] Maven Group has inappropriate fields in UI (create and edit)

Nexus version OSS 3.34.0

Maven Group displays all the "Maven 2" variables (Version policy, Layout policy, Content Disposition) on creation and edit typical of proxy and hosted repositories.

This is errant, at least Version policy and Layout policy (Content Disposition I believe also but not 100% sure) are not used by group, they use the individual member settings.

[NEXUS-30491] Outreach: Management capability confusing and broken

Nexus version OSS 3.33.0

I stumbled upon the "Outreach: Management" capability.
But there are multiple problems.

I don't find anything about it in the Nexus 3 documentation and it is not really self-explanatory
If I disable it and press "Save", I get a validation error "must not be null", either the error should be changed to say "must be enabled" or better the capability should not be disableable or eben better it should be disableable
The default outreach content url just responds with a 404 error

NEXUS-22698 Allow REST API search and download through proxy repositories

Currently a REST API search or download request against a proxy repository will only work if the components are cached locally in a proxy repository.

For instance a request to download the latest snapshot jar for a GAV:

curl "http://localhost:8083/service/rest/v1/search/assets/download?sort=version&repository=maven-snapshots-proxy&maven.groupId=org.foo.bar&maven.artifactId=project&maven.baseVersion=1.2.3-SNAPSHOT&maven.extension=jar"

This will fail unless the jar is already downloaded into the proxy.

Retrieving the latest version of a component via REST API through a proxy is a use case we should be supporting. Possible implementations for this include implementing a remote search capability, or, specifically for Maven, using the maven-metadata.xml files to find available versions.

Réf.: https://issues.sonatype.org/browse/NEXUS-22698
Version: 3.45.0

NEXUS-17671 Provide a REST API for cleanup policies

What problem are you trying to solve?
I'd like to be able to create and manage cleanup policies via the REST API
Do you have a workaround you are using at present?
I use the script REST API to script cleanup policies
What feature or behavior is this required for?
IaC provisioning of Nexus3
How could we solve this issue? (Not knowing is okay!)
Implement a REST interface for cleanup policies
Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?
Latest version running on Kubernetes using OrionDB.
Anything else?
I requested this almost 5 years ago.

p2 Hosted repository support for Nexus

Hosting and deploying the p2 repositories directly to the Nexus would be a huge favor as this would provide a better overview and handling for users which have no access to the filesystem. Our Eclipse RCP projects depend on a p2 hosted repo for publishing developed plugins. It is difficult to argue internally for Nexus as our single, trustable source of software components if a part of our development projects are not supported.

Nexus still makes bundler fall back to the full index resolution since compact index methods are not supported

Currently when running a fresh bundle install/bundle update against a nexus repository, that repository will return a 404 on /gem/info/{gem} causing bundler to fall back to dependency api based resolution, which is quite slow (as established in https://issues.sonatype.org/browse/NEXUS-31225, and https://issues.sonatype.org/browse/NEXUS-17626.) This affects both enterprise and oss users.

Unable to download maven snapshot if dependency version declared as range[0.20.0-SNAPSHOT, 0.21.0-SNAPSHOT) in pom.xml

Hi,

This is Vignesh

we have artifacts in JFrog planning to migrate to nexus as first phase have installed nexus open source version nexus-3.54.1-01 configured proxy repository for maven which is pointing to JFrog facing below issues.

when we try to pull snapshot from nexus, which is having dependency and the versions declared as range [0.20.0-SNAPSHOT, 0.21.0-SNAPSHOT) in pom.xml

Example pom.xml:

<parent>
    <groupId>com.inin</groupId>
    <artifactId>data</artifactId>
    <version>0.21.0-SNAPSHOT</version>
</parent>

<artifactId>some-common</artifactId>
<version>0.62.0-SNAPSHOT</version>

<properties>
    <some-data-common.version>[0.31.0-SNAPSHOT,0.32.0-SNAPSHOT)</some-data-common.version>
    <some-common.version>3.0.0-SNAPSHOT</some-common.version>
</properties>

<dependencies>
    <dependency>
        <groupId>com.inin</groupId>
        <artifactId>some-data-common</artifactId>
        <version>${some-data-common.version}</version>
    </dependency>
</dependencies>

Error:

_Failed to collect dependencies at com.inin:some-common:jar:0.62.0-SNAPSHOT -> com.inin:some-data-common:jar:[0.31.0-SNAPSHOT,0.32.0-SNAPSHOT): No versions available for com.inin:some-data-common:jar:[0.31.0-SNAPSHOT,0.32.0-SNAPSHOT) within specified range -> [Help 1]_

Enabled debug mode for http.client and outbound connection in nexus to trace proxy request and then found the error occuring when nexus try to do PUT request to upload metadata file to nexus repository and getting the path mismatch please find the debug log below

2023-05-26 08:07:59,333+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.httpclient.outbound - https://jfrog/maven-mirror/com/inin/some-data-common/maven-metadata.xml < HTTP/1.1 200 @ 1.391 s 2023-05-26 08:07:59,333+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.maven.internal.orient.MavenProxyFacet - Status: HTTP/1.1 200 2023-05-26 08:07:59,334+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.maven.internal.orient.MavenProxyFacet - Entity: ResponseEntityProxy{[Content-Type: application/xml,Content-Length: 1726,Chunked: false]} 2023-05-26 08:07:59,334+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.maven.internal.orient.MavenFacetImpl - **PUT maven-cache : com/inin/some-data-common/maven-metadata.xml** 2023-05-26 08:07:59,335+0000 DEBUG [qtp1305362650-2801] admin org.apache.http.impl.conn.DefaultManagedHttpClientConnection - http-outgoing-59: set socket timeout to 0 2023-05-26 08:07:59,335+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.maven.internal.orient.MavenFacetImpl - **Validating maven-metadata.xml before storing** 2023-05-26 08:07:59,336+0000 DEBUG [qtp1305362650-2801] admin **org.sonatype.nexus.repository.maven.internal.validation.MavenMetadataContentValidator - maven-metadata.xml contains a SNAPSHOT version (0.31.0-SNAPSHOT) therefore the version is expected to be part of the path** 2023-05-26 08:07:59,336+0000 WARN [qtp1305362650-2801] admin **org.sonatype.nexus.repository.maven.internal.validation.MavenMetadataContentValidator - maven-metadata.xml path com/inin/some-data-common/maven-metadata.xml does not match the expected path com/inin/some-data-common/0.31.0-SNAPSHOT/maven-metadata.xml** 2023-05-26 08:07:59,336+0000 WARN [qtp1305362650-2801] admin org.sonatype.nexus.repository.maven.internal.orient.MavenFacetImpl - ** /** 2023-05-26 08:07:59,337+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.maven.internal.orient.MavenFacetImpl - GET maven-cache : com/inin/some-data-common/maven-metadata.xml 2023-05-26 08:07:59,337+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.storage.StorageTxImpl - Transitioning: OPEN -> ACTIVE 2023-05-26 08:07:59,337+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.storage.StorageTxImpl - Transitioned: ACTIVE 2023-05-26 08:07:59,338+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.storage.StorageTxImpl - Transitioning: ACTIVE -> OPEN 2023-05-26 08:07:59,338+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.storage.StorageTxImpl - Transitioned: OPEN 2023-05-26 08:07:59,338+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.storage.StorageTxImpl - Transitioning: OPEN -> CLOSED 2023-05-26 08:07:59,339+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.storage.StorageTxImpl - Transitioned: CLOSED 2023-05-26 08:07:59,339+0000 WARN [qtp1305362650-2801] admin org.sonatype.nexus.repository.view.handlers.ExceptionHandler - Invalid content: GET /com/inin/some-data-common/maven-metadata.xml: org.sonatype.nexus.repository.InvalidContentException: Invalid maven-metadata.xml GAV com.inin, some-data-common, 0.31.0-SNAPSHOT does not match request path com/inin/some-data-common/maven-metadata.xml 2023-05-26 08:07:59,339+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.view.Router - Response: Response{status=Status{successful=false, code=404, message='Invalid maven-metadata.xml GAV com.inin, some-data-common, 0.31.0-SNAPSHOT does not match request path com/inin/some-data-common/maven-metadata.xml'}, payload=null} 2023-05-26 08:07:59,340+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.httpbridge.internal.ViewServlet - Request: Request{action='GET', path='/com/inin/some-data-common/maven-metadata.xml', parameters=null, payload=HttpRequestPayloadAdapter{contentType='null', size=-1}, multipart=false} 2023-05-26 08:07:59,340+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.httpbridge.internal.DefaultHttpResponseSender - Sending response: Response{status=Status{successful=false, code=404, message='Invalid maven-metadata.xml GAV com.inin, some-data-common, 0.31.0-SNAPSHOT does not match request path com/inin/some-data-common/maven-metadata.xml'}, payload=null} 2023-05-26 08:07:59,340+0000 DEBUG [qtp1305362650-2801] admin org.sonatype.nexus.repository.httpbridge.internal.ViewServlet - Service completed

This is preventing us from migration.

Thanks

Nexus-Staging-Maven-Plugin illegal reflective access through XStream usage

Core Issue

When using the nexus-staging-maven-plugin, an illegal reflective access warning is generated through use of XStream.
Running with MAVEN_OPTS=--illegal-access=debug, the reflective access occurs during XStream initialization. This can be seen here: https://pastebin.com/cHv3G2hM . XStream is aware of the issue and to mitigate it, they have deferred reflective access until absolutely necessary: x-stream/xstream#218 .

Potential Quick Fix
Whether the solution XStream has implemented is sufficient to fix the problem depends on whether the nexus-staging-maven-plugin requires any of the reflective field accesses XStream performs.
As a first start to solve the issue, XStream's version can be updated per this automated PR: sonatype/nexus-maven-plugins#91 It is possible that updating the version of XStream will solve the issue immediately.

Effects on Libraries

When JDK 16 is released this month, illegal reflective access will be denied by default. This presents ramifications to libraries using the nexus-staging-maven-plugin which have a higher JDK build-time requirement even if they are compatible with older JDK versions at runtime. For example, some libraries may want to support record features, and thus require JDK 16.
Changing MAVEN_OPTS=--illegal-access=permit or using .mvn/jvm.config could be a temporary workaround, but at some point this issue will have to be solved. Again, it may be as trivial as incrementing the XStream version.

NEXUS-28598 Session timeout setting does not work

The capability UI: Settings has a setting for session timeout.

Setting a higher value (e.g. multiple days) does not prevent session expiry.

I have a value of 24400 [min] (~ 17 days) but have to log in each day and even after several minutes / an hour.

The issue was originally tracked as NEXUS-28598.

I've reconfigured the Session timeout in the UI: Settings to one week (10080 minutes) - but I'm still getting logged out.

Test Case:

Log into Nexus

Browse a repository and click on HTML view, browse around a bit

Note the value of NXSESSIONID cookie

Wait a while (not sure how long exactly but over night was sufficient for me) - browser tab still open

Hit F5 - you're greeted with a 404 - same error if you click on one of the links in the HTML view

Go back to the main UI and see that I'm no longer marked as signed in

Verify the NXSESSIONID cookie is still the same as the day before, still present and has the same value. Chrome reports the cookie as "Session" for the Expires / Max-Age value.

[NEXUS-30683] Strict content validation doesn't like PKCS #12 files

Nexus version OSS 3.33.0

I tried to upload our code signing certificate to Nexus, but Nexus doesn't like it.
The file has file extension .p12 and the Java keytool says Keystore-Typ: PKCS12.
But on trying to publish to Nexus it complains with

Could not PUT '.../keystore-version.p12'. Received status code 400 from server: Detected content type [application/x-x509-key], but expected [application/x-pkcs12]: .../keystore-version.p12

Work-around is to disable the strict content type validation for that repository.

Nexus OrientDB to Postgres migration - security realm and password auth problems

Yesterday we finished the Nexus database migration but we ran into 2 bugs which we were able to resolve.

Wrong password after migration
in NEXUS_FOLDER/etc/fabric/nexus-store.properties the password field always has a trailing space " " after the migration. Resulting in Nexus not being able to start because the Postgres password is wrong. I had to manually remove the space after the password field and this solved this issue.

Corrupted realm_configuration table after migration
We upgraded Nexus 3.54.1 with nexus-db-migrator-3.54.1-01.jar and after the migration finished Nexus was not able to start and there was a Java stacktrace relating to the security realms (don't have the logs anymore). I was able to resolve this by manually editing the realm_configuration table as it had gotten corrupted after the migration (or already was corrupted before the migration but was still compatible with OrientDB).

After the migration the row value was:
1,"[""[NexusAuthenticatingRealm"", ""NexusAuthorizingRealm]""]"
Which is not a valid JSON Array (it also had some Realm names missing)
I changed it manually back to
["NexusAuthenticatingRealm", "NexusAuthorizingRealm"]
and then Nexus did start with Postgres but I still had to manually enable some Security Realms again through the admin portal.

I did not have the realm problem on our testing environment but that was a 3.53 (?) migration with nexus-db-migrator 3.53.1-01.jar. Nexus is currently working so I don't have a problem right now.

Sonatype Nexus Repository Issue Tracker is moving

At the end of May 2023, Sonatype will be closing access to our Jira instance at https://issues.sonatype.org/browse/NEXUS.
That instance of Jira has been licensed for Jira Server, a product that is reaching end-of-life with Atlassian on Feb 15, 2024. We expect to complete our internal Issue Tracking transition by the end of May 2023.

As a result, Sonatype will be moving our Issue Tracker for OSS installs of Sonatype Nexus Repository within Github Issues in https://github.com/sonatype/nexus-public as of today, May 1 2023.

Pro customers can continue to use https://support.sonatype.com/. Our support platform will provide continuity for visibility into support tickets that result in internal issues.

If you are a subscriber on an issue in our old Jira instance, expect to see communication pointing here as issues will be closing in the days up to the end of the service.

[NEXUS-28675] ldap integration cannot connect to ldaps connection with own certificate

Nexus version OSS 3.33.0

Our Active Directory servers need ldaps to be used.
We have that running with a certifiacte signed by an own CA certificate.
After trying to configure LDAP on verify I got unable to find valid certificationpath to requested target of course.

So I went to "SSL Certificates" configuration, added the CA certificate from PEM string which was added to the trust store. But the SSL error still occurs, even after a restart. It seems the trust store is not used for ldaps connections.

I did check the "Use certificates stored in the Nexus truststore to connect to external systems" option.

And when I press "View certificate" to the right of that option I just get an error saying "Certificates do not conform to algorithm constraints"

That last line actually had the important information and it is caused by the base image you use for the Docker image.
It has in /usr/share/crypto-policies/DEFAULT/java.txt as part of jdk.certpath.disabledAlgorithms the option RSA keySize < 2048 instead of the Java default 1024. It seems that file was used and overrides the Java default file, so it rejected the server certificate which only has 1024 bits with only a vaguely helpful message. After starting with -Djava.security.debug=certpath the message became a tad bit more helpful and showed that I'm looking at the wrong file. So after either upgrading the server certificate to 2048 bits or changing the setting to be ok with 1024 bits and still having the CA certificate in the NXRM trust store, it worked as expected.

Overwrite admin password at startup

We built our own helm chart for Nexus and we saw, it's possible to set the initial admin password with an environment variable.
Both NEXUS_SECURITY_INITIAL_PASSWORD and NEXUS_SECURITY_RANDOMPASSWORD variables are set and setting the password at the first startup is working properly. But changing the password seems to be impossible with the environment variable.

Is there a way to automate changing the admin password at startup for existing installations other than modifying in the database?

npm install/update fail because runs audit inside it.

What problem are you trying to solve?

npm install/update fail because runs npm audit inside it and nexus always try to intercept audit to use IQ Server and i am using a free version of nexus that don't have this capability.

Do you have a workaround you are using at present?

I have to use npm install/update with --no-audit, disabling this capability on npm

What feature or behavior is this required for?

To check vulnerabilities. You are forcing me to disable this check

How could we solve this issue? (Not knowing is okay!)

When using nexus OSS you have to redirect audit URL to original URL. npm install/update can't change URL by parameter, just npm audit stand alone.

Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?

CentOS 7, Nexus 3.50

Anything else?

[NEXUS-16089] terraform registry format support

What problem are you trying to solve?

https://issues.sonatype.org/browse/NEXUS-16089

Hi @nblair, can you please add terraform registry into Nexus? Would have been amazing.

Do you have a workaround you are using at present?

What feature or behavior is this required for?

to upload terraform plugins/modules to nexus terraform hosted repository

Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?

latest Nexus 3 OSS

Thank you.

Since v3.53 bundle installation via Kar-file dropping into $install-dir/deploy seems no longer to work

What problem are you trying to solve/occured?

After uprading Nexus to v3.53 in an Docker based deployment (see below, installation via dropping into $install-dir/deploy according to https://help.sonatype.com/repomanager3/integrations/bundle-development/installing-bundles#InstallingBundles-InstallingBundlesInto3.15.0andLater) , the composer community plugin does not longer work nor is loaded. See issue sonatype-nexus-community/nexus-repository-composer#140.

Do you have a workaround you are using at present?

Unfortunately not 😱... and Nexus does not allow downgrades!

How could we solve this issue? (Not knowing is okay!)

Please help... we're running into serious issues here....

Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?

Docker v23 on Debian 11 with sonatype/nexus3:latest image (v3.53)
see https://github.com/sonatype-nexus-community/nexus-repository-composer/blob/master/Dockerfile

NEXUS-36868: Helm Proxy: Nexus converts string to number in index.yaml causing Helm repo add to fail

Helm Proxy: Nexus converts string to number in index.yaml causing Helm repo add to fail

This is a based on NEXUS-36868. I am re-creating here for public visibility and tracking, and comments, and requests for more information.

What problem are you trying to solve?

If I have a Helm proxy set up to point to a remote Helm repository, there are cases where values in the index.yaml file get converted causing helm repo add to output an error as it tries to parse the index.yaml file provided by Nexus.

Error: looks like "http://localhost:8182/repository/helm-test/" is not a valid chart repository or cannot be reached: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal number into Go struct field ChartVersion.entries.appVersion of type string

More details below, but in summary, this is caused by certain chart metadata fields containing quoted strings that could be interpreted as number. In that case Nexus creates an incorrect proxied version of index.yaml. This proxied file cannot be read by the Helm CLI.

This stops the entire proxy repository being able to be used, due to a single new valid chart added on the remote repository. Therefore I think this is a critical issue.

Do you have a workaround you are using at present?

"Fixing" the chart metadata on the remote repository is the only fix. Note that the chart metadata is absolutely valid as per spec. More details below.

This can be done on repositories that we control, but is very cumbersome, and we shouldn't have to, as the charts are valid. Also, charts with metadata that causes an issue with Nexus could be added at anytime.

There is no option if we do not control the remote repository.

In summary, there is no real workaround.

What feature or behavior is this required for?

This is required to proxy a remote Helm repository. This remote repository may be a corporate repository.

How could we solve this issue? (Not knowing is okay!)

Fix the code that parses the index.yaml metadata. :)

Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?

I have successfully and simply reproduced this with Nexus OSS containers connected to remote Helm repository.

This was originally reported to us by customers using Nexus to connect to a corporate Helm repository. They would commonly use Nexus OSS in deployment environments, which would proxy to various remote Helm repositories, include corporate repositories.

Anything else?

This is most likely to happen with appVersion, which is a string, because often developers add number style strings.

I have tested this in 3.53.1, but also is present in several earlier versions that I have tested since it was noticed.

In my case, I noticed this happening when appVersion was set to a quoted string, but where the string could be interpreted as a number. However it was only in the case where the number string contained an underscore.

For example, there was a chart on the remote Helm repository where the appVersion was set to something like '22.09_01'. Note that the remote index file has this value quoted, so it should be interpreted as a string.

When I set up the Helm proxy in Nexus, and try to add try to do a helm repo add, I get as above.

Looking at this further, I see that the index.yaml from Nexus returns the appVersion unquoted, so it is interpreted as a number, and therefore it explains the Helm error.

I did some tests with a index.yaml file on a web server for some quick testing.

Setting a hard-coded index file on my test remote repository...

apiVersion: v1
entries:
  my-chart:
  - apiVersion: v1
    name: my-chart
    description: 'My Chart'
    version: 1.0.0
    created: 2023-01-01T00:00:00.000Z
    appVersion: '22.09_01'
    digest: 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
    urls:
    - my-chart-1.0.0.tgz

When Nexus returns the index file, you notice that appVersion value is not unquoted.

apiVersion: v1
entries:
  my-chart:
  - apiVersion: v1
    name: my-chart
    description: 22.09_01
    version: 1.0.0
    created: 2023-01-01T00:00:00.000Z
    appVersion: 22.09_01
    digest: 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
    urls:
    - my-chart-1.0.0.tgz

This seems to be the case for any number with an underscore in it. A number without an underscore such as 22.09 will remain quoted in the Nexus output.

A little more testing shows that it doesn't matter if the original index value is quoted or not.
However an unquoted number, without underscores, conveniently does get quoted when proxied.

Original Value	Proxied Value
22.09_01	22.09_01
'22.09_01'	22.09_01
"22.09_01"	22.09_01
22.09	"22.09"
22	"22"

The effect of this is that is some user sets the appVersion (or any other string field) to a number with an underscore, then it cannot be used via Nexus.

The appVersion is this case was correct, and was quoted. The Helm proxy had been in use for some time, and suddenly the Nexus proxy repo could no longer be used due to a new chart on the remote repository (which had a correct value).

This stops the entire proxy repository being able to be used, due to a single new valid chart added on the remote repository.

It is quite likely a someone may use an appVersion such as the example I provided. In this case is looks like the remote chart was using an underscore to indicate a patch. Therefore I could see this issue as potentially quite common.

[NEXUS-29135] Uploading more than 3 assets to a Maven component via REST is not possible

Nexus version OSS 3.33.0

If you create a Maven component using REST API, you can at most add 3 assets.
I see no way to add more assets either using the {{components}} endpoint, nor the {{assets}} endpoint.
So if you for example just have the "standard" assets (pom, jar, sources jar, javadoc jar) you cannot create this component via the REST API, let alone a component with additional assets.

[NEXUS-35956] docker group does not return Link header (pagination feature)

Original issue : https://issues.sonatype.org/browse/NEXUS-35956

This issue is related with NEXUS-26037.

Pagination works if i access the proxy repository :
curl -k -v https://<nexus_host>:8087/v2/renovate/renovate/tags/list\?n\=10
The header link is returned as expected :
< Link: <https://<nexus_host>:8087/v2/renovate/renovate/tags/list?n=10&last=0.0.4-slim>; rel="next"

But if this repository is inside a docker group then the Link header is not returned and it breaks the pagination.

Docker proxy for gitlab.com repository

I'm trying to set up a docker proxy for gitlab.com docker registry and nothing works.

Is there somebody who successfully managed this? Could you please share the working configuration?

Also, it will be a good option to have a collection of the most popular registry setups. E.g. google, docker, etc

Thanks in advance!

NEXUS-37518 Failed to run task 'Docker - Delete unused manifests and images' version 3.41.0-01

clone of https://issues.sonatype.org/browse/NEXUS-37518 to not miss this important issue...

Hi,

We are seeing an issue reproducible in several nexus instances we have running on version 3.41.0-01 when running the task Remove unused docker manifests and images (Docker - Delete unused manifests and images ). The task fails with the bellow logs.

2023-02-16 10:58:38,340+0000 INFO  [quartz-12-thread-5]  *SYSTEM org.sonatype.nexus.repository.docker.tasks.DockerGCTask - Task information:
2023-02-16 10:58:38,341+0000 INFO  [quartz-12-thread-5]  *SYSTEM org.sonatype.nexus.repository.docker.tasks.DockerGCTask -  ID: 26011f0c-640a-4268-aa8a-9089d3d65122
2023-02-16 10:58:38,342+0000 INFO  [quartz-12-thread-5]  *SYSTEM org.sonatype.nexus.repository.docker.tasks.DockerGCTask -  Type: repository.docker.gc
2023-02-16 10:58:38,342+0000 INFO  [quartz-12-thread-5]  *SYSTEM org.sonatype.nexus.repository.docker.tasks.DockerGCTask -  Name: Remove unused docker manifests and images
2023-02-16 10:58:38,342+0000 INFO  [quartz-12-thread-5]  *SYSTEM org.sonatype.nexus.repository.docker.tasks.DockerGCTask -  Description: Docker - Delete unused manifests and images
2023-02-16 10:58:38,344+0000 INFO  [quartz-12-thread-5]  *SYSTEM org.sonatype.nexus.repository.docker.internal.orient.DockerGCFacetImpl - Garbage collection starting on repository: RepositoryImpl$$EnhancerByGuice$$677596588{type=proxy, format=docker, name='dockerhub-proxy'}
2023-02-16 10:58:38,346+0000 INFO  [quartz-12-thread-5]  *SYSTEM org.sonatype.nexus.repository.docker.internal.orient.DockerGCFacetImpl - Running GC for v1 assets on dockerhub-proxy
2023-02-16 10:58:38,356+0000 INFO  [quartz-12-thread-5]  *SYSTEM org.sonatype.nexus.repository.docker.internal.orient.DockerGCFacetImpl - Finished GC for v1 assets on dockerhub-proxy. checked 0, deleted 0
2023-02-16 10:58:38,356+0000 INFO  [quartz-12-thread-5]  *SYSTEM org.sonatype.nexus.repository.docker.internal.orient.DockerGCFacetImpl - Running GC for v2 assets on dockerhub-proxy
2023-02-16 10:58:38,357+0000 INFO  [quartz-12-thread-5]  *SYSTEM org.sonatype.nexus.repository.docker.internal.orient.DockerGCFacetImpl - Fetched data for RepositoryImpl$$EnhancerByGuice$$677596588{type=proxy, format=docker, name='dockerhub-proxy'}. checked 0
2023-02-16 10:58:38,372+0000 ERROR [quartz-12-thread-5]  *SYSTEM org.sonatype.nexus.repository.docker.tasks.DockerGCTask - Failed to run task 'Docker - Delete unused manifests and images' on repository 'dockerhub-proxy'
java.lang.NullPointerException: Cannot get property 'digest' on null object
    at org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:60)
    at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:190)
    at org.codehaus.groovy.runtime.DefaultGroovyMethods.getAt(DefaultGroovyMethods.java:342)
    at org.codehaus.groovy.runtime.dgm$242.invoke(Unknown Source)
    at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoMetaMethodSiteNoUnwrapNoCoerce.invoke(PogoMetaMethodSite.java:251)
    at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.call(PogoMetaMethodSite.java:71)
    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
    at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:34)
    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:128)
    at org.sonatype.nexus.repository.docker.internal.V2Manifest.referencedDigests(V2Manifest.groovy:104)
    at org.sonatype.nexus.repository.docker.internal.orient.DockerGCFacetImpl.fetchDataForManifest(DockerGCFacetImpl.java:382)
    at org.sonatype.nexus.repository.docker.internal.orient.DockerGCFacetImpl.fetchDataForRepository(DockerGCFacetImpl.java:355)
    at org.sonatype.nexus.transaction.TransactionalWrapper.proceedWithTransaction(TransactionalWrapper.java:58)
    at org.sonatype.nexus.transaction.TransactionInterceptor.proceedWithTransaction(TransactionInterceptor.java:66)
    at org.sonatype.nexus.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:55)
    at org.sonatype.nexus.repository.docker.internal.orient.DockerGCFacetImpl.getExternalUsedLayersDigests(DockerGCFacetImpl.java:267)
    at org.sonatype.nexus.repository.docker.internal.orient.DockerGCFacetImpl.checkForReferencesInOtherRepositories(DockerGCFacetImpl.java:246)
    at org.sonatype.nexus.repository.docker.internal.orient.DockerGCFacetImpl.handleV2Assets(DockerGCFacetImpl.java:221)
    at org.sonatype.nexus.repository.docker.internal.orient.DockerGCFacetImpl.processRepository(DockerGCFacetImpl.java:144)
    at org.sonatype.nexus.transaction.TransactionalWrapper.proceedWithTransaction(TransactionalWrapper.java:58)
    at org.sonatype.nexus.transaction.TransactionInterceptor.proceedWithTransaction(TransactionInterceptor.java:66)
    at org.sonatype.nexus.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:55)
    at org.sonatype.nexus.repository.docker.internal.orient.DockerGCFacetImpl.deleteUnusedManifestsAndImages(DockerGCFacetImpl.java:126)
    at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
    at org.sonatype.nexus.common.stateguard.StateGuard$GuardImpl.run(StateGuard.java:272)
    at org.sonatype.nexus.common.stateguard.GuardedInterceptor.invoke(GuardedInterceptor.java:54)
    at org.sonatype.nexus.repository.docker.tasks.DockerGCTask.execute(DockerGCTask.java:48)
    at org.sonatype.nexus.repository.RepositoryTaskSupport.execute(RepositoryTaskSupport.java:79)
    at org.sonatype.nexus.scheduling.TaskSupport.call(TaskSupport.java:100)
    at org.sonatype.nexus.quartz.internal.task.QuartzTaskJob.doExecute(QuartzTaskJob.java:143)
    at org.sonatype.nexus.quartz.internal.task.QuartzTaskJob.execute(QuartzTaskJob.java:106)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
    at org.sonatype.nexus.quartz.internal.QuartzThreadPool.lambda$0(QuartzThreadPool.java:145)
    at org.sonatype.nexus.thread.internal.MDCAwareRunnable.run(MDCAwareRunnable.java:40)
    at org.apache.shiro.subject.support.SubjectRunnable.doRun(SubjectRunnable.java:120)
    at org.apache.shiro.subject.support.SubjectRunnable.run(SubjectRunnable.java:108)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:750) 

 The problematic image/manifest has oci mediatype.

The only images available on the repository belonged to scylladb/scylla and the issue was reproduce having the tag latest and 5.0.rc8 

These images are public and can be pulled from docker hub:

docker pull scylladb/scylla:5.0.rc8

docker pull scylladb/scylla:latest

the problematic manifest seems to belong to the tag 5.0.rc8 (which has a oci mediatype)

Logs and print screens attached:

Screenshot 2023-02-16 at 10.53.23 (images available on the repository)

I hope this is enough evidence to be able to be reproducible.

[NEXUS-25287] Rebuild maven metadata task does not remove metadata files from folders with no assets

Back to previous view https://issues.sonatype.org/browse/NEXUS-25287

[NEXUS-25287] Rebuild maven metadata task does not remove metadata
files from folders with no assets
https://issues.sonatype.org/browse/NEXUS-25287 Created: 09/14/20
Updated: 05/10/23

Status: Open
Project: Sonatype Nexus Repository
https://issues.sonatype.org/secure/BrowseProject.jspa?id=10001
Component/s: Maven
https://issues.sonatype.org/issues/?jql=project%3D10001%20AND%20%22component%22%3D15178%20ORDER%20BY%20priority%20ASC
Affects Version/s: 3.22.1
https://issues.sonatype.org/issues/?jql=project%3D10001%20AND%20%22affectedVersion%22%3D19229%20ORDER%20BY%20priority%20ASC, 3.26.1 https://issues.sonatype.org/issues/?jql=project%3D10001%20AND%20%22affectedVersion%22%3D20138%20ORDER%20BY%20priority%20ASC, 3.27.0 https://issues.sonatype.org/issues/?jql=project%3D10001%20AND%20%22affectedVersion%22%3D20123%20ORDER%20BY%20priority%20ASC, 3.29.2 https://issues.sonatype.org/issues/?jql=project%3D10001%20AND%20%22affectedVersion%22%3D21031%20ORDER%20BY%20priority%20ASC
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Mahendra Surani
https://issues.sonatype.org/secure/ViewProfile.jspa?name=msurani
Assignee: Unassigned
Resolution: Unresolved Votes: 5
Labels: migration-announce, supportant
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Caused
Duplicate
Relates
is related to NEXUS-26814
https://issues.sonatype.org/browse/NEXUS-26814 maven-metadata.xml
files are not remo... New

Last Updated By: Nicholas Blair Nicholas Blair
Date of First Response: 14/Sep/20 6:00 PM
Notability: 3
Impact: 3

Description

Rebuild maven metadata task does not remove metadata files from folders
with no assets.

The clean up task in version 3.26.1 was leaving snapshot folders with no
maven assets, except for the maven-metadata.xml. This seems to be fixed
in 3.27.0, but the problem is that the there is no way to remove these
maven-metadata.xml files using the rebuild maven metadata task.

Expected: The rebuild maven metadata should remove maven-metadata.xml
if there are no maven assets in that folder.

Comments

Comment by Joe Tom [X] (Inactive)
https://issues.sonatype.org/secure/ViewProfile.jspa?name=jtom [
09/14/20 ]

I assume workaround can remove manually but if wrong, please let me know.

Comment by Louis-Rémi Paquet
https://issues.sonatype.org/secure/ViewProfile.jspa?name=lrp [ 02/24/21 ]

The manual way is not realistic given the number of different assets we
have.

If the problem is now fixed in 3.27.0+, I think we could get away with a
script deleting those metadata files left behind.

Comment by Bas
https://issues.sonatype.org/secure/ViewProfile.jspa?name=Popo [
04/05/21 ]

Any news on this? This has been plaguing our CI/CD setup for months now.
We've got thousands upon thousands of useless
maven-metadata.xml/maven-metadata.xml.md5/maven-metadata.xml.sha1 files.

We've even seen Jenkins builds start to fail because Nexus is taking too
long to respond to requests.

Comment by Louis-Rémi Paquet
https://issues.sonatype.org/secure/ViewProfile.jspa?name=lrp [ 04/06/21 ]

If that still occurs with the latest versions,

I suggest you to write code/script to interact with the REST api to deal
with the dangling files.

You can also delete the whole folder if it's only affecting snapshots.
However, you'll have to republish them if you are indeed using these
snapshots.

Comment by Bas
https://issues.sonatype.org/secure/ViewProfile.jspa?name=Popo [
04/18/21 ]

I tried the REST API, but it is simply not suited for this kind of
massive cleaning job. I don't see any other option than bulk-deleting
the entire repo contents.

Unless Sonatype fixes the issue.

Comment by Nicholas Blair
https://issues.sonatype.org/secure/ViewProfile.jspa?name=nblair [
05/10/23 ]

Sonatype will retire our public-facing Jira instances on May 25, 2023.
This includes https://issues.sonatype.org/browse/NEXUS
https://issues.sonatype.org/browse/NEXUS. The decision is necessitated
by a need for increased security as well as to replace a system that is
almost at “end of life” with Atlassian.

Moving forward, please watch the Release Notes
https://help.sonatype.com/repomanager3/product-information/release-notes for a list of issues fixed in each product release.

Customers with active subscriptions to Sonatype solutions may report
defects by raising a support incident at: https://support.sonatype.com
https://support.sonatype.com/.

Users of Sonatype Nexus Repository OSS should file issues in:
https://github.com/sonatype/nexus-public
https://github.com/sonatype/nexus-public. Please see
#105
#105 for more details.

Generated at Fri May 12 07:51:52 UTC 2023 using Jira
9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.

[NEXUS-28610] Typo in Directories documentation

Nexus version OSS 3.33.0

Maybe it is because I'm not a native speaker, but "to out" does not seem to be the right verb here:

These log files include messages that would typically be too noisy to out into the main application log.

If it is, just ignore me and close the ticket. :-)

Found on https://help.sonatype.com/repomanager3/installation/directories

[NEXUS-26802] "Unable to show requested tree entry" when refreshing after last entry was deleted

Nexus version OSS 3.34.1-01

If you are browsing a repository and delete the last entry, then press the Refresh button in the upper right, you get the error "Unable to show requested tree entry" shown.

[NEXUS-26814] maven-metadata.xml files are not removed, causing slowness when fetching them

Back to previous view https://issues.sonatype.org/browse/NEXUS-26814

[NEXUS-26814] maven-metadata.xml files are not removed, causing
slowness when fetching them
https://issues.sonatype.org/browse/NEXUS-26814 Created: 02/23/21
Updated: 05/10/23

Status: New
Project: Sonatype Nexus Repository
https://issues.sonatype.org/secure/BrowseProject.jspa?id=10001
Component/s: Maven
https://issues.sonatype.org/issues/?jql=project%3D10001%20AND%20%22component%22%3D15178%20ORDER%20BY%20priority%20ASC
Affects Version/s: 3.22.1
https://issues.sonatype.org/issues/?jql=project%3D10001%20AND%20%22affectedVersion%22%3D19229%20ORDER%20BY%20priority%20ASC, 3.29.2 https://issues.sonatype.org/issues/?jql=project%3D10001%20AND%20%22affectedVersion%22%3D21031%20ORDER%20BY%20priority%20ASC, 3.30.0 https://issues.sonatype.org/issues/?jql=project%3D10001%20AND%20%22affectedVersion%22%3D20939%20ORDER%20BY%20priority%20ASC
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Louis-Rémi Paquet
https://issues.sonatype.org/secure/ViewProfile.jspa?name=lrp
Assignee: Unassigned
Resolution: Unresolved Votes: 3
Labels: migration-announce, performance, triaged
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2021-02-23-17-33-38-366.png
Issue Links:
Relates
relates NEXUS-25287 https://issues.sonatype.org/browse/NEXUS-25287
Rebuild maven metadata task does not ... Open

Last Updated By: Nicholas Blair Nicholas Blair
Date of First Response: 23/Feb/21 10:46 PM

Description

We ran into the issue of slowness (20s or more) to get maven-metadata files.

This happened for numerous artifacts under the same groupId.

All these tasks were run with no success of deleting thexe
maven-metadata.xml files

Repair - Rebuild Maven repository metadata (maven-metadata.xml)
https://help.sonatype.com/repomanager3/system-configuration/tasks#Tasks-Repair-RebuildMavenrepositorymetadata(maven-metadata.xml)
Maven - Delete SNAPSHOT
https://help.sonatype.com/repomanager3/system-configuration/tasks#Tasks-Maven-DeleteSNAPSHOT
Cleanup Repositories using their associated policies (with policies
defined on the right groupId)
Rebuild Repository Index
Compact blob store (probably not related but we tried everything )

Artifacts are, in fact, cleaned but maven-metadata.xml are still there.

After manually, through the UI, removing all these leftover files for a
particular groupId, fetching maven-metadata under this groupId was fast
again.

This was seen on 3.22.1 and 3.29.2 on our side but may affect other
versions as well.

Comments

Comment by Joe Tom [X] (Inactive)
https://issues.sonatype.org/secure/ViewProfile.jspa?name=jtom [
02/23/21 ]

Possibly duplicate of NEXUS-25287
https://issues.sonatype.org/browse/NEXUS-25287?

It is not clear to me from the summary/description if the issue is the
slowness or the issue is the repair. If the repair seems like a likely
dup. If the slowness, I suspect we'd need more info.

Comment by Louis-Rémi Paquet
https://issues.sonatype.org/secure/ViewProfile.jspa?name=lrp [ 02/23/21 ]

The issue here is the maven-metadata.xml files not being deleted when
the artifacts are.

Slowness is the symptom of this issue.

We experienced slowness which, according to our conclusions, is due to
the too great number of maven-metadata.xml files inside a specific
artifactId (one per each snapshot versions)

Comment by Joe Tom [X] (Inactive)
https://issues.sonatype.org/secure/ViewProfile.jspa?name=jtom [
02/23/21 ]

Ah I see. So then 25287 is just probably why your task fix attempts
failed. Thanks for clarify.

Comment by Joe Tom [X] (Inactive)
https://issues.sonatype.org/secure/ViewProfile.jspa?name=jtom [
02/23/21 ]

I can reproduce this behavior by manually deleting every asset (via browse).
The behavior does not seem reproducable if I delete the component (which
iiuc would also include delete via search as I believe that just shows
components).
There doesn't seem to be a workaround outside of further manual deletion
(given the linked ticket).

Comment by Louis-Rémi Paquet
https://issues.sonatype.org/secure/ViewProfile.jspa?name=lrp [ 02/24/21 ]

So, yes it's a duplicate if, when running the cleanup task, the
maven-metadata.xml is being removed when the assets are.

However, I'm still trying to find a way to delete them automatically and
in batch. We have a lot of them.

Comment by Joe Tom [X] (Inactive)
https://issues.sonatype.org/secure/ViewProfile.jspa?name=jtom [
02/24/21 ]

Sorry if I wasn't clear, it's not a duplicate IMO now that I understand
your issue. Cleanup is a workaround, but it shouldn't behave that way.
This ticket is the cause. Will let triage team disagree with me when we
get there. Thanks for your patience and report.

Comment by Bas
https://issues.sonatype.org/secure/ViewProfile.jspa?name=Popo [
04/05/21 ]

Any news on this? This has been plaguing our CI/CD setup for months now.
We've got thousands upon thousands of useless
maven-metadata.xml/maven-metadata.xml.md5/maven-metadata.xml.sha1 files.

We've even seen Jenkins builds start to fail because Nexus is taking too
long to respond to requests.

Comment by R. Fitzner
https://issues.sonatype.org/secure/ViewProfile.jspa?name=fitzner [
06/27/22 ]

Dear Sonatype team,

since there is not update on this issue so far, can you please provide a
groovy script to clean up theses undetached metadata.xml files (incl.
matching checksum files) please?

Thank you for your help in advance.

Comment by Nicholas Blair
https://issues.sonatype.org/secure/ViewProfile.jspa?name=nblair [
05/10/23 ]

Moving forward, please watch the Release Notes
https://help.sonatype.com/repomanager3/product-information/release-notes for a list of issues fixed in each product release.

Customers with active subscriptions to Sonatype solutions may report
defects by raising a support incident at: https://support.sonatype.com
https://support.sonatype.com/.

Users of Sonatype Nexus Repository OSS should file issues in:
https://github.com/sonatype/nexus-public
https://github.com/sonatype/nexus-public. Please see
#105
#105 for more details.

Generated at Fri May 12 07:48:15 UTC 2023 using Jira
9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.

[NEXUS-23658] npm Audit support in Nexus Repository without an IQ server

Original issue: https://issues.sonatype.org/browse/NEXUS-23658 (https://web.archive.org/web/20230517144340/https://issues.sonatype.org/browse/NEXUS-23658)

npm audit command should work (without the need of adding IQ server) when using Nexus as repository.

I suppose Nexus could easily proxy the "audit" requests to https://registry.npmjs.org/

Nexus failing to find gems via Bundler when using a group repo

Originally reported in forum post Nexus failing to find Gems as a Bundler source but which exist in the Nexus UI

What problem are you trying to solve?

When running Bundler, Nexus reports the following error:

Resolving dependencies…
Your bundle is locked to GEM_NAME (GEM_VERSION) from rubygems repository https://nexus.example.com/repository/rubygems/ or installed locally, but that version can no longer be found in that source.
That means the author of GEM_NAME (GEM_VERSION) has removed it. You’ll need to update your bundle to a version other than GEM_NAME (GEM_VERSION) that hasn’t been removed in order to install.

where GEM_NAME and GEM_VERSION refer to some internal or public gem. Exactly which gem fails depends on what needs updating on a particular machine. It has also been seen to work then fail if the gem is removed and bundle install is run again.

The gem referenced is clearly available in Nexus when browsing via the UI
In the case of public gems, the gem and specified version are available on rubygems.org
There is no evidence in Nexus logs of what is happening (errors, warning or informational)

Do you have a workaround you are using at present?

Taking the group out of the picture seems to work, however this completely defeats the purpose of using a repo group and means updating many projects.

# source '.../rubygems
source '.../rubygems-proxy'

source '.../rubygems-hosted' do
  # Internal gems
end

# Public gems

What feature or behavior is this required for?

Installing project dependencies

How could we solve this issue? (Not knowing is okay!)

Without any diagnostic information, we have no idea why this is occurring.

Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?

Reproduced with Nexus OSS 3.53.0, 3.53.1 and 3.54.1-01
Operating system is Ubuntu 18.04 installed with the unix package. No database is specified.
We are using a standard group setup with a hosted rubygems repo for internal gems and proxy for public gems
Our install has been working fine for years and no configuration changes were made since an upgrade 6-7 months before this started happening

Anything else?

Nope

[NEXUS-28674] Allow multiple ldap addresses or copying of ldap configurations

Nexus version OSS 3.33.0

We have two domain controllers in our network that mirror each other if one needs to go down.
It would be nice if there were an easy way to configure both.
Currently you have to completey configure each connection manually.

It would be nice if you could either supply multiple host names. For example in TeamCity conifiguration I can just do

java.naming.provider.url=ldaps://dc1.company.com/dc=company,dc=com ldaps://dc2.company.com/dc=company,dc=com

and it will try dc2 if dc1 is not reachable.

Another alternative would be the possibility to copy a connection, so that only the hostname and name need to be changed and the rest ist just copied.

[NEXUS-28671] Possible Typo in "Searching for Components" doc

Nexus version OSS 3.33.0

Found on https://help.sonatype.com/repomanager3/user-interface/searching-for-components:

(imagine wanting to search for "aether-util" (see below for more details on double quotes), this would require the full name to match against, rather than a tokenized version)

should probably be (code format for "aether-util")

(imagine wanting to search for "aether-util" (see below for more details on double quotes), this would require the full name to match against, rather than a tokenized version)

When running behind IIS as a reverse proxy, error message "Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)" appears

What problem are you trying to solve?

(Migrated from Jira - NEXUS-21834)

I've setup Nexus on Windows, using IIS as a reverse proxy, and I created some APT repositories.

I've successfully uploaded a couple of packages in it, but when I try doing apt-get update from a client (especially an older one), I get the following error:

Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)

After some research, it seems that the problem is that IIS (being on Windows) sends the InRelease file with CRLF instead of LF. If I manually (I'm using Fiddler as a proxy-in-the-middle) remove the CR characters from the output, apt-get update works perfectly (I've managed to install a couple of packages).

Do you have a workaround you are using at present?

I managed to do a workaround, using URL rewrite.
Add this to web.config:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <rewrite>
            <outboundRules>
                <rule name="Replace CRLF with LF" preCondition="ReleaseFile">
                    <match filterByTags="None" pattern="\r" />
                    <action type="Rewrite" value="" />
                </rule>
                <preConditions>
                    <preCondition name="ReleaseFile">
                        <add input="{REQUEST_URI}" pattern="/repository/([-a-z0-9]*)/dists/(\w*)/InRelease" />
                    </preCondition>
                </preConditions>
            </outboundRules>
        </rewrite>
    </system.webServer>
</configuration>

And then it just works!

The REQUEST_URI does most of the heavy lifting. It should work for most cases, but if it doesn't, it's easy to extend the regular expression, or even hardcode the URL for the repo.

This is still just a workaround, but it's one that works without any changes to the code.

What feature or behavior is this required for?

This is required to host an apt repository on a nexus instance running on Windows, using IIS as a reverse proxy.

How could we solve this issue? (Not knowing is okay!)

I had made a patch and pull request for the fix from when nexus-repository-apt was a separate plugin. It was a simple fix, really, just replace \r with the empty string. The original pull request probably doesn't work as-is anymore, because the file has changed since then, but the principle remains the same: Add these three lines before signing the release files:

releaseFile = releaseFile.replace("\r", "");
inRelease = new String(inRelease, Charsets.UTF_8).replace("\r", "").getBytes();
releaseGpg = new String(releaseGpg, Charsets.UTF_8).replace("\r", "").getBytes();

Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?

It's been a very long time since I opened this bug, but it's still there on Nexus 3.53.0-01, on Windows Server 2022 21H2, using the default database (Embedded OrientDB)

[NEXUS-31461] Unpredictable sort order for Maven versions

Status: New
Project: Sonatype Nexus Repository
Component/s: Maven, REST, Search
Affects Version/s: 3.38.0, 3.38.1, 3.40.1, 3.46.0, 3.48.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Hardeep Nagra Assignee: Unassigned
Resolution: Unresolved Votes: 19
Labels: migration-announce, regression, sam-cashew, supportant
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2022-05-31-11-54-54-452.png
Issue Links:
Caused
is caused by NEXUS-28918 Search API for maven format does not ... Closed
Duplicate
Relates
is related to NEXUS-30694 Sorting Maven components with Version... Closed
Last Updated By:
Nicholas Blair
Nicholas Blair
Date of First Response: 08/Mar/22 3:01 PM
Story Points: 5
Team: NXRM - Mad Max
Notability: 3
Impact: 2

Description
A follow-up to NEXUS-30694, the same issue is still occurring for maven versions where a random order is being returned.

To reproduce:

Uploaded two snapshots to 3.38:

mvn deploy:deploy-file -DgroupId=com.foo.hsmservice.service -DartifactId=hsmservice-deployment -Dversion=1.31-us_481184_luigi__migration_2-SNAPSHOT -DgeneratePom=true -Dpackaging=jar -DrepositoryId=nexus -Durl=http://localhost:8081/repository/maven-snapshots -Dfile=./testjar.jar
2. Call the search/assets/download REST API, to retrieve the latest version e.g.

curl -v -u admin:admin123 "http://localhost:8081/service/rest/v1/search/assets/download?sort=version&repository=maven-snapshots&maven.groupId=com.foo.hsmservice.service&maven.artifactId=hsmservice-deployment&maven.baseVersion=1.31-us_481184_luigi__migration_2-SNAPSHOT&maven.extension=jar"
And note the version returned.

Then repeat steps 1-2 again and note that the latest timestamped snapshot is not returned. Instead the order is random.

Potential Cause:

For the given version strings e.g.

1.31-us_481184_luigi__migration_2-20220312.160843-37
1.31-us_481184_luigi__migration_2-20210419.153348-38
It seems to be much the same as NEXUS-30694 where the "normalized_version" is returning the same values resulting in an unpredictable order e.g.

jshell> versionNormalizer.getNormalizedValue("1.31-us_481184_luigi__migration_2-20210412.160843-37");
$27 ==> "000000001.000000031.000000000.b.us_-000481184-luigi__migration_000000002"
jshell> versionNormalizer.getNormalizedValue("1.31-us_481184_luigi__migration_2-20210419.153348-38");
$28 ==> "000000001.000000031.000000000.b.us-000481184-_luigi__migration_000000002"
However please be aware it is not just Snapshot versions affected, Release versions with a similar string also have the same issue e.g.

jshell> versionNormalizer.getNormalizedValue("1.31-us_481184_luigi_migration-1");
$8 ==> "000000001.000000031.000000000.e.us_-000481184-luigi_migration"
jshell> versionNormalizer.getNormalizedValue("1.31-us_481184_luigi_migration-2");
$9 ==> "000000001.000000031.000000000.e.us-000481184-_luigi_migration"
Expected:

Versions should be sorted in alpha-numeric order.

Comments
Comment by José Coelho [ 05/30/22 ]
I'm experiencing this same issue in Nexus 3.38.1-01

Comment by Laurent Thoulon [ 05/31/22 ]
Adding a screenshot of the issue on my end. We use a versioning system that integrates the timestamp and as you can see the timestamps are not in the proper order.

Comment by Arnab [ 07/05/22 ]
Adding some observations on the issue for SNAPSHOT versions (on 3.38.1-01):

The same search endpoint (service/rest/v1/search/assets) returns different ordering and different latest version for the same G, A, V, Extension & Classifier combination.
Not only the latest version is returned incorrectly (less frequent), order of appearance for rest of the available version is also random in nature.
In my test example following was the returned order in two different times for the same URL (expected descending order)
-7, -8, -1, -4, -2, -3, -5, -6
-8, -4, -5, -6, -7, -1, -2, -3

This doesn't sort with the timestamp as well, it's not deterministic in that way either.
Comment by art lucero [ 07/14/22 ]
still an issue on 3.40.1-01

Comment by Benjamin Peter [ 07/27/22 ]
We also have this issue. I found this command helpful to see if we also had the problem.

http https://nexus/service/rest/v1/search/assets\?sort\=version\&repository\=myrepo\&maven.groupId\=mygid\&maven.artifactId\=myid\&maven.baseVersion\=1.0.0-RC-SNAPSHOT\&maven.extension\=jar --pretty=none | jq '.items[] | .maven2.version' | uniq
Comment by bendem [ 08/23/22 ]
Would like to add that ascending sort works fine, it's just the descending sort that's broken:

curl '$API/search/assets/?sort=version&direction=desc&repository=maven-snapshots&maven.extension=war&maven.groupId=be.liege.cti.population&maven.artifactId=population-web-service&maven.baseVersion=7.0.3-WOCODO-SNAPSHOT&maven.classifier=' | jq -r '.items[].maven2.version'
7.0.3-WOCODO-20220823.065340-10
7.0.3-WOCODO-20220823.073743-11
7.0.3-WOCODO-20220823.081558-12
7.0.3-WOCODO-20220823.081622-13
7.0.3-WOCODO-20220822.074517-9
7.0.3-WOCODO-20220819.073504-8
7.0.3-WOCODO-20220223.142723-7

curl '$API/search/assets/?sort=version&direction=asc&repository=maven-snapshots&maven.extension=war&maven.groupId=be.liege.cti.population&maven.artifactId=population-web
-service&maven.baseVersion=7.0.3-WOCODO-SNAPSHOT&maven.classifier=' | jq -r '.items[].maven2.version'
7.0.3-WOCODO-20220223.142723-7
7.0.3-WOCODO-20220819.073504-8
7.0.3-WOCODO-20220822.074517-9
7.0.3-WOCODO-20220823.065340-10
7.0.3-WOCODO-20220823.073743-11
7.0.3-WOCODO-20220823.081558-12
7.0.3-WOCODO-20220823.081622-13

Comment by bendem [ 08/23/22 ]
Nevermind, it just worked by mistake. I have the same behavior now:

curl -s '$API/search/assets/?sort=version&direction=asc&repository=maven-snapshots&maven.extension=war&maven.groupId=be.liege.cti.population&maven.artifactId=population-web-service&maven.baseVersion=7.0.3-WOCODO-SNAPSHOT&maven.classifier=' | jq -r '.items[].maven2.version'
7.0.3-WOCODO-20220223.142723-7
7.0.3-WOCODO-20220819.073504-8
7.0.3-WOCODO-20220822.074517-9
7.0.3-WOCODO-20220823.065340-10
7.0.3-WOCODO-20220823.081622-13
7.0.3-WOCODO-20220823.073743-11
7.0.3-WOCODO-20220823.081558-12
7.0.3-WOCODO-20220823.085042-14

Comment by Jan Wedding [ 01/31/23 ]
Any plans to get this fixed or any workaround to get results in a stable order?

Comment by BMW FS IT [ 03/22/23 ]
Hello,

We are also interested in a fix for this issue. Can you please provide an update with an expected date when this will be fixed?

Thank you!

Comment by Alexandre Chatiron [ 05/07/23 ]
I push a pull request for this problem #107 , seems to fix the problem for me

Can you check it ?

Thanks

Comment by Nicholas Blair [ 05/10/23 ]
Sonatype will retire our public-facing Jira instances on May 25, 2023. This includes https://issues.sonatype.org/browse/NEXUS. The decision is necessitated by a need for increased security as well as to replace a system that is almost at “end of life” with Atlassian.

Moving forward, please watch the Release Notes for a list of issues fixed in each product release.

Customers with active subscriptions to Sonatype solutions may report defects by raising a support incident at: https://support.sonatype.com.

Users of Sonatype Nexus Repository OSS should file issues in: https://github.com/sonatype/nexus-public. Please see #105 for more details.

Generated at Fri May 12 08:46:24 UTC 2023 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.

[NEXUS-26810] Advanced search link when browsing repositories without search permission

Nexus version OSS 3.34.1-01

If you are a user with nx-repository-view---browse but without nx-search-read, and you browse one of the repositories you have access to, there is an "Advanced search..." link in the upper right corner, that would lead you to the search page.

But as you don't have the privilege you are instead prompted to log in. (this was with the anonymous user, didn't try what happens with an authenticated user without the privilege).

Imho the link should not be shown if you don't have the right privilege to use it.

NEXUS-6779 Microsoft symbol server support

The Microsoft C/C++ and .NET ecosystems use debugging symbols with symbol files (.pdb) and symbol servers (host .pdb files).

Hosted debugging symbols serve as a critical aide in debugging versioned libraries and packages that you are not actively working on in a/their respective checked out source code repository.

Noteworthy, portable PDB is an alternative multi-platform format to the traditional Windows pdb format.

This issue is migrated from NEXUS-6779, where it had 77 votes.

These are directly related to NuGet support, developers working with NuGet packages often need the symbol files for these when debugging.

Microsoft's recommended configuration consists of quite a few servers, so having proxy support in Nexus would be useful:

http://www.symbolsource.org/Public/Home/VisualStudio

I did a bit of preliminary investigation. Outbound requests for symbol files from visual studio take this format:

http://referencesource.microsoft.com/symbols/System.Xml.pdb/48994C53259A42D6B3939159933C6D971/System.Xml.pdb

I think the number may be a Microsoft GUID.

Additionally, we should also provide support for hosted symbol server repositories, since developers of NuGet packages need a place to publish their symbol files.

Finally we will (obviously) need to have group repository support for symbol repositories so that the above can be aggregated.

Somewhat/Possibly related #140

[NEXUS-38846] Unable to upload .deb to apt repository when using gpg subkey

Nexus version 3.52.0-01

apt-hosted repository, which uses gpg subkey as Signing key, causes web-ui to lag and curl upload to fail successfully while attempting to upload .deb package. When using private.key everything works as intended.

Log

somenexus.io | 2023-04-24 08:30:15,871+0000 INFO [qtp389670052-383] admin org.sonatype.nexus.repository.upload.internal.OrientUploadManagerImpl - Uploading component with parameters: repository="apt" format="apt"
somenexus.io | 2023-04-24 08:30:15,874+0000 INFO [qtp389670052-383] admin org.sonatype.nexus.repository.upload.internal.OrientUploadManagerImpl - Asset with parameters: file="test_1.0.400_i386.deb"
somenexus.io | 2023-04-24 08:30:15,958+0000 ERROR [qtp389670052-383] admin org.sonatype.nexus.coreui.UploadResource - Unable to perform upload to repository apt
somenexus.io | java.lang.NullPointerException: null
somenexus.io | at org.bouncycastle.openpgp.operator.jcajce.JcaPGPContentSignerBuilder.build(Unknown Source)
somenexus.io | at org.bouncycastle.openpgp.PGPSignatureGenerator.init(Unknown Source)
somenexus.io | at org.sonatype.nexus.repository.security.GpgUtils.initPgpSignatureGenerator(GpgUtils.java:254)
somenexus.io | at org.sonatype.nexus.repository.security.GpgUtils.signInline(GpgUtils.java:169)
somenexus.io | at org.sonatype.nexus.repository.apt.internal.gpg.AptSigningFacet.signInline(AptSigningFacet.java:96)
somenexus.io | at org.sonatype.nexus.repository.apt.orient.internal.hosted.OrientAptHostedFacet.rebuildIndexes(OrientAptHostedFacet.java:183)
somenexus.io | at org.sonatype.nexus.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:49)
somenexus.io | at org.sonatype.nexus.repository.apt.orient.internal.hosted.OrientAptHostedFacet.ingestAsset(OrientAptHostedFacet.java:139)
somenexus.io | at org.sonatype.nexus.transaction.TransactionalWrapper.proceedWithTransaction(TransactionalWrapper.java:58)
somenexus.io | at org.sonatype.nexus.transaction.TransactionInterceptor.proceedWithTransaction(TransactionInterceptor.java:66)
somenexus.io | at org.sonatype.nexus.transaction.TransactionInterceptor.invoke(TransactionInterceptor.java:55)
somenexus.io | at org.sonatype.nexus.repository.apt.orient.internal.hosted.OrientAptHostedFacet.ingestAsset(OrientAptHostedFacet.java:107)
somenexus.io | at org.sonatype.nexus.repository.apt.orient.OrientAptUploadHandler.handle(OrientAptUploadHandler.java:69)
somenexus.io | at org.sonatype.nexus.repository.upload.internal.OrientUploadManagerImpl.handle(OrientUploadManagerImpl.java:110)
somenexus.io | at org.sonatype.nexus.coreui.internal.UploadService.upload(UploadService.java:78)
somenexus.io | at org.sonatype.nexus.coreui.UploadResource.postComponent(UploadResource.java:86)
somenexus.io | at com.palominolabs.metrics.guice.ExceptionMeteredInterceptor.invoke(ExceptionMeteredInterceptor.java:23)
somenexus.io | at com.palominolabs.metrics.guice.TimedInterceptor.invoke(TimedInterceptor.java:26)
somenexus.io | at org.sonatype.nexus.validation.internal.ValidationInterceptor.invoke(ValidationInterceptor.java:53)
somenexus.io | at org.apache.shiro.guice.aop.AopAllianceMethodInvocationAdapter.proceed(AopAllianceMethodInvocationAdapter.java:49)
somenexus.io | at org.apache.shiro.authz.aop.AuthorizingAnnotationMethodInterceptor.invoke(AuthorizingAnnotationMethodInterceptor.java:68)
somenexus.io | at org.apache.shiro.guice.aop.AopAllianceMethodInterceptorAdapter.invoke(AopAllianceMethodInterceptorAdapter.java:36)
somenexus.io | at org.sonatype.nexus.coreui.UploadResource.postComponentWithHtmlResponse(UploadResource.java:108)
somenexus.io | at com.palominolabs.metrics.guice.ExceptionMeteredInterceptor.invoke(ExceptionMeteredInterceptor.java:23)
somenexus.io | at com.palominolabs.metrics.guice.TimedInterceptor.invoke(TimedInterceptor.java:26)
somenexus.io | at org.sonatype.nexus.validation.internal.ValidationInterceptor.invoke(ValidationInterceptor.java:53)
somenexus.io | at org.apache.shiro.guice.aop.AopAllianceMethodInvocationAdapter.proceed(AopAllianceMethodInvocationAdapter.java:49)
somenexus.io | at org.apache.shiro.authz.aop.AuthorizingAnnotationMethodInterceptor.invoke(AuthorizingAnnotationMethodInterceptor.java:68)
somenexus.io | at org.apache.shiro.guice.aop.AopAllianceMethodInterceptorAdapter.invoke(AopAllianceMethodInterceptorAdapter.java:36)
somenexus.io | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
somenexus.io | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
somenexus.io | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
somenexus.io | at java.lang.reflect.Method.invoke(Method.java:498)
somenexus.io | at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:138)
somenexus.io | at org.jboss.resteasy.core.ResourceMethodInvoker.internalInvokeOnTarget(ResourceMethodInvoker.java:546)
somenexus.io | at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTargetAfterFilter(ResourceMethodInvoker.java:435)
somenexus.io | at org.jboss.resteasy.core.ResourceMethodInvoker.lambda$invokeOnTarget$0(ResourceMethodInvoker.java:396)
somenexus.io | at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:358)
somenexus.io | at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:398)
somenexus.io | at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:365)
somenexus.io | at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:338)
somenexus.io | at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:440)
somenexus.io | at org.jboss.resteasy.core.SynchronousDispatcher.lambda$invoke$4(SynchronousDispatcher.java:229)
somenexus.io | at org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0(SynchronousDispatcher.java:135)
somenexus.io | at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:358)
somenexus.io | at org.jboss.resteasy.core.SynchronousDispatcher.preprocess(SynchronousDispatcher.java:138)
somenexus.io | at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:215)
somenexus.io | at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:245)
somenexus.io | at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:61)
somenexus.io | at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
somenexus.io | at org.sonatype.nexus.siesta.internal.resteasy.ComponentContainerImpl.service(ComponentContainerImpl.java:111)
somenexus.io | at org.sonatype.nexus.siesta.SiestaServlet.service(SiestaServlet.java:137)
somenexus.io | at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
somenexus.io | at com.google.inject.servlet.ServletDefinition.doServiceImpl(ServletDefinition.java:290)
somenexus.io | at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:280)
somenexus.io | at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:184)
somenexus.io | at com.google.inject.servlet.DynamicServletPipeline.service(DynamicServletPipeline.java:71)
somenexus.io | at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:85)
somenexus.io | at org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:61)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)
somenexus.io | at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:154)
somenexus.io | at org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:66)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)
somenexus.io | at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:154)
somenexus.io | at org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:66)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)
somenexus.io | at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:154)
somenexus.io | at org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:66)
somenexus.io | at org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:458)
somenexus.io | at org.sonatype.nexus.security.SecurityFilter.executeChain(SecurityFilter.java:96)
somenexus.io | at org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:373)
somenexus.io | at org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)
somenexus.io | at org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)
somenexus.io | at org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:387)
somenexus.io | at org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:370)
somenexus.io | at org.sonatype.nexus.security.SecurityFilter.doFilterInternal(SecurityFilter.java:112)
somenexus.io | at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:154)
somenexus.io | at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
somenexus.io | at com.codahale.metrics.servlet.AbstractInstrumentedFilter.doFilter(AbstractInstrumentedFilter.java:112)
somenexus.io | at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
somenexus.io | at org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:61)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)
somenexus.io | at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:154)
somenexus.io | at org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:66)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)
somenexus.io | at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:154)
somenexus.io | at org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:66)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)
somenexus.io | at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:154)
somenexus.io | at org.apache.shiro.web.servlet.ProxiedFilterChain.doFilter(ProxiedFilterChain.java:66)
somenexus.io | at org.apache.shiro.web.servlet.AbstractShiroFilter.executeChain(AbstractShiroFilter.java:458)
somenexus.io | at org.sonatype.nexus.security.SecurityFilter.executeChain(SecurityFilter.java:96)
somenexus.io | at org.apache.shiro.web.servlet.AbstractShiroFilter$1.call(AbstractShiroFilter.java:373)
somenexus.io | at org.apache.shiro.subject.support.SubjectCallable.doCall(SubjectCallable.java:90)
somenexus.io | at org.apache.shiro.subject.support.SubjectCallable.call(SubjectCallable.java:83)
somenexus.io | at org.apache.shiro.subject.support.DelegatingSubject.execute(DelegatingSubject.java:387)
somenexus.io | at org.apache.shiro.web.servlet.AbstractShiroFilter.doFilterInternal(AbstractShiroFilter.java:370)
somenexus.io | at org.sonatype.nexus.security.SecurityFilter.doFilterInternal(SecurityFilter.java:112)
somenexus.io | at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:154)
somenexus.io | at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.executeChain(AdviceFilter.java:108)
somenexus.io | at org.apache.shiro.web.servlet.AdviceFilter.doFilterInternal(AdviceFilter.java:137)
somenexus.io | at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:154)
somenexus.io | at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
somenexus.io | at com.sonatype.nexus.licensing.internal.LicensingRedirectFilter.doFilter(LicensingRedirectFilter.java:116)
somenexus.io | at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
somenexus.io | at com.codahale.metrics.servlet.AbstractInstrumentedFilter.doFilter(AbstractInstrumentedFilter.java:112)
somenexus.io | at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
somenexus.io | at org.sonatype.nexus.internal.web.ErrorPageFilter.doFilter(ErrorPageFilter.java:79)
somenexus.io | at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
somenexus.io | at org.sonatype.nexus.internal.web.EnvironmentFilter.doFilter(EnvironmentFilter.java:101)
somenexus.io | at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
somenexus.io | at org.sonatype.nexus.internal.web.HeaderPatternFilter.doFilter(HeaderPatternFilter.java:98)
somenexus.io | at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:82)
somenexus.io | at com.google.inject.servlet.DynamicFilterPipeline.dispatch(DynamicFilterPipeline.java:104)
somenexus.io | at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:133)
somenexus.io | at org.sonatype.nexus.bootstrap.osgi.DelegatingFilter.doFilter(DelegatingFilter.java:73)
somenexus.io | at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:201)
somenexus.io | at org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626)
somenexus.io | at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:552)
somenexus.io | at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
somenexus.io | at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:600)
somenexus.io | at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
somenexus.io | at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
somenexus.io | at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624)
somenexus.io | at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
somenexus.io | at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1440)
somenexus.io | at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
somenexus.io | at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:505)
somenexus.io | at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1594)
somenexus.io | at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
somenexus.io | at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1355)
somenexus.io | at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
somenexus.io | at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
somenexus.io | at com.codahale.metrics.jetty9.InstrumentedHandler.handle(InstrumentedHandler.java:239)
somenexus.io | at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
somenexus.io | at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
somenexus.io | at org.eclipse.jetty.server.Server.handle(Server.java:516)
somenexus.io | at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:487)
somenexus.io | at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:732)
somenexus.io | at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:479)
somenexus.io | at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
somenexus.io | at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
somenexus.io | at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105)
somenexus.io | at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104)
somenexus.io | at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338)
somenexus.io | at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315)
somenexus.io | at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173)
somenexus.io | at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)
somenexus.io | at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:409)
somenexus.io | at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
somenexus.io | at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
somenexus.io | at java.lang.Thread.run(Thread.java:750)

[NEXUS-19183] Java JDK JRE 11/17 runtime support

Original issue: https://issues.sonatype.org/browse/NEXUS-19183 (https://web.archive.org/web/20230517160610/https://issues.sonatype.org/browse/NEXUS-19183)

Java 8 is not supported anymore for more than a year (2022/03/31).
Nexus has to be upgraded to support (at least) Java 11 and ideally Java 17 ASAP.

I'm not sure if any comment from the original issue has to be copied here as most of them are exasperation from the more than 4 years of waiting...

[NEXUS-28700] Formatting error in "Privileges" doc

Nexus version OSS 3.33.0

Found on https://help.sonatype.com/repomanager3/system-configuration/access-control/privileges:

should probably be

Nexus crash during start - v3.54.1-01

After upgrade to 3.54.1-01 it works for short time. But now it's crashing on start.

nexus.log

I this this is https://issues.sonatype.org/browse/NEXUS-27710 again. History shows that this issue exists for a long time now

Why can this be fixed?

[NEXUS-28707] Formatting error in "Storage Guide" doc

Nexus version OSS 3.33.0

Found on https://help.sonatype.com/repomanager3/repository-management/storage-guide:

should be

Support for NuGet symbol packages (.snupkg)

Debug symbols for NuGet packages can be published alongside the .nupkg file as a .snupkg file.

See the upstream Creating symbol packages docs.

Of particular interest will be section NuGet.org symbol package constraints.

When working with NuGet packages - the prevalent format in the popular .NET ecosystem - publishing debug symbols alongside the package is important to aid debugging of referenced libraries.

[NEXUS-11881] Delete 'directory' using HTTP DELETE request

https://issues.sonatype.org/browse/NEXUS-11881

With nexus 2 it was possible to delete artifact using DELETE URLs of the form

https://host/nexus/content/repositories/<repoId>/<groupId>/<artifactId>/<version>

This was very convenient to implement a custom cleanup strategy of releases published to nexus. This appears not to work anymore on nexus 3.

Can this be supported again? (either through simple HTTP DELETE or through REST?). Or is it perhaps already supported?

This functionality is not covered through the nexus cleanup tasks since Nexus does not know what artifacts constitute a release together and what the specific release cleanup policy is.

[NEXUS-28701] Formatting error in "Content Selectors" doc

Nexus version OSS 3.33.0

Found on [https://help.sonatype.com/repomanager3/system-configuration/access-control/content-selectors]:

should probably be

nexus-staging-maven-plugin deploy goal injection not invoked on maven 4

Version .13 of the plugin (latest) fails with maven 4
The "magic" where it replaces deploy plugin execution with maven staging plugin execution is failing, and the plugin isn't invoked while it was invoked in maven 3.
See maven issue for more details:
https://issues.apache.org/jira/browse/MNG-7627

[NEXUS-28702] Disabling "Allow developer debugging" does not have any effect

Nexus version OSS 3.33.0

I wondered that "Allow developer debugging" is enabled by default and decided to switch it off.

Then I reloaded the page where I have ?debug enabled and it is still in debug mode.

sonatype / nexus-public Goto Github PK

nexus-public's Introduction

Sonatype Nexus Repository Open Source Codebase

Downloadable Bundles

Support

Build Requirements

Configuring Maven for SNAPSHOT Dependencies

Building From Source

Running

License

Getting help

nexus-public's People

Contributors

Stargazers

Watchers

Forkers

nexus-public's Issues

What problem are you trying to solve/occured?

Do you have a workaround you are using at present?

How could we solve this issue? (Not knowing is okay!)

Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?

Helm Proxy: Nexus converts string to number in index.yaml causing Helm repo add to fail

What problem are you trying to solve?

Do you have a workaround you are using at present?

What feature or behavior is this required for?

How could we solve this issue? (Not knowing is okay!)

Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?

Anything else?

What problem are you trying to solve?

Do you have a workaround you are using at present?

What feature or behavior is this required for?

How could we solve this issue? (Not knowing is okay!)

Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?

Anything else?

What problem are you trying to solve?

Do you have a workaround you are using at present?

What feature or behavior is this required for?

How could we solve this issue? (Not knowing is okay!)

Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?

Recommend Projects

Recommend Topics

Recommend Org