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.
I use Ubuntu Hardy Heron 8.04. I installed NB6.1 and then, installed Maven, Module Manager and the Missing Module Resolver without any problems. I then installed the Groovy plugin. It installed normally but afterwards, the NB IDE does not start anymore. When clicking the start icon, I get the Open 0 item status bar icon for few seconds but I never see the splashscreen. The System Monitor shows that the JVM is starting normally but stops after few seconds.
Created attachment 61006 [details] netbeans messages log
Maybe problem in autoupdate? Reassigning for evauation.
Sorry, but I cannot see any related problem with autoupdate. Reporter says: "I then installed the Groovy plugin. It installed normally but afterwards, the NB IDE does not start anymore." In this time Autoupdate code cannot called nor executed. I'm afraid I only can reassign back.
Created attachment 61023 [details] NB6.1 startup missing dependencies checkist
After de-installing and re-installing NB6.1 from scratch but without deleting the ¨user/.netbeans/6.1 directory, the Missing Module Resolver plugin kicked in upon NB61 startup with the attached message stating that some dependencies were not up to date. I let the Resolver resolved (after all, I only would have to re-install another time if it did not worked...) and after update, the NB61 started normally. As long as I did a clean install (deleting the .netbeans/6.1 directory) the problem persisted. When I did a dirty reinstall, the Resolver saved the day. However, after few tests, the integration with Java SE as described in Martin's blog is simply not working. But that is probably another issue alltogether.
After testing at the office under Windows XP, the behaviour is exactly the same. After a clean installation of the NB6.1 IDE followed by an separate installation of Maven, Module Manager and Missing Module Resolver, the installation of the Groovy plugin causes the Netbeans IDE to not start at all (no splash screen, nothing). From that point, I uninstalled NB6.1 from Windows Control Panel "Add/Remove programs" and reinstall it normally. At first start, a window displays a list of unresolved modules; click "Disable and Continue". Few seconds later, the Resolver proposes to download the missing modules. Accept the proposition and let the resolver installs the dependencies. After restarting NB6.1, the plugin somewhat works but integration between Groovy and Java as described in MA's blog is not present.
I will look at this next week, when I'll be back from JavaOne. For having Java SE integration working we'll need to push newer version of plugin to UC, I'll do that too.
So you added dev update center to 6.1 final, right?
Problem persists: I have a fresh and complete installation of Hardy Heron with a fresh download of NB6.1 which worked perfectly well. As soon as I install Groovy plugin (V1.2) with it's wealthy list of dependencies, NB does not start anymore. I don't even get to the splash screen. So I'll do my uninstall and reinstall trick once again. Question: Is the last comment addressed to me?
ledj56 : yes, it is addressed to you :-)
Maybe I am wrong but I do perceive little arrogance behind this comment...I would not normally confuse bug tracking with blog posting... I have added this UC quite some times ago on my home system (Windows and Linux) and on my office system (windows and today on my new linux install). I wonder how you could know that I was actually downloading the plugin at the exact moment you wrote that comment? Anyway...probably just a coincidence... Maybe your efforts would be better appreciated by ordinary users like me if that Update Center URL was published in the Groovy plugin wiki or blog. The UC name is of no use and it took me quite some Googling to finally find it in a Geerjan Blog entry; since then, I keep it in a bookmark and happily send it to my co-workers when I hear frustration comments about "Where the heck is that UC?...."; I will spare you the other comments about your project and planet Sun.... Publishing new functionality on your blog without updating the UC is also the kind of move that do not help your cause. We don't want to know how things are going in the trunk...we want to see and experiment what is published. So if it is not ready to be published in UC, you maybe better not to talk about it. When I joined this company, everybody was using Eclipse and I was the only Netbeans guy. Now almost all developpers are mostly using Netbeans with little Eclipse for some specific things. It is the first time though that a Netbeans plugin generate so much frustrations (and comments, and jokes, etc) to the point that we actually evaluate alternatives not only to the plugin but to Netbeans itself. It is actually to the point where the plugin is lessening NB's value. If you want to have a happy, helpful and supportive community, providing helpful information to the plugin users as opposed to the plugin developpers would be a very good time investment.
> Maybe I am Sorry, I have no idea what are you talking about (arrogance, blog posting...). This is P1 and I want it to be fixed or closed in any other way. > I wonder how you could know that I was actually downloading the plugin at the exact moment you wrote that comment? It's joke, isn't it? Of course I didn't know... > Maybe your efforts would be better appreciated by ordinary users like me if that Update Center URL was published... So this needs to be clarified. Dev UC should be used only in Dev builds, that's why it is not available anywhere else. Using it from final release is very bad idea. > Publishing new functionality on your blog without updating the UC is also the kind of move that do not help your cause. > We don't want to know how things are going in the trunk...we want to see and experiment what is published. > So if it is not ready to be published in UC, you maybe better not to talk about it. Every commit in trunk is published in Dev UC 3 times a day. If plugin is already installed, it takes updates from UC only if spec number was increased. I wasn't sure if this was done, but now I checked that, and it was done properly. > When I joined this company, everybody was using Eclipse and I was the only Netbeans guy. > Now almost all developpers are mostly using Netbeans with little Eclipse for some specific things. Thank you for this! > It is the first time though that a Netbeans plugin generate so much frustrations... I am really sorry to hear this, but please consider the fact that: a) you tried to install plugin in wrong IDE version (that's why I was asking about it earlier) b) plugin itself wasn't published yet in any milestone, early access, etc... it's not even alpha quality yet, just trunk snapshots. Do you use a lot of OS software from trunk? > If you want to have a happy, helpful and supportive community, providing helpful information Yes, I want, for sure, so please don't give up and try plugin in Dev build...
Decreasing to P3 as this is unsupported. Should be closed?
Ok, closing.