git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[jira] [Closed] (DAFFODIL-1913) Strange jar ends up in lib_managed of daffodil - trips up Eclipse IDE users


     [ https://issues.apache.org/jira/browse/DAFFODIL-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Thompson closed DAFFODIL-1913.
-----------------------------------

Pulled the latest updates from the incubator-daffodil repository and verified the updates included the specified commit, ba5b94a5795e242502740a1f99f8ea5240eb874e.

Verified by review of source files associated with this update.

> Strange jar ends up in lib_managed of daffodil - trips up Eclipse IDE users
> ---------------------------------------------------------------------------
>
>                 Key: DAFFODIL-1913
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1913
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: 2.1.0
>            Reporter: Michael Beckerle
>            Assignee: Dave Thompson
>            Priority: Major
>             Fix For: 2.1.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)