Re: [oscar-devel] Packaging Bundles

[Nektarios K. P. <npa...@in...>]

Humberto Cervantes wrote:
> In my point of view, I think the 1st solution is better since:
> 
> - It's less discouraging for somebody who wants to begin to explore a
> new project to just download the source, type 'ant' and see that it
> compiles directly. Just think about your own reactions when you download
> some tar file in Linux, type ./configure and see a bunch of errors, you
> just go and grab the rpm !
> 
> - The cost of including libraries is rather negligible. In particular
> because today we have more and more high speed internet access plus
> gigabytes of hard drive.
> 

I am afraid that we are facing the problem of two quite different use 
scenarios that OSCAR / OSGi is trying to satisfy. What you are saying is 
true for the desktop environment of a home-user,

We are talking about source-bundle and indeed the download/compile phase 
is, in most cases, going to happen on a host with high speed internet 
access and gigabytes of hard drive. But the situation for embedded 
devices is different. Both download time and storage space have to be 
considered.

A feature I would like to see in those source-bundles is a build option 
like say 'ant strip' that produce multitpl bundles. The main bundle and 
one bundle for each required library.

Example:
The source bundle for application app-foo1 contains:
	-the source
	-required library lib-bar-1.jar
		that provides com.acme.bar1 var1.0
	-required library lib-bar-2.jar
		that provides com.acme.bar2 ver1.0
	-the build script

If you type `ant`, you get a single bundle app-foo1-all.jar, which 
contains the compiled application and the embedded libraries 
lib-bar-1.jar and lib-bar-2.jar.

if you type ant strip, you get three bundles:
	app-foo1.jar
		with Import-Package headers requesting
		com.acme.bar1;specification-version=1.0
		and  com.acme.bar2;specification-version=1.0
	lib-bar1.jar
		with Export-Package header
		com.acme.bar1;specification-version=1.0
	lib-bar2.jar
		with Export-Package header
		com.acme.bar2;specification-version=1.0


But this is only my point of view, and whatever would be the result of 
this discussion would be a "Recommendation"


---
nek