When adding a new version to analyze an Application that includes Maven based source code, you must tell the Console where to find the Maven local or remote HTTP/S repository. The location of the repository is crucial to ensure that any associated JAR files can be automatically discovered and that POM dependencies can also be located. See Configuring source code delivery for Maven for more information.
To tell Console where the repositories are located you can use this Maven panel:
Repositories discovered in the uploaded source code and any repositories defined at Application level always take priority over any repositories defined in this options panel.
Any repository added in this panel is valid for all Nodes (and therefore all applications) managed in Console. If you configure multiple large repositories in this panel, the source code delivery action can take a significant amount of time to process through all the repositories when only some may be relevant for a specific Application. To counter this, you can ALSO defined repositories at Application level (see Application - Config - Maven configuration settings) - these are specific to the Application and won't be valid for any other Application/Node.