Management → Managing Components → Creating Components → Source Configuration Type Fields → Nexus Sonatype
The Nexus Sonatype source type component supports granular access and filtering for artifacts stored in Nexus repositories.
To use Nexus as an artifact source, select Nexus in Source Config Type and then configure the type-specific fields. For information about creating components, see Creating Components.
|Server URL||Base URL and port for the Nexus server, for example: http://localhost:8081|
|User Name||Nexus user name|
|Password||Password for the Nexus user|
|Repository||The name of the Nexus repository|
|Nexus Component||Specify a Nexus component name if you only want to import versions of that component. Use this field when you have multiple components in the same repository, for example, for NPM repositories.|
|Component Group||The group ID of the component to which the assets belong. In Maven repositories the ID follows Java package naming rules, for example, org.apache.maven.|
|Import folders as versions||Applies to repository types that do not have specific versions, for example, 'raw'. Folders with subfiles are imported as separate versions.|
|Import all new versions||Selected: all missing versions are imported.
Not selected: only the latest version is imported.
|Skip empty versions||Versions without content are not imported.|
Specify patterns to match files to include in the upload. You can match exact file paths and file names, or you can specify wildcards. The default value is **/*, for all directories and files.
You can specify exact file path and file name combinations with one entry per line. For example,
You can specify wildcards to match directories and files where the wildcard ** indicates every directory and the wildcard * indicates every file. For example, the pattern dist/**/* would retrieve the entire file tree under the dist directory.
Specify patterns to match files to exclude from the upload. You can match exact file paths and file names, or you can specify wildcards. See the examples in the row above.
|Preserve execute permissions||File execute permissions are preserved.|
|Import versions automatically||Configured version source are polled periodically for new versions.|
|Copy to CodeStation||
This option, selected by default, creates a tamper-proof copy of the artifacts and stores them in the embedded artifact management system, CodeStation. For optimal use of Deployment Automation, the check box should be selected.
If you deselect Copy to Codestation for this source configuration type, pointers to versions are saved in Deployment Automation rather than the versions themselves. This enables you to track the versions, but limits some functionality in Deployment Automation. See Maintaining Versions Externally.
|Use latest component properties for versions download||When component
version artifacts are downloaded, the properties set for the associated
component are used instead of the properties set when the version is created.
Component version properties are always preserved when a version is created.
|Default Version Type||The default version type to be created for imported versions.|
|Inherit cleanup settings||This environment will inherit version cleanup configurations from the settings of each component or the system.|
Copyright © 2011–2019 Micro Focus or one of its affiliates. All rights reserved.