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: | integrated freemarker is an incomplete re-packaged freemarker 2.3.8 distribution | ||
|---|---|---|---|
| Product: | platform | Reporter: | Viktor Lapitski <lvv> |
| Component: | Data Systems | Assignee: | Jaroslav Tulach <jtulach> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | blocker | CC: | tspiva |
| Priority: | P1 | ||
| Version: | 5.x | ||
| Hardware: | Sun | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | |||
| Bug Blocks: | 99404 | ||
|
Description
Viktor Lapitski
2007-04-03 21:41:35 UTC
Yes, I know. I did it to minimize the amount of broken links as original freemarker jar depens on a lot of libraries that are not present in NetBeans at all. Please write me a testcase to demonstrate what API you are using and reopen. I'll extend the current filter. Hopefully I will not need to include everything... i'm using API documented at the freemarker site. And if something of the API isn't used now i might use it later. How did you verify that your version do support the whole API? Obviuosly it doesn't. Then, where is the documentation of what your version supports? Until that documentation provided this bug can't be closed. You need to be more concrete about things that do not work. List of excludes is here: http://www.netbeans.org/source/browse/libs/freemarker/build.xml and as far as I can tell it contains classes that would not be loadable into VM anyway - e.g. Rhino, Log4J, Jython, servlet... The list can of course be modified, if there is a reason. So far the biggest concern has been the size of the list of warnings printed in verify-class-linkage step of ant -f libs/freemarker/build.xml |