You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@daffodil.apache.org by "Michael Beckerle (JIRA)" <ji...@apache.org> on 2018/08/13 19:19:00 UTC
[jira] [Created] (DAFFODIL-1983) Eliminate eclipse classpath
maintenance - UpdateEclipseClasspaths - run from sbt
Michael Beckerle created DAFFODIL-1983:
------------------------------------------
Summary: 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: Michael Beckerle
Fix For: 2.2.0
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
(v7.6.3#76005)