[
http://jira.codehaus.org/browse/MSQL-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202478#action_202478
]
Benjamin Bentmann commented on MSQL-46:
---------------------------------------
Just to have it mentioned: An alternative solution to the current
forceMojoExecution option, could be
{code:java}
/** @parameter */
private Boolean skip;
{code}
where in the case of {{skip == null}} the plugin would dynamically derive the
default value based on the project packaging, i.e. {{true}} for
{{packaging==pom}} and {{false}} otherwise.
> the sql-maven-plugin mojos shall not get executed for projets with packaging
> type 'pom'
> ---------------------------------------------------------------------------------------
>
> Key: MSQL-46
> URL: http://jira.codehaus.org/browse/MSQL-46
> Project: Maven 2.x SQL Plugin
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.4
>
>
> If a company has a lot of similar backend projects, they may move the whole
> sql-maven-plugin configuration over to a shared backend/pom.xml which they
> use as parent for all backend projects. This parent project will not have any
> SQL scripts itself, but may like to define common sql executions like a
> 'createtestdata.sql'.
> In this case the sql-maven-plugin currently fails because the sql statements
> usually don't exist in the parent project.
> The solution is to allow skipping the execution of all sql-maven-pluign mojos
> if it gets executed on a project with packaging type 'pom.
--
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
