Yep, still not working as in the past.
So here goes my fundamental question: is it a bug or a feature (http://
globalnerdy.com/wordpress/wp-content/uploads/2007/12/
bug_vs_feature.gif)?
Please answer!
On 4 Gru, 00:50, MarkH markh.ne...@gmail.com wrote:
I'm still having Eclipse console logging
I'm still having Eclipse console logging issues with 1.4.0. (OSX10.6.5/
Helios).
I tried the following:
1. Used the Eclipse plugin to generate a new GWT/AppEngine app.
2. Added a java.util.logging.Logger to the GreetingServiceImpl
3. Added logger.fine(test); to the greetServer call
4. set
I changed the GWT log level to TRACE solving partially the problem, infact
now I have very verbose logs.
On Wed, Nov 3, 2010 at 15:33, Rajeev Dayal rda...@google.com wrote:
No, I did not mean dropping it there - I meant changing it in the Web App
Launch Configuration UI - edit your launch
We're going to fix this for the App Engine 1.4.0 release. What we'll do is
have messages at Log.INFO level be outputted when you've got your Launch
Configuration's log level set to INFO.
In the Google Plugin for Eclipse, we'll make a change such that any new
launch configurations created have a
Thanks, I'll wait for 1.4.0.
On Thu, Nov 4, 2010 at 16:33, Rajeev Dayal rda...@google.com wrote:
We're going to fix this for the App Engine 1.4.0 release. What we'll do is
have messages at Log.INFO level be outputted when you've got your Launch
Configuration's log level set to INFO.
In the
Logged issue http://code.google.com/p/googleappengine/issues/detail?id=4011
On Thu, Nov 4, 2010 at 11:33 AM, Rajeev Dayal rda...@google.com wrote:
We're going to fix this for the App Engine 1.4.0 release. What we'll do is
have messages at Log.INFO level be outputted when you've got your Launch
I also have this problem. In addition, it seams that the new 1.3.8
version does not recognize the 1.3.7 local_db.bin development mode
datastore (if i switch back it's ok)
On Nov 3, 4:38 am, timzon jerome.bre...@gmail.com wrote:
Dropping default log level (.level) to TRACE, INFO or FINEST doesn't
No, I did not mean dropping it there - I meant changing it in the Web App
Launch Configuration UI - edit your launch configuration (in Eclipse), and
set the log level to TRACE. Does that help?
On Tue, Nov 2, 2010 at 10:38 PM, timzon jerome.bre...@gmail.com wrote:
Dropping default log level
Dropping default log level (.level) to TRACE, INFO or FINEST doesn't
fix the problem.
log.info (with default INFO level) used to work before 1.3.8 upgrade
and doesn't work after the upgrade.
On Oct 29, 2:49 pm, Rajeev Dayal rda...@google.com wrote:
Drop you launch configuration's log level down
Same problem.
Issue logged: http://code.google.com/p/googleappengine/issues/detail?id=3969
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe
Starred the issue:
http://code.google.com/p/googleappengine/issues/detail?id=3969
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this
Drop you launch configuration's log level down to TRACE. Do you see the
messages now?
On Fri, Oct 29, 2010 at 1:23 PM, John Bito j...@bobberinteractive.comwrote:
Starred the issue:
http://code.google.com/p/googleappengine/issues/detail?id=3969
--
You received this message because you are
Hi,
is anyone from App Engine team is aware of this?
I can raise new issue in the bugtracer (http://code.google.com/p/
googleappengine/issues/list) but at this moment AppEngine has 1596
registered defects. Is there a point in registering another one, maybe
you could fix this skipping the red tape?
Same problem for me.
Any solution?
On 27 oct, 02:03, Raymond dslam2...@gmail.com wrote:
I'm facing the same issue too.
On Oct 26, 11:47 am, Dan Dubois uvico...@gmail.com wrote: I am getting the
same problem but still on GWT 2.0.3. It must be an
app engine java dev server problem.
On
I am getting the same problem but still on GWT 2.0.3. It must be an
app engine java dev server problem.
On Oct 25, 6:04 am, vvorski vic...@vorski.com wrote:
Same here with python on a Mac. Have heard reports of same with Java
on windows. Seems to be a global1.3.8problem?
V/.
On Oct 24, 9:04
Similar here.
Now only logs WARNING and ERROR.
Logging properties set to INFO and prior to 1.3.8 upgrade INFO logged
fine.
Have configuration procedures been changed or something?
Window 7 32bit
Eclipse 3.5 and 3.6
--
You received this message because you are subscribed to the Google Groups
I am seeing the same problem but thought is was due to new GWT 2.1RC1
logging capability.
See thread at
http://groups.google.com/group/google-web-toolkit/browse_frm/thread/c5afa6655edec800#
I just tested my app with 1.3.7 and .8. With .7 it works and not with .
8. I am only testing on the
Same here with python on a Mac. Have heard reports of same with Java
on windows. Seems to be a global 1.3.8 problem?
V/.
On Oct 24, 9:04 pm, jt john.j.tho...@gmail.com wrote:
Hello,
I upgraded my project from 1.3.4 to 1.3.8. After the upgrade, the
console fails to log. If I switch back to
18 matches
Mail list logo
