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.
Product Version: NetBeans IDE Dev (Build 20130218-0f0525fff6ef) (build form the javaee7 branch) Java: 1.7.0_06; Java HotSpot(TM) 64-Bit Server VM 23.2-b09 Runtime: Java(TM) SE Runtime Environment 1.7.0_06-b24 System: Linux version 3.2.0-27-generic running on amd64; UTF-8; en When I create new project and setup the server, the server is not set and by going thru project properties and by project run I'm always warned that the project was not set. Steps to reproduce: 1, create new Maven Project and set any server (I used GF 3.1.2.2) 2, go to the project properties->Run tab and you will see your server but 3, add JSF framework and you will see no server warning 4, close the properties and invoke Run on the project -> No server selected appears As you saw I tried more ways but I'm not able to set the server into my maven project. Thanks.
*** Bug 226649 has been marked as a duplicate of this bug. ***
Should be fixed in: web-main #c68126fe76f9 (javaee7 branch)
Thanks Martin.
Integrated into 'main-golden', will be available in build *201303042300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/c68126fe76f9 User: Martin Janicek <mjanicek@netbeans.org> Log: #226348 - Strange behavior around servers in the maven projects
I can still reproduce in the latest trunk builds (and I suspect also in the javaee7 builds). Did this break again? I am using GF 4 dev/promoted build.
Ok, I'll take a look at it later this week
Just for the record, works for me in the javaee7 branch.
Reproducible in trunk, I'm working on it..
The regression in trunk was caused by my changeset (web-main #889e29c0ae19) which was rewriting the code to use ProjectUtils.getPreferences instead of deprecated AuxiliaryProperties. It turns out that these two concepts are not completely interchangeable and thus I had to rewrite the rest of the maven.j2ee code to use the same preferences storage. Long story short: web-main #a16963ec8744 should fix the problem..