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.
Summary: | Server and port settings in project properties not always noticed | ||
---|---|---|---|
Product: | ruby | Reporter: | Chris Kutler <ckutler> |
Component: | Rails | Assignee: | issues@ruby <issues> |
Status: | NEW --- | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Chris Kutler
2008-07-11 20:53:30 UTC
Yes, the workaround is to stop the server before rerunning. If a server instance is running for a project, the run action will use that automatically. Looks like it should check whether the server configuration has changed and if it has, stop the current server process and start a new one. I think is not a particularly common scenario though, and the workaround is straightforward, so I'm downgrading this to P4. |