serverside problems with multi-module projects
Laures opened this issue · 9 comments
for unknown reasons the server returns an invalid respons for a single module in multi module projects. once this has happend the first time the issue travels through the modules in their reactor ordering (the order in which maven builds the modules) with every build.
For example:
build X:
module1: success
module2: fail
module3: skipped
build X+1:
module1: success
module2: success
module3: fail
once the issue reached the last module it will vanish (so far it has not returned).
The behavior is persistent over machines (no surprise there).
mvn -e returns the following stacktrace:
[ERROR] Failed to execute goal com.versioneye:versioneye-maven-plugin:2.1.0-BATSU:update (default-cli) on project mvc: Oh no! Something went wrong. Get in touch with the VersionEye guys and give them
feedback.You find them on Twitter at https//twitter.com/VersionEye. Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
[ERROR] at [Source: java.io.InputStreamReader@76ce21e7; line: 1, column: 2]
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.versioneye:versioneye-maven-plugin:2.1.0-BATSU:update (default-cli) on project mvc: Oh no! Something went wrong. Get
in touch with the VersionEye guys and give them feedback.You find them on Twitter at https//twitter.com/VersionEye.
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Oh no! Something went wrong. Get in touch with the VersionEye guys and give them feedback.You find them on Twitter at https//twitter.com/Vers
ionEye.
at com.versioneye.UpdateMojo.execute(UpdateMojo.java:32)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.codehaus.jackson.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null')
at [Source: java.io.InputStreamReader@76ce21e7; line: 1, column: 2]
at org.codehaus.jackson.JsonParser._constructError(JsonParser.java:1433)
at org.codehaus.jackson.impl.JsonParserMinimalBase._reportError(JsonParserMinimalBase.java:521)
at org.codehaus.jackson.impl.JsonParserMinimalBase._reportUnexpectedChar(JsonParserMinimalBase.java:442)
at org.codehaus.jackson.impl.ReaderBasedParser._handleUnexpectedValue(ReaderBasedParser.java:1198)
at org.codehaus.jackson.impl.ReaderBasedParser.nextToken(ReaderBasedParser.java:485)
at org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2770)
at org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2718)
at org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1886)
at com.versioneye.UpdateMojo.uploadDependencies(UpdateMojo.java:45)
at com.versioneye.UpdateMojo.execute(UpdateMojo.java:28)
... 21 more
NOTE: 2.1.0-BATSU is actually the current snapshot. i had to fix the version because our maven repository does not accept snapshots.
issue happened on multiple projects with a maximum of three times on the same repository
i made some tests and the response i get is the html-error-page. My last test was at 11.15 (german time). I hope you find something helpful in your logs.
@Laures How many modules you have in your reactor? Do you have the html-error-page? A screenshot could be helpful.
i just printed the content of the reader returned by httpUtils.post (which by the way is a static method. not sure why you create an instance of it). the result is:
<!DOCTYPE html>
<html >
<head >
<title>VersionEye</title>
</head>
<body style="color: #22211f;
background-color: lightgray;
background-repeat: no-repeat;
background-position: 50px 30px;
font-size: 14px;
font-family: sans-serif, arial, verdana, tahoma, 'lucida grande', 'Segoe UI', 'lucida sans unicode';
padding: 0px;
margin: 0px;">
<div style="background-image: url('https://s3.amazonaws.com/veye_assets/header_os.png');
background-repeat: repeat-x;
background-position: top;
margin: 0px;
padding: 0px;
height: 55px;
width: 100%;
vertical-align: middle;">
<div style="width: 690px;
margin: 0 auto;
clear: both;
display: block;
height: 0;">
<div style="float: left; margin: 0; padding: 0;">
<a href="http://www.versioneye.com"><img src="https://s3.amazonaws.com/veye_assets/header_logo_os.png" /></a>
</div>
<div style="float:left; margin-top: 13px; margin-left: 5px;">
<a href="http://www.versioneye.com"><img src="https://s3.amazonaws.com/veye_assets/eye_off.png" /></a>
</div>
</div>
</div>
<div style="width: 690px;
margin: 0 auto;">
<div style="
display: inline-block;
width: 650px;
padding: 20px;
margin-top: 10px;
background-color: white;
-moz-border-radius: 10px;
-webkit-border-radius: 10px;
border-radius: 10px;
text-align: center;" >
<br/>
<br/>
<br/>
<h2>We're sorry, but something went wrong.</h2>
<p>We've been notified about this issue and we'll take a look at it shortly.</p>
<br/>
<br/>
<br/>
</div>
<div style="-moz-border-radius: 10px; -webkit-border-radius: 10px; border-radius: 10px;
text-align: left;
margin-top: 15px;
padding: 20px;
width: 650px;
margin-left: auto;
margin-right: auto;
clear: both;
background-color: white;
font-size: 12px;
color: #808080;
word-wrap:break-word;" >
VersionEye GmbH | Invalidenstrasse 50/51 | D-10557 Berlin | Germany |
E-Mail: contact [at] versioneye.com | Amtsgericht: Berlin / Charlottenburg | Handelsregister: Berlin, HRB 144242 B | USt-IdNr.: DE282045007 | CEO: Robert Reiz
</div>
</div>
<br/>
<br/>
</body>
</html>
One of my projects has 8 modules and some have more.
I guess I made the method static afterwards and didn't update the method calls.
I try to reproduce it. Must be a server issue.
@Laures In the Exception you posted earlier I can see that UpdateMojo.java:28 is causing the problem. That's why I don't think it's an server problem. I just pushed an update. Can you please try it again with the current master branch?
@Laures Can you please try again with the current version of the plugin, which is 3.7.0. Many Thanks!
I close this ticket because nobody else had this problems. I assume it's fixed in the current version.