[ 
https://issues.apache.org/jira/browse/FLINK-30426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648004#comment-17648004
 ] 

Sergey Nuyanzin commented on FLINK-30426:
-----------------------------------------

Seems that the reason is update ArchUnit to 1.0.0

There is a breaking change done in 0.23.0 (described at 
[https://github.com/TNG/ArchUnit/releases/tag/v0.23.0)]

After that any rule matching nothing will fail.
Flink-connector-pulsar depends on flink-snapshot and as a result pulls a newer 
version of flink-architecture-tests-test and 
flink-architecture-tests-production which are now built with 1.0.0 ArchUnit. 
And it leads to breaking change mentioned above.

A simple WA is use of {{archRule.failOnEmptyShould=false}} as mentioned in 
release notes.
At the same time it also questionable if there is a need for 
{{ProductionCodeArchitectureRules}} in this connector since there is no any 
{{api}} packages or {{Public}} annotation which is the subject of search for 
some of those rules

> Archunit can't find any tests in Pulsar repository
> --------------------------------------------------
>
>                 Key: FLINK-30426
>                 URL: https://issues.apache.org/jira/browse/FLINK-30426
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Pulsar
>    Affects Versions: pulsar-4.0.0
>            Reporter: Martijn Visser
>            Priority: Blocker
>              Labels: pull-request-available
>
> CI is failing on {{main}} with:
> {code:java}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) 
> on project flink-connector-pulsar: Execution default-test of goal 
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test failed: 
> org.junit.platform.commons.JUnitException: TestEngine with ID 'archunit' 
> failed to discover tests: 'java.lang.Object 
> com.tngtech.archunit.lang.syntax.elements.MethodsThat.areAnnotatedWith(java.lang.Class)'
>  -> [Help 1]
> {code}
> It does work for {{v3.0}} but there's no obvious difference between the two 
> branches that might explain this issue. 



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

Reply via email to