-
Notifications
You must be signed in to change notification settings - Fork 147
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
eo-maven-plugin
allows attributes without names in an abstract object
#3294
Comments
@maxonfjvipon Could you take a look please? |
@volodya-lombrozo thanks for the report, here is a feedback: Problems
I would recommend adding a 'Steps to Reproduce' section to help developers recreate the issue on their end. Please fix the bug report in order it to get resolved faster. |
fix(#3294): added `PhiMojo` fails on error flag
@yegor256 Could you release a new version, please? |
@rultor release, tag is |
@maxonfjvipon the problem in rultor was, as expected, in the size of the machine. Now, we are using AWS t2.xlarge and it all works. |
@maxonfjvipon How can I use the new version? |
@volodya-lombrozo just change the version in the |
@yegor256 Yes, changing version helps. Thank you. |
The current version of
eo-maven-plugin
allows to declare attributes without names in abstract objects.new-KClW
is an abstract object (as far as I know,) and theΦ.org.eolang.int
is its attribute without a name. When I runxmir
->phi
transformation, I don't see any errors, but I should. Attributes in abstract objects must have names.If we ignore this issue, we will face with such errors.
I use the fooling plugin configuration in the project:
The text was updated successfully, but these errors were encountered: