This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Original reported by Arun Gupta in email: "For a Maven project, I don't even see the option of adding Frameworks during project creation. Why ?" Still more and more people is asking about the Framework step inside the new Maven project wizard, so at least it has sense to evaluate this option for Maven projects. There is another question whether it should be plain NB's Add Framework step or something like Add Dependency step which would handle our supported frameworks differently. I think that it needs some investigation how to do that as best. Thanks.
This is related to the fact that we just use a single archetype for Java EE projects which we don't try to customize/enhance during project creation, right? Not sure what it would entail to do some post-processing in the wizard.
AFAIK you are correct Petre. I don't have a strong opinion on this (speaking in general about customization in wizards) but I guess it could be useful to make even Maven projects more customizable - there were several votes with similar requests during the past few months. It's not problematic (technically) to enhance the project I'm just not sure if that's a standard way how to do this in Maven. I'll talk to Milos to know more learned opinion but it looks to me that obviously less experienced Maven users would benefit from this so I'm probably for it.
(In reply to comment #0) > There is another question whether it should be plain NB's Add Framework step or > something like Add Dependency step which would handle our supported frameworks > differently. Not sure again, but if we name it "Add Dependency" users will expect all versions from Maven central will be available. And from what I have understand on mailing discussion a lot of feature in e.g. persistence area won't work correctly when using e.g. Hibernate 4.x. On the other hand I think they are changing versions in pom.xml anyway :)
(In reply to comment #2) > I'm just not sure if that's a standard way how to do this in Maven. I'll talk > to Milos to know more learned opinion but it looks to me that obviously less > experienced Maven users would benefit from this so I'm probably for it. Great, thanks. That's why I wrote that it should be at least evaluated - I don't have strong opinion too. (In reply to comment #3) > Not sure again, but if we name it "Add Dependency" users will expect all > versions from Maven central will be available. Yeah and that's exactly what I thought too. :) It was just an idea about some kind of merged dependencies/framework step. Since our framework panel can be pretty useless for maven users. But dependencies panel don't allow our framework setup ... So both panels? :) I'm not a maven guy at all so sorry I'm not able to evaluate this properly. But since we speak and think about it more I'm not sure if the Framework tab in the maven project wizard is really wanted. I suppose that Milos already investigated about this by the project wizard implementation and the simplicity of the wizard will be intentional.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss