Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
adpi2 opened this issue Aug 6, 2024 · 0 comments
Open

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

adpi2 opened this issue Aug 6, 2024 · 0 comments

Comments

@adpi2
Copy link
Member

adpi2 commented Aug 6, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant