I notice that your github repo is based on 2.1.4-SNAPSHOT while the artifact that the download plugin is looking for has version 3.0.4-SNAPSHOT. Perhaps you have imported some but not all the changes from upstream into your local clone?

I recommend that you pull all upstream changes into your own repo and rebase your fix. As simpler option might be just to reclone the latest upstream repo and re-apply your patch.

I've got the first error [1]. If I fixed the ModuleSystem !param names to be consistent with method parameters I've got to the second error [2] which I'm not able to solve as I do not understand where is the HelpMojo class generated from.

Could it be a problem of only my laptop? Or problem exists just between keyboard and chair?

I don't know how that didn't fail for me when I was writing the code, I've been using OpenJDK 8 too.

Me too. Maybe it depends on the jdk8 version. This is a real problem in the agent module because the parser generator generats code with missing tag values. I have fixed the problem in agent/pom.xml by changing the javadoc plugin settings to switch off checking for missing tags (see BYTEMAN-306). I also worked around the byteman maven rulecheck plugin pom the same way -- the real fix in that code is to correct the javadoc. This problem in the modules code can also be worked around by adding the relevant javadoc plugin config but really just needs the javadoc fixing.

I cannot account for why you are seeing this and I am not since I used exactly the same JDK8 release -- although in my case on Fedora 21.

In any, James' fix to the javadoc tags in the modules plugin is in trunk, as also is Severin's fix for the Byteman maven plugin and a fix to disable the javadoc errors in agent caused by the inability of the parser generator to correctly generate tag info. So, if you pull the latest git repo you should be able to get it to build.

unfortunately I'm still not the lucky one. Pulling the newest fixes (BYTEMAN-306) does not resolve failures that I can see [1].

I asked on of my colleagues to clone the repo and run mvn install to get it installed and he ends with the same failures as me (he uses Debian). Would be possible that you have some locally change maven settings.xml or something?