Currently, the v2 plugin will start java db when you start the app server IF the option is checked.
the v3 plugin doesn't support started java db at all.
In a perfect world... the java db would start IFF there was an app deployed on the server which is going to use it....
The app server would probably need to be 'the one' to do this.
In a less than perfect world, the IDE might be able to make a better guess about when to start the java db, by looking
at the datasources that an app that is being deployed will use... if a CP in the list going to use java db, we may want
to make sure the db is started.
A naive implementation (that extends the driver deployment feature) seems to work... but this probably requires an API
change to do right.