Repository navigation
Xalan from Stanford kills Java cups #56
Description
Activity
@mssammon @danyaljj @YimingJiang FYI (I won't be able to tackle this right now)
could we make stanford an optional dependency?
For some projects that actually require the dep/const parser that's not really an option.
For me excluding stanford from the pipeline at the time of generating the lbjava files did the trick:
<dependency> <groupId>edu.illinois.cs.cogcomp</groupId> <artifactId>illinois-nlp-pipeline</artifactId> <version>${cogcomp-nlp-version}</version> <exclusions> <exclusion> <groupId>edu.stanford.nlp</groupId> <artifactId>stanford-corenlp</artifactId> </exclusion> </exclusions> </dependency>
When I import core-utils and lbjava in the same project, java cups breaks down and cannot work.
The reason behind this is core-utils brings stanford corenlp which in turn brings xalan jar.
Xalan and java cups do not go well.