|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [mojo-dev] [jira] (MDITA-11) Hide the required dependen... Dan Tran (JIRA)
- [mojo-dev] [jira] (MDITA-11) Hide the required dep... Dan Tran (JIRA)
- [mojo-dev] [jira] (MDITA-11) Hide the required dep... Markus KARG (JIRA)
- [mojo-dev] [jira] (MDITA-11) Hide the required dep... Dan Tran (JIRA)
- [mojo-dev] [jira] (MDITA-11) Hide the required dep... Markus KARG (JIRA)
- [mojo-dev] [jira] (MDITA-11) Hide the required dep... Dan Tran (JIRA)
- [mojo-dev] [jira] (MDITA-11) Hide the required dep... Dan Tran (JIRA)
- [mojo-dev] [jira] (MDITA-11) Hide the required dep... Dan Tran (JIRA)
I am not able to digest your suggestion.
However, I think the correction solution to add an addition configuration into ditaot-maven-plugin called <dependencies> which has the same semantic of maven <dependencies>
for example
<execution>
<configuration>
<dependencies>
<dependency>
[....]
This way we can have a exact default, or user can add his/her own. However, this increases the complexity of the plugin implementation itself to code up dependency handling which is not trivial ( this is maven job, not plugin job)