On Tue, Jan 26, 2021 at 8:23 PM Josh Juneau <[email protected]> wrote:
> Thanks for the great feedback on the Java EE 8 archetype that is being > used with Apache NetBeans. When I created the archetype, it was not meant > to become a standard. Rather, it was meant as a starting point for Java EE > 8 projects and to get Java EE 8 project support into Apache NetBeans. I > was hoping that it would be built upon by the community over time, and even > that a better and more standardized Maven archetype be put into place. > The biggest issue with the archetype is that it's not designed for the NB JEE wizard at all, which actually creates 4 related projects instead of one. And there seems to be some regression that has crept in to the JEE 7 project builder that's making it fail. So, the greenfield JEE experience in Netbean right now is pretty rough. However, there is keen insight here that I think there is room for different JEE project types as well. A simple example that you have is a microprofile skeleton. That certainly doesn't need multiple projects, and I think it is a popular path forward. And, naturally, I think there should be support for Java EE 8 and Jakarta EE 9. Though functionally identical, the simple renaming would be helpful moving forward. If we can get the JEE 8 one fixed, the JEE 9 one will come "for free". Although I wonder if they had to rename all of their schemas as well, that would be a deeper issue when the IDE generates things like a persistence.xml or an ejb-jar.xml. What I don't know is what are the tell tales to the IDE that tell it that we're working with a "JEE" project, where it wants to hook up a deployment server, etc. Is it simply the detecting a packaging style of war, vs ejb, vs ear instead of jar that informs the IDE what to do? Does it look for the plugin in the pom? Consider a microprofile project. That would likely just be a standalone jar, bundling the microprofile runtime with the application code to make a fat jar...I guess. It has different deployment options. > All that said, I think it would be great to have the Apache NetBeans > projects generated by Maven archetypes that are all hosted under a standard > namespace. We should also be updating the archetypes as time goes on, as > needed. These are community supported, just like Apache NetBeans, so they > should continue to evolve. > I just don't know that once an archetype is checked in to the source base, when and how are those published to something like Maven Central. In theory, Apache also has its own repository, and I guess it routinely and automatically forwards up to Maven central? I don't think we'd need to install the archetypes locally as part of the module deployment, but that's certainly an option. Regards, Will Hartung
