Uploaded image for project: 'Daffodil'
  1. Daffodil
  2. DAFFODIL-1430

macroLib should not be needed after scala compilation, but seems to be required

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: 2.2.0
    • Component/s: Infrastructure
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mbeckerle Michael Beckerle
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: