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.

Bug 125864 - Dialogue blocking Output window when creating Rails project
Summary: Dialogue blocking Output window when creating Rails project
Status: NEW
Alias: None
Product: ruby
Classification: Unclassified
Component: Rails (show other bugs)
Version: 6.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: issues@ruby
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-23 18:18 UTC by algnod
Modified: 2011-01-28 20:11 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screenshot (104.78 KB, image/png)
2008-01-23 18:41 UTC, algnod
Details

Note You need to log in before you can comment on or make changes to this bug.
Description algnod 2008-01-23 18:18:46 UTC
Using: /netbeans-6.1-200801220000 Ruby only version

If I create a new Rails project and press finish, I am asked in an output window whether I would like to have my
application.rb overwritten. But I cannot access the output window and project creation is stalled.
Please see screenshot.
Comment 1 algnod 2008-01-23 18:21:13 UTC
Oh yes, and maybe the update rails, install jruby open ssl support and proxy settings buttons should be disabled at this
stage?
Comment 2 algnod 2008-01-23 18:41:37 UTC
Created attachment 55452 [details]
Screenshot
Comment 3 algnod 2008-01-30 08:49:44 UTC
I tried this again today with build:
netbeans-6.1-200801290002

and did not get to the point where I was queried, if application.rb should be overridden.

What is different from my previous attempt, is that this time I did not update rails because version 2.0.2 is now in
included in the daily build.

So to retest you would have to find the situation where you are prompted whether or not application.rb should be
overridden. This might be the case with a rails update?

Alex
Comment 4 Erno Mononen 2008-02-07 22:28:43 UTC
Right, that's probably the case with a rails update. I couldn't reproduce though, from which version did you upgrade to 
2.0.2?
Comment 5 algnod 2008-02-07 22:39:13 UTC
The original bug was in daily build netbeans-6.1-200801220000 and here I upgraded from 1.2.x? or whatever version of
rails was part of the download. Rails 2.x only came with a later daily build and I did not have that problem then.
Comment 6 Erno Mononen 2008-09-30 17:05:11 UTC
Adjusting the priority since this shouldn't happen that often.