[ 
https://issues.apache.org/jira/browse/MEECROWAVE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Struberg resolved MEECROWAVE-323.
--------------------------------------
    Fix Version/s: 2.0.0
         Assignee: Mark Struberg
       Resolution: Fixed

this is resolved in MW-2.0.0

> Incorrect filename for annotation processor
> -------------------------------------------
>
>                 Key: MEECROWAVE-323
>                 URL: https://issues.apache.org/jira/browse/MEECROWAVE-323
>             Project: Meecrowave
>          Issue Type: Bug
>    Affects Versions: 1.2.14
>         Environment: Java 17
>            Reporter: Vladimir V. Bychkov
>            Assignee: Mark Struberg
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> Dependency artifact 
> [meecrowave-core:1.2.14:jakarta|https://repo1.maven.org/maven2/org/apache/meecrowave/meecrowave-core/1.2.14/meecrowave-core-1.2.14-jakarta.jar]
>  contains file /META-INF/services/*jakarta*.annotation.processing.Processor. 
> The name of file si incorrect: this file is not a part of Jakarta EE, but 
> part of Java EE. His name since JDK 6 was und stays 
> *javax*.annotation.processing.Processor.
> This error is name is a blocker: when build with maven-compiler it produces 
> error
> {code}
> Caused by: org.apache.maven.plugin.compiler.CompilationFailureException: 
> Compilation failure error: Bad service configuration file, or exception 
> thrown while constructing Processor object: 
> jakarta/annotation/processing/AbstractProcessor
>         at 
> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1310)
>         at 
> org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:183)
>         at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
>         at 
> org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2(MojoExecutor.java:370)
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to