On Fri, Apr 23, 2021 at 5:06 AM Eric Bresie <ebre...@gmail.com> wrote:
> Just to understand the problem being discussed > > There are Netbeans wrapper plugins (I.e. Netbeans specific artifacts) like > the JavaFX or Java EE plugins > These plug-ins have dependencies on third party libraries which (possibly > depending on licenses) are or are not included in the wrapper plug-in. > If included then the wrapper may need updating to reflect newer version > when developing or packaging the plug-in artifact (to be published > someplace like maven central) > If not included then they may need to be retrieved from a location in the > process (either development or runtime) which may no longer be available. > Specifically for the JEE ones. There is no "official" source of the original artifacts any more, the assets of codehaus have been mirrored across several repositories. And those are just mirrors, I don't know if anyone is actively maintaining them. For the new JEE, notably Java EE 8 and Jakarta EE 9, new artifacts need to be created. The JEE Wizard also needs to be updated back to what it originally did with orchestrating these artifacts. NB can readily create projects from archetypes, and that's not the issue I'm seeing. What I'm seeing is that there's hard coded behaviour that's dependent on the archetypes, so, potentially, if the archetype changes, the code and functionality breaks. Thus there's a tighter coupling between the two. I think the work is straightforward to restore the functionality for the EJB, I just don't know where the archetypes would be committed, or how they would be published. Would I just commit them to the NB source tree and publish them myself to Maven central? How and where is the process documented? Ostensibly it's a one shot, published once and done thing, so it's not like it needs a CI pipeline to back it up. It's more procedural than anything else. Regards, Will Hartung
