Re: [orbit-dev] zip downloads

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

The zips that we have are not bundles
but zips that have bundles in them.  They happen to have just one
but otherwise they are no different than any of hte other zips that we
produce at Eclipse.  My hope is that we would just have one form for
the bundles on the server and it would be JAR'd. This is very much in line
with what Update does and what hte new provisioning story will do.  How
that archive is handled once it is downloaded is a different matter.  In
essence we are uing the .zip extension as a flag. As you say, I would rather
do something more explicit.

The bug report you pointed out is very
much at play here.  It may be the case that we have to do something
like this.  I am still torn as to whether it could/should be in the
bundle itself.  Certianly in the provisioning system we have places
to put it other than in the bundle JAR but as cool as it will be we don;t
want to force everyone through the provisioning funnel.

The problem I am talking about here
is a little pedantic and somewhat simple semantics but it does feel important
(at least to me).  The issue is, there are two valid forms for a bundle
in Eclipse today.  JAR'd and as a dir.  A zip that has a dir
or a JAR in it does not count.  So haveing a bundle download page
that gives people individual bundles where some come stand alone and others
come nested inside a zip feels inconsistent. 

Jeff

David M Williams <david_williams@xxxxxxxxxx>
Sent by: orbit-dev-bounces@xxxxxxxxxxx

07/26/2007 10:41 PM

Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>

To	Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
cc
Subject	Re: [orbit-dev] zip downloads

> [...] 
>  If this is simply a way of signaling that the archive should
be 
> exploded then I'd propose that we find a different way.  A JAR'd
> bundle and a folder bundle should be exactly the same.  The zips
> have an extra directory level that make this inconsistent 

Yes, this was the reason. I may have decided this all on my own as one
way to handle it. 
If you'd like to change, I suppose we could always use features. :) 

I'm not sure what you mean by "extra directory level" .... the
zips should be unzipped to [install-dir]/plugins, 
and the jars should be copied to [install-dir]/plugins. 

So, suspect I'm missing what the problem is. 

Is it just that there are different files extensions? I think before we
could (easily) fix that, we'd need 
some improvements such as https://bugs.eclipse.org/bugs/show_bug.cgi?id=157562.

Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>
Sent by: orbit-dev-bounces@xxxxxxxxxxx

07/26/2007 10:21 PM

Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>

To	Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
cc
Subject	[orbit-dev] zip downloads

It has been pointed out that our download site has a mixture of JARs and
zips where the zips contain just one bundle.  It seems that this is
done for bundles that need to be run in folder form rather than JAR'd.
 While this was likely discussed and agreed to, I am failing to recall
when and why.  This seems wholy inconsistent and confusing.  If
this is simply a way of signaling that the archive should be exploded then
I'd propose that we find a different way.  A JAR'd bundle and a folder
bundle should be exactly the same.  The zips have an extra directory
level that make this inconsistent 

Jeff _______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev