[
https://issues.apache.org/jira/browse/DAFFODIL-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson closed DAFFODIL-1983.
-----------------------------------
Verified the specified commit (commit be3b714fab3e01d270b083e8853f821ea2f45fe0)
is included in the latest pull from the incubator-daffodil repository.
Verified by review that changes specified in commit comment were included.
Verified the incubator-daffodil sbt test suites execute successfully.
> 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
> Assignee: Mike Beckerle
> Priority: Minor
> Fix For: 2.7.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
(v8.3.4#803005)
