You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Josh Adams (Jira)" <ji...@apache.org> on 2020/05/05 14:21:00 UTC
[jira] [Resolved] (DAFFODIL-2310) Move VariableMap.scala into
runtime1 package
[ https://issues.apache.org/jira/browse/DAFFODIL-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Adams resolved DAFFODIL-2310.
----------------------------------
Assignee: (was: Josh Adams)
Resolution: Fixed
This has been fixed in commit 56fe8fee1af3bb6ba885fcf638e13ceb39fa257b
> Move VariableMap.scala into runtime1 package
> --------------------------------------------
>
> Key: DAFFODIL-2310
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2310
> Project: Daffodil
> Issue Type: Improvement
> Components: Back End, Clean Ups
> Affects Versions: 2.5.0
> Reporter: Mike Beckerle
> Priority: Minor
> Fix For: 3.0.0
>
>
> This file really belongs in the runtime1 package of daffodil-core.
> While at it, it could be renamed to VariableMapFactory.scala, as that's what it defines
> (The VariableMap data structure itself is part of daffodil-runtime1)
>
> This ticket is just a reminder on this issue. Not moving file now, because work is simultaneously ongoing on reimplementing variables, and to preserve diff capability while that is underway, moving files around is discouraged.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)