[
https://issues.apache.org/jira/browse/XMLBEANS-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17584933#comment-17584933
]
PJ Fanning commented on XMLBEANS-626:
-------------------------------------
See
https://github.com/apache/xmlbeans/commit/382fd47d26d06a4fb75707b0787449bda5473896
> Interface extensions need explicit dependency on javaparser-symbol-solver-core
> ------------------------------------------------------------------------------
>
> Key: XMLBEANS-626
> URL: https://issues.apache.org/jira/browse/XMLBEANS-626
> Project: XMLBeans
> Issue Type: Bug
> Components: Binding
> Affects Versions: Version 5.1.1
> Reporter: Peter Keller
> Priority: Minor
> Fix For: Version 5.1.2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Tidying up the dependencies for my XMLBeans-consuming project, I find that I
> need to specify an explicit dependency on
> {{{}com.github.javaparser:javaparser-symbol-solver-core{}}}, or the interface
> extension generation step fails with:
> {{> java.lang.NoClassDefFoundError:
> com/github/javaparser/symbolsolver/model/resolution/TypeSolver}}
> For context, I am building with Gradle, and defining the Ant schema
> compilation task as follows:
> {{ant.taskdef (}}
> {{ name: "xmlbean",}}
> {{ classname: "org.apache.xmlbeans.impl.tool.XMLBean",}}
> {{ classpath: configurations.xbeanconf.asPath}}
> {{)}}
> It is the {{classpath}} in the above snippet that needs
> {{{}javaparser-symbol-solver-core{}}}, and it is not pulled in as a
> transitive dependency from anywhere so I have to declare a dependency on it
> myself.
> Is this intended? Or should {{javaparser-symbol-solver-core}} be considered
> for inclusion as a dependency of xmlbeans itself? Or should I be doing this
> differently?
> Any hints appreciated.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
