You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #198, the year in the XML namespace for the Orchestra XML schemas was changed from 2020 to 2023, for example, http://fixprotocol.io/2023/orchestra/repository to http://fixprotocol.io/2023/orchestra/repository. Java code generated from these schemas is given a package name derived from the namespace, but in the same PR the code references were updated to "2022" rather than "2023".
The solution is to update these package name references to reflect "2023" rather than "2022".
Example error output:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project interfaces: Compilation failure
[ERROR] /Users/plucas/dev/oss/fix/fix-orchestra/interfaces/src/main/java/module-info.java:[5,41] package is empty or does not exist: io.fixprotocol._2022.orchestra.interfaces
The text was updated successfully, but these errors were encountered:
patricklucas
added a commit
to patricklucas/fix-orchestra
that referenced
this issue
Aug 28, 2024
In #198, the year in the XML namespace for the Orchestra XML schemas was changed from 2020 to 2023, for example,
http://fixprotocol.io/2023/orchestra/repository
tohttp://fixprotocol.io/2023/orchestra/repository
. Java code generated from these schemas is given a package name derived from the namespace, but in the same PR the code references were updated to "2022" rather than "2023".The solution is to update these package name references to reflect "2023" rather than "2022".
Example error output:
The text was updated successfully, but these errors were encountered: