[
http://jira.codehaus.org/browse/MSQL-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241542#action_241542
]
H.-C. Gürsoy commented on MSQL-65:
----------------------------------
Hi Dan, Robert,
just only for the records...
I don't want to execute a specific execution-block by an Id.
Example: you have a database setup in two steps. In the first step (execution
block one), the database user dropped and created by a sys, in the next step,
the tables and indices are created by the new user.
Looking a bit around IMHO it's the same Bug as described in
http://jira.codehaus.org/browse/MNG-3401 reported some years ago, regarding the
Maven core and described by me in an another context
(http://jira.codehaus.org/browse/MNG-3425). Too long ago to remember ad hoc ;-)
> username and password configuration is ignored if configured in execution and
> triggered by sql:execute
> ------------------------------------------------------------------------------------------------------
>
> Key: MSQL-65
> URL: http://jira.codehaus.org/browse/MSQL-65
> Project: Maven 2.x SQL Plugin
> Issue Type: Bug
> Affects Versions: 1.4
> Environment: SUN JDK 1.6 u20 on Windows 7 (64bit) and Linux (Ubuntu
> 10.10, 32bit)
> Maven 2.1.1
> Reporter: H.-C. Gürsoy
>
> Description:
> - the plugin has multiple executions
> - the username and password is configured for each execution individual in
> it's configuration
> - they are not bound to a phase
> - the execution is triggered by mvn sql:execute
> In this case, the username / password configurations in the executions are
> ignored!
> This is not that I would expect.
> If I configure the username / password in the global configuration of the
> plugin, these are used.
> If I bound the executions to a phase (the same or different), the username /
> password configurations in the executions are not ignored, then I trigger the
> plugin through the lifecycle (e.g. bound all executions to install, executing
> "mvn clean install").
> I've not tested all, but for example the url configuration behaves as I would
> expect (configurations in the executions are used).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
