On Tue, 6 Oct 2026, 18:59 Michael Bien, <[email protected]> wrote:

> The open question is what should be the project marker and do we want
> pollute repos with nb config files - but I suppose there are solutions
> to that too, e.g a file at the root / private folders or even in the nb
> user config
>

My suggestion on the PR was any folder not otherwise picked up that has
either the default AuxiliaryConfiguration attribute (which as of NB31
should survive upgrades) or the .netbeans.xml file used for the sharable
storage. That will be the default way of storing any configuration against
them anyway, and people could choose whether to share the configuration or
not.

Of course, that's then implementation specific not API. Other platform
applications, plugins, etc. could choose an alternative mechanism.

There might also need to be a marker attribute or SPI for the group dialog
to mark folders that need to be turned into projects.

I was looking at a similar thing to your generic project after FOSDEM in
2020, but that year went a little awry. I wanted to provide some basic user
configurable actions and query support for working with unknown build
systems (Bach at the time).

Best wishes,

Neil

>

Reply via email to