[
https://issues.jboss.org/browse/AS7-3377?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka edited comment on AS7-3377 at 8/6/12 4:59 PM:
-----------------------------------------------------------
Note that JBoss AS 7 Maven plugin can handle these tasks with goals deploy-driver,
add-datasource, add-xa-datasource:
http://docs.jboss.org/jbossas/7/plugins/maven/latest/examples/complex-exa...
Honza, could you think over if we could use it efficiently instead of manual copying?
(Sorry for late note, I only found about it now :)
was (Author: ozizka):
Note that JBoss AS 7 Maven plugin can handle these tasks with goals deploy-driver,
add-datasource, add-xa-datasource:
http://docs.jboss.org/jbossas/7/plugins/maven/latest/examples/complex-exa...
Honza, could you think over if we could use it efficiently instead of manual copying?
TS: Check how JDBC drivers are copied
-------------------------------------
Key: AS7-3377
URL:
https://issues.jboss.org/browse/AS7-3377
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Honza Brázdil
Fix For: 7.2.0.Alpha1
I created some initial impl, but that copies drivers to deployments/.
The preferred way for TS harness is to create a module, since the other way is easy to do
manually in case if interrest.
What's specially needed to check is that the driver and DB config ends up in all
instances of multi-node modules (cluster, multinode, etc.).
https://community.jboss.org/wiki/DataSourceConfigurationInAS7
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira