Comments for Piraguablog

Comment on Grails Dependency Management – Setting the Ivy Proxy by Peter Ledbrook

Peter Ledbrook — Mon, 21 Jun 2010 07:16:03 +0000

This is fixed in Grails 1.3.2. Also, extra commands were added to make it easy to enable and disable the proxy: add-proxy, remove-proxy, and clear-proxy. The first two deal with named proxy settings (so you can have multiple proxies configured), as does set-proxy now:

grails set-proxy work

Comment on Building Grails Apps with SVN and Hudson and fighting with application.properties by j pimmel

j pimmel — Thu, 28 Jan 2010 06:39:14 +0000

Interesting Mike… We’ve been having some similarly odd issues regarding the grails-app/il8n/messages.properties file.. it get zero-byted by some part of the grails process after initial checkout, so we have a similar shell step in most of our Hudson builds (we stopped using update) where we revert that

svn revert grails/il8n/messages.properties

Comment on Grails Code Coverage Plugin 1.1.4 Released! by Ravi Hasija

Ravi Hasija — Sat, 24 Oct 2009 22:16:56 +0000

Fantastic work guys!!! Great.

I have a question though:

I have a Category class that references itself as a one to many. I have two integration test files. One to test static constraints and one to test the relationship.

Anyway, when I run the test I am getting code coverage for static constraints (as a separate Class file Category$__clinit__closure1) and those lines show up green in the html report, but the lines where hasMany and belongsTo relationship is defined, the code does not show up as green, even though the report shows 100% coverage.

Could you please share your comment. I am new to Grails, so I might be missing something.

Comment on Grails, p6spy and Sql Profiler by j pimmel

j pimmel — Thu, 08 Oct 2009 21:19:05 +0000

I’m trying to get this working in 1.2 and having no luck with the logging output.

The P6Spy shows green and i get the 3 init messages, driverManager; registeredDriver and reloadProperties.

I have logSql=true in my datasource and am seeing the HSQl dumping to console as i use the app. No SQL statements of further logging appears in P6SPy app os spy.log (they never have)

I followed you examples exactly as above – here is my spy.properties

realdriver=com.mysql.jdbc.Driver
log4j.appender.SQLPROFILER_CLIENT=org.apache.log4j.net.SocketAppender
log4j.appender.SQLPROFILER_CLIENT.RemoteHost=localhost
log4j.appender.SQLPROFILER_CLIENT.Port=4445
log4j.appender.SQLPROFILER_CLIENT.LocationInfo=true
log4j.logger.p6spy=DEBUG,STDOUT,SQLPROFILER_CLIENT

appender=com.p6spy.engine.logging.appender.Log4jLogger

Is there anything that needs to be changed in the log4j config of the app? This is what I have

log4j = {
error ‘grails.app’, ’stdout’, ‘file’
root {
error()
}
additivity = true
}

I also have Grails in Action and nothing in there is helping me resolve this.

When running the app with ‘-Dlog4j.debug=true’ i get the following output

log4j: Trying to find [log4j.xml] using context classloader java.net.URLClassLoader@10f0625.
log4j: Trying to find [log4j.xml] using org.codehaus.groovy.grails.cli.support.GrailsRootLoader@fd13b5 class loader.
log4j: Trying to find [log4j.xml] using ClassLoader.getSystemResource().
log4j: Trying to find [log4j.properties] using context classloader java.net.URLClassLoader@10f0625.
log4j: Using URL [jar:file:/home/jerome/grails/dist/grails-scripts-1.2-M2.jar!/log4j.properties] for automatic log4j configuration.
log4j: Reading configuration from URL jar:file:/home/jerome/grails/dist/grails-scripts-1.2-M2.jar!/log4j.properties
log4j: Parsing for [root] with value=[error, NULL].
log4j: Level token is [error].
log4j: Category root set to ERROR
log4j: Parsing appender named “NULL”.
log4j: Parsed “NULL” options.
log4j: Finished configuring.
No authentication for svn repo at ywRepository …
log4j: setFile called: stacktrace.log, true
log4j: setFile ended
The plugin is disabled therefore nothing needs to be done here.
Running Grails application..
8-Oct-2009 2:18:30 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
8-Oct-2009 2:18:30 PM org.apache.catalina.core.StandardService start
INFO: Starting service Tomcat
8-Oct-2009 2:18:30 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0-snapshot
8-Oct-2009 2:18:30 PM org.apache.catalina.startup.ContextConfig defaultWebConfig
INFO: No default web.xml
8-Oct-2009 2:18:31 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
log4j: Could not find root logger information. Is this OK?
log4j: Parsing for [p6spy] with value=[DEBUG,STDOUT,SQLPROFILER_CLIENT].
log4j: Level token is [DEBUG].
log4j: Category p6spy set to DEBUG
log4j: Parsing appender named “STDOUT”.
log4j:ERROR Could not find value for key log4j.appender.STDOUT
log4j:ERROR Could not instantiate appender named “STDOUT”.
log4j: Parsing appender named “SQLPROFILER_CLIENT”.
log4j: Setting property [port] to [4445].
log4j: Setting property [locationInfo] to [true].
log4j: Setting property [remoteHost] to [localhost].
log4j: Parsed “SQLPROFILER_CLIENT” options.
log4j: Handling log4j.additivity.p6spy=[null]
log4j: Finished configuring.
Server running. Browse to http://localhost:8080/imt-grails-webapp

Comment on Grails, p6spy and Sql Profiler by Ted Naleid » Batch Import Performance with Grails and MySQL

Ted Naleid » Batch Import Performance with Grails and MySQL — Thu, 01 Oct 2009 05:53:54 +0000

[...] Mike Hugo has a great post on using the p6spy plugin with the JDBC SQL profiler. [...]