You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Steve Lawrence (JIRA)" <ji...@apache.org> on 2018/02/14 15:42:00 UTC
[jira] [Commented] (DAFFODIL-1903) Eclipse classpath broken for
daffodil-test and other tests - now must have daffodil-lib-unittest
[ https://issues.apache.org/jira/browse/DAFFODIL-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364295#comment-16364295 ]
Steve Lawrence commented on DAFFODIL-1903:
------------------------------------------
We seem to keep running into bugs with the eclipse classpath/project files falling behind. Would it be worth looking into the sbt-eclipse plugin ([https://github.com/sbt/sbteclipse)] which is supposed to be able to generate eclipse classpath/projects based on the sbt configuration? Or maybe we have a unique configuration that the plugin can't quite handle?
> Eclipse classpath broken for daffodil-test and other tests - now must have daffodil-lib-unittest
> ------------------------------------------------------------------------------------------------
>
> Key: DAFFODIL-1903
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1903
> Project: Daffodil
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: 2.1.0
> Reporter: Michael Beckerle
> Priority: Major
> Fix For: 2.1.0
>
>
> Moving built-in-formats from daffodil-lib to daffodil-lib-unittest breaks many things. Every eclipse project that depended on that file is broken and must have its eclipse classpath modified.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)