`eo-maven-plugin` allows attributes without names in an abstract object

[volodya-lombrozo]

The current version of eo-maven-plugin allows to declare attributes without names in abstract objects.

new-KClW ↦ ⟦
  Φ.org.eolang.int(
    α0 ↦ Φ.org.eolang.bytes(
      Δ ⤍ 00-00-00-00-00-00-00-00
    )
  )
⟧

new-KClW is an abstract object (as far as I know,) and the Φ.org.eolang.int is its attribute without a name. When I run xmir -> 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:

<plugin>
  <groupId>org.eolang</groupId>
  <artifactId>eo-maven-plugin</artifactId>
  <version>0.38.4</version>
  <executions>
    <execution>
      <id>convert-xmir-to-phi</id>
      <phase>process-classes</phase>
      <goals>
        <goal>xmir-to-phi</goal>
      </goals>
      <configuration>
        <phiInputDir>${project.build.directory}/generated-sources/opeo-decompile-modified-xmir</phiInputDir>
        <phiOutputDir>${project.build.directory}/generated-sources/phi-expressions</phiOutputDir>
      </configuration>
    </execution>
  </executions>
</plugin>

[volodya-lombrozo]

@maxonfjvipon Could you take a look please?

[github-actions[bot]]

@volodya-lombrozo thanks for the report, here is a feedback:

Problems

• The bug report is missing several crucial elements, reducing its effectiveness.
• The title of the report is too broad and doesn't provide a succinct summary of the specific issue at hand.
• The report fails to include the steps needed to replicate the problem, a necessary detail for developers to understand the issue thoroughly.

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. Analyzed with gpt-4

[volodya-lombrozo]

@yegor256 Could you release a new version, please?

[yegor256]

@rultor release, tag is 0.39.0

[rultor]

@rultor release, tag is 0.39.0

@yegor256 OK, I will release it now. Please check the progress here

[rultor]

@rultor release, tag is 0.39.0

@yegor256 Done! FYI, the full log is here (took me 14min)

[yegor256]

@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.

[volodya-lombrozo]

@maxonfjvipon How can I use the new version?

[yegor256]

@volodya-lombrozo just change the version in the pom.xml. It doesn't work? Maybe it's better to report a new ticket, if it doesn't.

[volodya-lombrozo]

@yegor256 Yes, changing version helps. Thank you.