Just to update this thread quick...
The error is occurs mostly because the perm size is filling up or the
loading of a specific class is causing the ClassLoader to error out.
This the primary reason why I added the exclusions list. The other
reason is that scanning the entire classpath and loading every class
into the JVM in any action package could take a long time.
I recall some work to change things to use ASM rather than loading the
class into the JVM. This work should have reduced the need for
exclusions almost completely since the class isn't actually loaded
into the JVM at all. The byte code is parsed by ASM instead.
-bp
On Jul 15, 2008, at 9:19 AM, Musachy Barroso wrote:
I did use Toplink Essentials and in its jar there is a package
called "persistence.antlr.actions". So the locators matched. Don't
know why
it comes to an error, but I think it is the same reason Brian
excluded
hibernate and some other packages by default.
Yes, that could be tricky, yet the plugin should just be log it as an
error and move on, I get a few of those when running in eclipse.
musachy
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
