Skip to content

rule's "scalacopts" should get higher priority than toolchain "scalacopts" #382

Open
@or-shachar

Description

@or-shachar

In scalacopts there are some options that can be overridden by their last occurrance and some options that are aggregated

We need a test that makes sure that options that come from library rule scalacopts comes after any option that comes from toolchain's scalacopts

On #364 I did not add such test and I think it should be added.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions