vaadin-addons - response body problem

Hi everybody,

Here is server response from


I can’t download addons via maven.
Do you have a mirror?
What i’m doing wrong?

Some details:

Response Header

HTTP/1.1 200 OK
x-amz-id-2: 1GQvDaHeSlW+FK59Z/fQMb4JHLIwwYJ0qWvjC0Dq23MuufbIpUDw3OfMrEi/Lgpl
x-amz-request-id: 466C22B7B79B6C17
Date: Wed, 08 Jan 2014 15:20:49 GMT
x-amz-meta-group: 1000
x-amz-meta-owner: 1000
x-amz-meta-permissions: 16877
Last-Modified: Fri, 27 Aug 2010 12:49:42 GMT
ETag: "d66759af42f282e1ba19144df2d405d0"
Accept-Ranges: bytes
Content-Length: 38
Server: AmazonS3

Response Body


Sean isn’t browsable, but Maven should be able to download add-ons from there just fine as it knows the path for the add-on based on the group id, artifact id and version.

As I said before, i can’t download via maven. Here is output. About month ago, maven worked like a harm.

09-Jan-2014 15:30:27     [ERROR]
 Failed to execute goal on project Project: Could not resolve dependencies for project com.sean:project:war:0.1: Failed to collect dependencies at net.sf.jasperreports:jasperreports:jar:5.5.0 -> com.lowagie:itext:jar:2.1.7.js2: Failed to read artifact descriptor for com.lowagie:itext:jar:2.1.7.js2: Could not transfer artifact com.lowagie:itext:pom:2.1.7.js2 from/to vaadin-addons ( Connection to refused: Connection refused: connect -> [Help 1]

thanks in advance

The last part of the error message comes from a transitive dependency that probably should be in Maven Central - not a Vaadin add-on. Normally Maven just tries to contact all the configured repositories until an artifact is found, and gives an error message for repositories where in which it was not found (even if it is later found in another repository) so that part of the message is normal. The beginning (if not cut out of context) does suggest, though, that perhaps Maven is not checking Maven Central for that artifact at all (configured that way at your end or not found in central and that resolution cached?).

If something is not working, some additional information is probably needed about the problem and the project configuration and what Maven outputs.