Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.1.0
-
None
Description
So I believe this jar is not part of Daffodil, nor called by daffodil. It is used at the time we generate the javadoc for Daffodil. Yet the jar ends up in lib_managed.
./lib_managed/docs/com.typesafe.genjavadoc/genjavadoc-plugin_2.11.8
./lib_managed/docs/com.typesafe.genjavadoc/genjavadoc-plugin_2.11.8/genjavadoc-plugin_2.11.8-0.10-javadoc.jar
./lib_managed/jars/com.typesafe.genjavadoc/genjavadoc-plugin_2.11.8
./lib_managed/jars/com.typesafe.genjavadoc/genjavadoc-plugin_2.11.8/genjavadoc-plugin_2.11.8-0.10.jar
./lib_managed/srcs/com.typesafe.genjavadoc/genjavadoc-plugin_2.11.8
./lib_managed/srcs/com.typesafe.genjavadoc/genjavadoc-plugin_2.11.8/genjavadoc-plugin_2.11.8-0.10-sources.jar
Then when we generate .classpath files for the Eclipse IDE, they contain this library, which is not pulled when you do 'sbt updateClassifiers', but only when you package daffodil-japi I believe.
So why this ends up in lib_managed when other "tools" do not is a mystery.