Micron Confidential I was able to find a manual work-around by copying the nbactions.xml from a previous version of NB then creating the path (Projects wasn’t in the path) and putting the file down. Seems to be working.
From: Douglas Thompson (dthompson) <[email protected]> Date: Friday, December 3, 2021 at 8:41 AM To: [email protected] <[email protected]> Subject: Re: NB 12.5 Maven Goal Definitions Sorry, I forgot images don’t come through. * In my NB -> Options -> Java -> Maven -> Edit Custom Goal Definitions * Adding an action shows grayed out with – Disabled next to it From: Douglas Thompson (dthompson) <[email protected]> Date: Friday, December 3, 2021 at 8:29 AM To: [email protected] <[email protected]> Subject: NB 12.5 Maven Goal Definitions We’re seeing a problem in our Windows 10 environments where, in NB 12.5, we can’t seem to set the Maven Goal definitions. I verified this on a clean install of NB 12.5 with Windows 10 (I did not import from a previous NB installation). NB 12.1 seems to be working fine, but it’s possible there were security measures added after having these set. Could this be some sort of security restriction in our Windows 10 environments, or is this a known issue? Is there a manual way we can modify files to enable Maven actions? [cid:[email protected]] Thanks. Doug. Micron Confidential
