-
Notifications
You must be signed in to change notification settings - Fork 4
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
The first part of the alias is invalid jeo.seq.of2
#127
Comments
@yegor256 Could you help with it, please? |
@volodya-lombrozo unfortunately, we don't publish documentation for every lint, but we have it, check this page: https://github.com/objectionary/lints/blob/master/src/main/resources/org/eolang/motives/aliases/broken-alias-first.md It seems, the way you format |
@yegor256 Can you please connect the documentation with a failure message, please? It will help to mitigate issues. |
@yegor256 Moreover, the documentation you sent doesn't help. I'm getting the same error for the following [ERROR] <metas>
[ERROR] <meta>
[ERROR] <head>package</head>
[ERROR] <tail>j$org.j$eolang.j$hone.j$param</tail>
[ERROR] <part>j$org.j$eolang.j$hone.j$param</part>
[ERROR] </meta>
[ERROR] <meta>
[ERROR] <head>alias</head>
[ERROR] <tail>seq.of2 jeo.seq.of2</tail>
[ERROR] <part>jeo.seq.of2</part>
[ERROR] <part>seq.of2</part>
[ERROR] </meta>
[ERROR] <meta>
[ERROR] <head>alias</head>
[ERROR] <tail>seq.of0 jeo.seq.of0</tail>
[ERROR] <part>jeo.seq.of0</part>
[ERROR] <part>seq.of0</part>
[ERROR] </meta>
[ERROR] <meta>
[ERROR] <head>alias</head>
[ERROR] <tail>seq.of1 jeo.seq.of1</tail>
[ERROR] <part>jeo.seq.of1</part>
[ERROR] <part>seq.of1</part>
[ERROR] </meta>
[ERROR] <meta>
[ERROR] <head>alias</head>
[ERROR] <tail>method jeo.method</tail>
[ERROR] <part>jeo.method</part>
[ERROR] <part>method</part>
[ERROR] </meta>
[ERROR] <meta>
[ERROR] <head>alias</head>
[ERROR] <tail>params jeo.params</tail>
[ERROR] <part>jeo.params</part>
[ERROR] <part>params</part>
[ERROR] </meta>
[ERROR] <meta>
[ERROR] <head>alias</head>
[ERROR] <tail>int jeo.int</tail>
[ERROR] <part>jeo.int</part>
[ERROR] <part>int</part>
[ERROR] </meta>
[ERROR] <meta>
[ERROR] <head>alias</head>
[ERROR] <tail>annotation-property jeo.annotation-property</tail>
[ERROR] <part>jeo.annotation-property</part>
[ERROR] <part>annotation-property</part>
[ERROR] </meta>
[ERROR] <meta>
[ERROR] <head>alias</head>
[ERROR] <tail>bool jeo.bool</tail>
[ERROR] <part>jeo.bool</part>
[ERROR] <part>bool</part>
[ERROR] </meta>
[ERROR] <meta>
[ERROR] <head>alias</head>
[ERROR] <tail>class jeo.class</tail>
[ERROR] <part>jeo.class</part>
[ERROR] <part>class</part>
[ERROR] </meta>
[ERROR] <meta>
[ERROR] <head>alias</head>
[ERROR] <tail>annotation jeo.annotation</tail>
[ERROR] <part>jeo.annotation</part>
[ERROR] <part>annotation</part>
[ERROR] </meta>
[ERROR] <meta>
[ERROR] <head>alias</head>
[ERROR] <tail>maxs jeo.maxs</tail>
[ERROR] <part>jeo.maxs</part>
[ERROR] <part>maxs</part>
[ERROR] </meta>
[ERROR] </metas> Please, help. It's still a blocker. |
The order of |
@volodya-lombrozo should be this:
This will be similar to this EO code (which is correct):
On a side note, I don't think you need this meta at all, since you use FQN in the |
@yegor256 It's a requirement from you objectionary/jeo-maven-plugin#883 |
@volodya-lombrozo it seems, I was wrong, sorry. Once the value of @maxonfjvipon please, confirm this |
@yegor256 It seems that yes, you need alias only for the first object in dispatches chain:
|
@maxonfjvipon So, I can hardcode: <meta>
<head>alias</head>
<tail>jeo org.eolang</tail>
<part>jeo</part>
<part>org.eolang</part>
</meta> Or what? |
@volodya-lombrozo you don't need any |
@volodya-lombrozo does it work without |
@yegor256 I can't say anything before this PR is merged: objectionary/jeo-maven-plugin#942 |
@yegor256 Thank you for your suggestion! Removing meta elements seems to have resolved the issue. |
I'm getting this error:
When use the following java code:
This significantly blocks the development.
Please fix the plugin by providing a human-readable message with the actions I need to take to resolve the problem.
The text was updated successfully, but these errors were encountered: