Skip to content

Incorrect classpath because INCLUDE field in pom file is ignored #85

@adpi2

Description

@adpi2

Describe the bug

This bug originated in scalameta/metals#5807 (comment) and was reported by @PhilDakin and @gerashegalov

When importing this pom file which contains:

                             <resources>
                                <resource>
                                    <directory>${spark.rapids.source.basedir}</directory>
                                    <targetPath>META-INF</targetPath>
                                    <includes>
                                        <!-- The NOTICE will be taken care of by the antrun task below -->
                                        <include>LICENSE</include>
                                        <include>NOTICE</include>
                                    </includes>
                                </resource>
                                <resource>
                                    <directory>${spark.rapids.source.basedir}/python</directory>
                                </resource>
                            </resources>

The entire ${spark.rapids.source.basedir} directory ends up in the classpaths, which shadows other entries.

Expected behavior

It should isolate LICENSE and NOTICE in a different folder and add that folder to the classpath.

Operating system

None

Version of Maven

???

Version of bloop-maven-plugin

2.0.0

Version of Bloop

1.6.0

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