git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[jira] [Resolved] (DAFFODIL-1430) macroLib should not be needed after scala compilation, but seems to be required


     [ https://issues.apache.org/jira/browse/DAFFODIL-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Lawrence resolved DAFFODIL-1430.
--------------------------------------
       Resolution: Duplicate
    Fix Version/s:     (was: deferred)
                   2.2.0

Fixed as part of DAFFODIL-1857. Marking as a duplicate.

> macroLib should not be needed after scala compilation, but seems to be required
> -------------------------------------------------------------------------------
>
>                 Key: DAFFODIL-1430
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1430
>             Project: Daffodil
>          Issue Type: Improvement
>          Components: Infrastructure
>            Reporter: Michael Beckerle
>            Priority: Major
>             Fix For: 2.2.0
>
>
> We now have this new daffodil-macro-lib module. 
> In the projects/build.scala, it is *not* listed as "nopub". It seems to be needed to be published, but I don't know why it would be needed.
> In creating a scala build for a data format (where the jar created contains the DFDL schema, and can run TDML tests), there is a dependency on the daffodil-tdml library, and this transitively ends up requiring the macroLib, so fails if the projects/build.scala is changed so that macroLib is "nopub".
> So the task here is figure out why, so that macroLib truly is only needed at scala-compile time for daffodil, and not needed when other consumers of daffodil libraries are used.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)