[
https://jira.codehaus.org/browse/MOJO-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=299029#comment-299029
]
Sander Verhagen edited comment on MOJO-1534 at 5/17/12 12:31 PM:
-----------------------------------------------------------------
MOJO-1847 may be slightly related. In that one I was already wondering out-loud
why the compile classpath was added to begin with? Perhaps that's a pre-1.5.4
requirement? I am running a patch without the compile classpath being added to
Ant, and that works as a charm.
was (Author: sverhagen):
MOJO-1847 may be slightly related. I that one I was already wondering
out-loud why the compile classpath was added to begin with? Perhaps that's a
pre-1.5.4 requirement? I am running a patch without the compile classpath being
added to Ant, and that works as a charm.
> dita-maven-plugin should not use the project compile classpath to construct
> ant classpath
> -----------------------------------------------------------------------------------------
>
> Key: MOJO-1534
> URL: https://jira.codehaus.org/browse/MOJO-1534
> Project: Mojo
> Issue Type: Improvement
> Components: dita
> Reporter: Brett Porter
> Assignee: Dan Tran
>
> the plugin currently uses the ugly recommendation of an "optional" compile
> dependency so that they are not passed on to other projects, but can be
> obtained. It would be better that the plugin uses the plugin dependency
> classpath to construct the DITA classpath.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.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
