the sonar maven plugin must be executed on the same host than the server because derby listens only on 127.0.0.1.
The first step is to add the following properties to conf/derby.properties :
#####
- Uncomment the two following properties if the embedded database is derby and if
- the sonar maven plugin is executed on a different host than the server.
- By default the Derby Network Server will only listen on the loopback address.
#####
#derby.drda.host=0.0.0.0
#derby.drda.portNumber=1527
The problem is now to configure the security policy : http://db.apache.org/derby/docs/dev/adminguide/tadminnetservcustom.html
Improvement
Closed
Major
The Derby embedded database listens only on the loopback interface
Derby should be used only for test/demo purposes. So this Derby limitation is a good thing, it enforces to use another database for production use. It will not be fixed.