[
https://issues.jboss.org/browse/JBIDE-26808?page=com.atlassian.jira.plugi...
]
Maneesh Mehra commented on JBIDE-26808:
---------------------------------------
This is great. Can these profiles be dynamically applied to build jobs too that run on
build systems depending on whether they run within the enterprise's trusted network or
outside ? Reason I am asking this is because some teams are doing upstream development and
have build systems that are located on both trusted and public systems. Its a challenge to
them to identify which repo to use, based on where the build job is running.
In any case, would you mind updating the Google doc with these instructions for benefit of
all developers ? I am sure developers will be mindful of switching ti an appropriate
profile based on where they are connected.
Also overall, what is the ETA for closure on this issue ?
Thx in advance.
Assure that npm on the machines uses internal Nexus NPM registry
-----------------------------------------------------------------
Key: JBIDE-26808
URL:
https://issues.jboss.org/browse/JBIDE-26808
Project: Tools (JBoss Tools)
Issue Type: Task
Components: qa
Affects Versions: 4.13.0.AM1
Reporter: Ondrej Dockal
Assignee: Jan Richter
Priority: Major
Fix For: 4.13.0.Final
According to [1] we need to take actions at projects using npm.
[1]:
https://docs.google.com/document/d/1dn1gQFaJ_Q0IOeRAnFAsBMgVRnwA8ieLQV-AG...
--
This message was sent by Atlassian Jira
(v7.13.5#713005)