|
||||||||
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)
Just a few thoughts, not tried out so far:
Effectively the complex classpath is needed neither by your plugin nor by the user's application, but solely by DITA-OT which is a dependency. Hence, provide the default classpath for DITA-OT in your plugin's POM in a <dependencies> section private to the DITA-OT dependency:
<build>
<plugins>
<plugin>
<groupId>com.github.dita-ot</groupId>
<artifactId>dita-ot-minimal</artifactId>
<version>1.8</version>
...
<dependencies>
...(complex classpath here)...
</dependencies>
</plugin>
</plugins>
</build>
To override it later, it should be enough to have a profile here, or let the user configure change the classpath using a dependency management section.