The JEE Maven archetypes are a bit of a disaster right now, there's relevant issues in JIRA already.
But it brought up a question. Historically, and currently, the archetypes used for these projects (I don't know about others) are not part of Netbeans. They're external archetypes used by Netbeans. For example, originally, there were several from org.codehaus.mojo.archetypes. I don't know the original relationship between Sun/Oracle and codehaus. The current ones, for JEE 8, are from io.github.juneau001. Now, barring the detail that the JEE 8 ones are just flat out wrong given the structure of the JEE Maven Application Wizard (honestly, I don't know how these were committed -- this isn't even a subtle failure), I'm curious whether these should be "owned" by the Netbeans project, rather than a kind contributor. By own, I simply mean they're under the netbeans.apache.org name space, and the archetype templates are checked in to the NB source tree and, somehow, they're distributed to an appropriate Maven Repo to ideally get picked up by Maven Central. Does Netbeans already have a mechanism for publishing and managing archetypes? Any reason that NB can't or shouldn't do that? Regards, Will Hartung ]
