[dash-dev] Maven setup and corrupt 'xtext proxy'

Discussion:

Alex Blewitt

2011-12-13 16:01:11 UTC

Does anyone know why/when the 'xtext proxy' was set up on maven.eclipse.org? It was causing builds which were corrupted from the xtext one to be served out to anyone who asked for assets via the /public/ maven repository.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=365727

I have removed this but we will need to execute a clean on the hudson build slaves that may have cached bad content and let that resync. Does anyone know how we go about doing this?

Alex

David Carver

2011-12-13 17:14:38 UTC

Permalink

I had created this at the request of the Xtext project, as they didn't
want/couldn't use the mvn deploy or release plugins since they were
using Buckminster to create their maven repository.

Sorry if I broke things with the proxy.

Dave

Post by Alex Blewitt
Does anyone know why/when the 'xtext proxy' was set up on maven.eclipse.org? It was causing builds which were corrupted from the xtext one to be served out to anyone who asked for assets via the /public/ maven repository.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=365727
I have removed this but we will need to execute a clean on the hudson build slaves that may have cached bad content and let that resync. Does anyone know how we go about doing this?
Alex
_______________________________________________
dash-dev mailing list
https://dev.eclipse.org/mailman/listinfo/dash-dev

Alex Blewitt

2011-12-13 22:47:03 UTC

Permalink

Did they give any reasons why the 'mvn deploy' wouldn't work for the specific artefacts that they were looking for? Is it just that Buckminster generates a Maven repository, but doesn't have any of the project components which permits a mvn:deploy or mvn:deploy-file to run?

Alex

I had created this at the request of the Xtext project, as they didn't want/couldn't use the mvn deploy or release plugins since they were using Buckminster to create their maven repository.
Sorry if I broke things with the proxy.
Dave

_______________________________________________
dash-dev mailing list
https://dev.eclipse.org/mailman/listinfo/dash-dev

David Carver

2011-12-13 23:49:30 UTC

Permalink

Yep, they didn't want to go through writing a script that would run
mvn:deploy-file.

They use buckminster, and didn't want to go through trying to get maven
working as part of the build. They might be open to contributions. I
believe the comments are in the original bug report.

Dave

Post by Alex Blewitt
Did they give any reasons why the 'mvn deploy' wouldn't work for the specific artefacts that they were looking for? Is it just that Buckminster generates a Maven repository, but doesn't have any of the project components which permits a mvn:deploy or mvn:deploy-file to run?
Alex

I had created this at the request of the Xtext project, as they didn't want/couldn't use the mvn deploy or release plugins since they were using Buckminster to create their maven repository.
Sorry if I broke things with the proxy.
Dave

_______________________________________________
dash-dev mailing list
https://dev.eclipse.org/mailman/listinfo/dash-dev