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: | Adding postgres JDBC driver for JRuby requires geek skills | ||
---|---|---|---|
Product: | ruby | Reporter: | Craig Mcclanahan <craigmcc> |
Component: | Platform | Assignee: | Erno Mononen <emononen> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | davidvc, mkrauskopf |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | Macintosh | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Craig Mcclanahan
2007-12-08 07:37:10 UTC
I believe this is a P2 because (a) the workaround is ugly and (b) PotsgreSQL support is important to Solaris/Database strategy, even though one could argue it's not important because there are few PostgreSQL users. This is something we hope to change, and making PostgreSQL hard to access doesn't encourage that to happen. Note that this issue is not restricted to just adding a Postgres JDBC driver. The same problem occurs if you want to add *any* Java class library in a way that causes it to show up in the classpath seen by JRuby. I'll have a look at this. Related to this is http://wiki.netbeans.org/wiki/view/OutOfBoxVersionabilityProposal. The PostgreSQL drivers (and other JDBC drivers) are now automatically added to the class path, please see http:// wiki.netbeans.org/RubyDatabaseIntegration for more info. Note that a reference to project.properties is only added if the referenced file could be referenced using a relative path, otherwise the reference is put to private.properties - this applies also to any JAR file added through the project customizer. It is still not ideal, but considering all this, I think the issue can be downgraded to P3. I think we can close this once issue 138316 is fixed. Closing now that issue 138316 is fixed, the drivers and active record jdbc adapters for mysql and postgresql are now bundled with the IDE. |