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 102153

Summary:	Exception from RakeProjectHelper when creating Ruby On Rails project from existing sources
Product:	ruby	Reporter:	Jiri Skrivanek <jskrivanek>
Component:	Project	Assignee:	Martin Krauskopf <mkrauskopf>
Status:	VERIFIED FIXED
Severity:	blocker
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:
Bug Depends on:	116803
Bug Blocks:
Attachments:	Stack trace.

Description Jiri Skrivanek 2007-04-23 14:19:49 UTC

Exception is printed to console when creating Ruby On Rails project from
existing sources. To reproduce:

- create a new Ruby On Rails project
- delete this project but don't delete sources
- open New Project wizard and choose Ruby|Ruby On Rails Project from existing
sources
- click Next
- browse for project folder (previously deleted project)
- click Finish and exception is printed to console:

Occurred at: null:-1
Caused: org.xml.sax.SAXParseException: Premature end of file.

Ruby 0.82.0, IDE 20070423-0756, JDK1.5.0_11, WindowsXP.

Comment 1 Jiri Skrivanek 2007-04-23 14:20:36 UTC

Created attachment 41456 [details]
Stack trace.

Comment 2 Jiri Kovalsky 2007-07-03 14:16:00 UTC

Reassigning this issue to newly created 'ruby' component.

Comment 3 Torbjorn Norbye 2007-08-09 22:56:40 UTC

I can reproduce this, but only when I follow your steps and create a new project from a project I had already created
inside NetBeans in the same IDE session.

If I create a Rails project on the command line (using the "rails" command), and then try to import it into the IDE, it
succeeds without an exception. This seems like a more realistic scenario.

Comment 4 Martin Krauskopf 2007-09-26 17:10:09 UTC

Setting TBD - just would like to now the culprit.

Comment 5 Martin Krauskopf 2007-09-27 15:04:18 UTC

Cannot reproduce any more on Linux (supposing Tor was able to reproduce on Mac -> All/All). This might be closely
related to the recently fixed issue 102201 and might be issue 116678. Let me know (reopen) if you are still able to
reproduce. Thanks.

Comment 6 Jiri Skrivanek 2007-10-12 12:39:55 UTC

Verified - cannot reproduce anymore.