Okay...backing out updates, I hink it may be due to usage of
<dependency>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>4.0.0-M4</version>
<type>maven-plugin</type>
</dependency>
4.0.0-M3 seemed to work but then M4 seemed to start breaking things.
Any idea why this upgrade may break things with the nbm-maven-plugin:4.8?
Or are there some other dependencies mayb not referenced in the pom file?
Eric Bresie
ebre...@gmail.com
On Sun, Apr 2, 2023 at 11:18 AM Eric Bresie <ebre...@gmail.com> wrote:
>
> Trying to update my maven dependency plugins and when I've updated all of
> them, I've get build failures like
>
> Failed to execute goal
>> org.apache.netbeans.utilities:nbm-maven-plugin:4.8:manifest
>> (default-manifest) on project python4nb:
>> Uncategorized problems with NetBeans dependency verification (maybe
>> MNBMODULE-102 or wrong maven dependency metadata).
>> Supposedly external classes are used in the project's binaries but the
>> classes are not found on classpath.
>> Class usages: [
>> com.github.luben.zstd.ZstdInputStream,
>> org.jetbrains.annotations.Contract,
>> org.jetbrains.annotations.Nullable,
>> com.github.luben.zstd.BufferPool,
>> com.github.luben.zstd.ZstdOutputStream,
>
>
>
>> org.jetbrains.annotations.NotNull] -> [Help 1]
>> To see the full stack trace of the errors, re-run Maven with the -e
>> switch.
>> Re-run Maven using the -X switch to enable full debug logging.For more
>> information about the errors and possible solutions, please read the
>> following articles:
>> [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
>
> This seems similar to what was described previously for 4.2 version of
> https://lists.apache.org/thread/sm6qc78mgbn271mdy9pnbbs9dzp8b6m5
> But if I do <verifyRuntime>false</verifyRuntime> the nbm-maven-plugin
> appears to no longer recognize this tag.
>
> Any ideas?
>
> Eric Bresie
> ebre...@gmail.com
>
