Re: [cbi-dev] Procedure to deploy to download.eclipse.org

[Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx>]

Mikael Barbero wrote:
>> I think much of this can be tackled by Maven plugins during the build
>> already. I can very well imagine tycho-p2-repository:archive-repository
>> learning to compress the update site with zx as well.
> 
> Of course. We have to weight what has to be done on the client side and on the server side. However, for things that we want to enforce, I think this is much easier to do it on the server side.
>
>> Same thing goes for mirror and stats URIs.
> 
> Yes, on the server side we can implement some checks and reject repos that don't meet the criteria instead of doing the actual work. However, I think that everybody will more than happy if the server does most of the hurdle and they don't have to change their build to do it. Moreover, improvements on the server side are much easier to deploy than to convince everybody to use a new version of a Maven plugin ;)

Implementing the checks on the server (web-service) side and rejecting
if the quality criteria (no mirror URIs, no index.html, whatever) are
not met sounds reasonable.

I would just prefer if much of the actual metadata would be filled in on
the client/build side, not by the server/publisher. In particular, this
makes it much easier to test things locally; just look at the
artifacts.xml and check whether the stats URI is set, for example.

Also, you would not need to pass so many arguments to the publisher
server (like stats URI, mirror URI, project description). All that IMHO
should be required is the desired location on download.eclipse.org.

I envision this to be a bit like Maven Central. You upload your JAR+POM,
it gets checked, and then published at a certain location of all quality
criteria are met.

In fact, I think Tycho by default already produces the perfect artifact
to upload to a publishing web service: the zipped update site.

What do you think?

>> There is one common resource, however, which I would really like to be
>> offered by CBI: a common index.html for update sites that adheres to
>> eclipse.org's current theme.
> 
> Definitely, that could be one thing with a lot of values for projects.
> 
> I am really interested in working on something like this. I will draft a document with the ideas and see where it goes.

Great. Thank you.

Also, one further benefit I can see is that not every project needs to
write its own PHP script to do directory listings (which is not
completely trivial to do without security issues).

Best wishes,

Andreas

-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940