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.
Created attachment 127308 [details] screen_1 1. Create empty Maven project (File -> New Project -> Maven -> Java Application) 2. result: screen_1.png 3. Select default Java package and create new Groovy Class (screen_2.png) 4. Project structure is changed (no more Java classes): screen_3.png
Created attachment 127309 [details] screen_2
Created attachment 127310 [details] screen_3
Michale, could you please attach the project (I mean the one which seems to be broken after creating groovy class)? I'm following your steps, but it works for me just fine. Btw: What version of NB are you using?
Especially I'm interested in pom.xml (before and after) ..the problem has to be there, not sure why I'm not able to reproduce.
Created attachment 127311 [details] project directory
My configuration is: java -version java version "1.7.0_10-ea" Java(TM) SE Runtime Environment (build 1.7.0_10-ea-b14) Java HotSpot(TM) 64-Bit Server VM (build 23.6-b04, mixed mode) Product Version: NetBeans IDE 7.3 Beta (Build 201210011125) Java: 1.7.0_10-ea; Java HotSpot(TM) 64-Bit Server VM 23.6-b04 System: Mac OS X version 10.7.5 running on x86_64; US-ASCII; en_US (nb) User directory: /Users/michalo/Library/Application Support/NetBeans/7.3beta Cache directory: /Users/michalo/Library/Caches/NetBeans/7.3beta
Created attachment 127315 [details] Correct project structure Weird, even with your project it's working correctly. I'm attaching the screenshot from my environment.
Could you take a look into your Tools/Plugins/Installed to see if there is a groovy feature installed and enabled?
I'm sorry Michal but I can't move forward with this issue without more information. I didn't seen this behavior on my environment so far, so it's most probably caused a different configuration on your machine. Could you please also test if the problem persist in NetBeans 7.3beta2? Thanks in advance and please reopen the issue if you will find some additional information.