It seems we're getting a lot of failures due to deploy problems. Do we
really need to deploy the snapshots? (as I doubt that we can fix the
deployment problems) Or can we maybe ignore the error if deployment fails?

Regards
Carsten

Am 04.10.15 um 13:07 schrieb Apache Jenkins Server:

> Waiting for Jenkins to finish collecting data
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on 
> project org.apache.sling.settings: Failed to deploy metadata: Could not 
> transfer metadata 
> org.apache.sling:org.apache.sling.settings:1.3.7-SNAPSHOT/maven-metadata.xml 
> from/to apache.snapshots.https 
> (https://repository.apache.org/content/repositories/snapshots): Failed to 
> transfer file: 
> https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.settings/1.3.7-SNAPSHOT/maven-metadata.xml.
>  Return code is: 502, ReasonPhrase: Proxy Error. -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR] 
> [ERROR] After correcting the problems, you can resume the build with the 
> command
> [ERROR]   mvn <goals> -rf :org.apache.sling.settings
> channel stopped
> 


-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Reply via email to