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
On 12/13/2011 05:47 PM, Alex Blewitt wrote:
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
On 13 Dec 2011, at 17:14, David Carver wrote:
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
On 12/13/2011 11:01 AM, Alex Blewitt wrote:
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
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
