You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Mike Beckerle (Jira)" <ji...@apache.org> on 2019/11/08 14:28:00 UTC

[jira] [Commented] (DAFFODIL-1983) Eliminate eclipse classpath maintenance - UpdateEclipseClasspaths - run from sbt

    [ https://issues.apache.org/jira/browse/DAFFODIL-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970232#comment-16970232 ] 

Mike Beckerle commented on DAFFODIL-1983:
-----------------------------------------

This problem is caused by the eclipse-projects subdir, and the split of what are "normal" project modules into a regular and test variant, but only for eclipse for IDE edit-compile-test cycle speed.

It's possible that if we did away with that regular/test split, regular old 'sbt eclipse' (which has been improved) would "do the right thing". Then we could remove the .classpath and .project files from the git repo (via .gitignore), and require users to recreate them or update them 

This is worth doing as an experiment at some point. To see if we can live with just ordinary eclipse project structure instead of this split world which requires all this added hassle.

> Eliminate eclipse classpath maintenance - UpdateEclipseClasspaths - run from sbt
> --------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-1983
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1983
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Infrastructure
>    Affects Versions: 2.2.0
>            Reporter: Mike Beckerle
>            Priority: Major
>
> Every time library versions are updated, the eclipse classpaths in eclipse-projects must be updated. We have a tool to do this, located in daffodil-propgen module, (formerly daffodil-lib), but it requires DAFFODIL_ROOT and so only can be run under eclipse. 
> Not all developers use eclipse, so there's always this two-part change where library versions change, then the eclipse classpaths have to be fixed up to match. 
> Ideally, we would run this tool from sbt when updateClassifiers is run and we would thereby completely eliminate the need to maintain the eclipse classpath files at all.  Every time you sbt clean ; sbt updateClassifiers, you need to refresh all the eclipse projects anyway.
> So the task is to run this from sbt as part of updateClassifiers (perhaps), and eliminate the dependency on DAFFODIL_ROOT. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)