On Tue, 11 Mar 2008, Andi Vajda wrote:
If you specify "--classpath Foo.jar" to JCC, it will use the classes
in the jar file to "link" against, but won't stub them unless
explicitly asked to. If you use the "--jar Foo.jar" argument instead,
it does three things: uses the jar file to "link" against, copies the
jar file to the extension bundle, and generates stubs for each class
found in the jar file (unless explicitly told not to).
Each _public_ class, not each class. This can make a big difference.
I'd like to be able to specify a jar file that would be part of the
classpath, and included in the bundle, but not automatically stubbed.
I see, like --include this.jar --include that.jar, no wrappers but know about
them and copy them. Easy enough.
How about this patch ?
Andi..
Index: jcc/cpp.py
===================================================================
--- jcc/cpp.py (revision 394)
+++ jcc/cpp.py (working copy)
@@ -268,6 +268,10 @@
classpath.append(args[i])
classNames.update(expandjar(args[i]))
jars.append(args[i])
+ elif arg == '--include':
+ i += 1
+ classpath.append(args[i])
+ jars.append(args[i])
elif arg == '--package':
i += 1
packages.add(args[i])
_______________________________________________
pylucene-dev mailing list
[email protected]
http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
