Does this maybe have something to do with the "type" of project involved
(i.e. was a new Maven project created, was it a "Java" project
[ant/gradle], from an existing project/existing code, etc.) ?  I know when
I was working on an "Ant project" vs a "Maven" project, the properties in
each were slightly different (i.e. Maven did not have "Libraries" purely
but instead had "Dependencies" and included "javascript properties", Ant
allowed adding dependency via "Libraries for the project", etc.)

At what point did the "no actions" become present? It sounds like in the
old iteration [which may have had actions] but after imported then no
longer exists in the new context?

So is this a possible issue in the "import" context, the "project" context,
or some other context?

Does an issue need to be raised for this then?

Eric Bresie
[email protected]


On Fri, Dec 3, 2021 at 5:35 PM Douglas Thompson (dthompson) <
[email protected]> wrote:

> 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?
>
>
>
>
>
> Thanks.
>
>
>
> Doug.
>
> Micron Confidential
>

Reply via email to