chore: Add 'localNpm' Maven build profile and 'npm.registry' Maven property to accomodate the UI build in corporate environments#5465
Open
cdprete wants to merge 1 commit into
Conversation
… already installed Node and NPM instead of downloading it since the download may be blocked (e.g.: in corporate environments) and 'npm.registry' Maven property to allow to change the registry to use
cdprete
changed the title
cdprete
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi.
In corporate environments the access to certain resources may be blocked, may need some proxy settings or these resources may be provided through different channels (e.g.: an internal package manager).
This PR adds the possibility to build the UI locally with the available toolchain by:
npmsteps with theexec-maven-plugin, to leverage the already installed NodeJS and NPM and already available on thePATHnpm.registrywhich can be externally set with-Dnpm.registry=https://my.corporate.registryduring the build in order to point to the corporate internal registry rather than tohttps://registry.npmjs.org/