There's so much we don't own. We integrate. Yes, that has disadvantages, but also the advantage that we can help users with actually existing, e.g., Maven archetypes, rather than those made specifically for NetBeans.
On the other hand, there's nothing stopping anyone from providing pull requests for any Maven archetype, including their own custom ones, e.g., there's a new Micronaut project template in the upcoming 12.4 using the publicly available Micronaut Maven archetype. Gj On Thu, Apr 22, 2021 at 4:25 PM Will Hartung <willhart...@gmail.com> wrote: > On Wed, Apr 21, 2021 at 11:39 PM Geertjan Wielenga > <geertjan.wiele...@googlemail.com.invalid> wrote: > > > Indeed, if there's a particular technology that isn't supported correctly > > in NetBeans or is outdated, just create an issue and let's work on it. > > > > Can we do that, point to a specific problem that needs to be fixed? > > > > I would take a stab at fixing the JEE project wizards, but I'm not willing > to do that if NB can't own the maven archetypes. The archetypes and the > wizards are intertwined, it does not appear to be a simple wrapper around > just invoking the archetype, so one can't be changed without the other. > > If we can come up with a mechanic for hosting/publishing the archetypes, > then I'll open an issue and dig in to it further. > > Regards, > > Will Hartung >
