Hi,
Another way to handle this would be to create a separate logging.properties
file, and then add the following to your launch configuration:
-Djava.util.logging.config.file=/path/to/test/logging.properties ...
This would be cleaner than modifying your code.
Rajeev
On Tue, Sep 8, 2009 at 7:2
The root problem unsurprisingly turns out to be logging configuration.
Stop this from happening by setting the following DataNucleus loggers
PRIOR to your JDOHelper.getPersistenceManagerFactory() calls:
//This one caused all the WARNING and SEVERE logs about eclipse UI
elements
Logger.getLogger
I just found out that it all gets spammed as a response to
JDOHelper.getPersistenceManagerFactory(). It only happens when running
the Local Service implementation as specified on the AppEngine wiki
On Sep 8, 3:34 pm, Erem wrote:
> Hi Rajeev,
>
> Thanks for the response! It's a normal JUnit launc
Hi Rajeev,
Thanks for the response! It's a normal JUnit launch config.
There are only 2 classpath entries in my launch config:
---
v Bootstrap Entries
JRE System Library [jre1.6.0_15 - 32-bit[
v User Entries
> MyProject (default classpath)
I still can't figure it out how to sh
Hi,
Is this a normal JUnit Launch Configuration, or is there a special plugin
that you're using?
Can you navigate to the launch configuration's classpath tab and list out
the entries?
Thanks,
Rajeev
On Wed, Aug 26, 2009 at 4:58 PM, Amendmen7 wrote:
>
> I'm having the same issues. I have tri
I'm having the same issues. I have tried turning off all known loggers
in the setUp methods of my LocalDatastoreTestCase superclass, but it
has no effect re: this logspam!
Has anyone found an answer?
On Aug 5, 8:41 am, Stephan wrote:
> I'm having the same problem here. Using a fresh eclipse ins
