Took a while but I got some feedback :) Thanx.
You remarks are valid Guillaume. My main scope of putting this out
there was to see this kind of feedback so we or you guys can improve
it. is OSS so go one, fork and make pull requests.
Or make issues so we can discuss them.

Now back to your remarks, the OSGi version will nto be regenerated
only in case the original jar changes or when the recipe (bnd
instructions) changes. As the recipe can only change by updating it
(deploying another one) or when the jar changes, basically you can say
that the bundle remains the same.

Maybe we can also introduce staging into the picture so when the
bundle changes (recipe/jar changed) we create the osgi into a staging
repository that is then promoted to a production one only after manual
validation.

On Thu, Aug 2, 2012 at 11:05 PM, Guillaume Nodet <gno...@gmail.com> wrote:
> Nice work Alin !
>
> I think the reproductibility of the download is really a *major* problem.
>
> That's why when we release wrapped bundles in servicemix, we add some
> incremental counter for the osgi metadata itself, so that the artifact never
> changes:
>
> http://central.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.commons-io/
>
> So we have the version of the original jar followed by '_' and the counter
> in case the metadata is fixed or enhanced.
>
> Until there's a way to have downloads reproducible, I strongly thing that
> can not be used in production.
>
> Another problem is that I fear people will start using those bundles and
> find some osgi related problems for libraries that don't really work well in
> OSGi, so it can be confusing.    So I wonder if this should be limited to
> libraries for which a bnd instruction file has been provided and tested.

-- 
Alin Dreghiciu
Software Developer
My profile: http://www.linkedin.com/in/alindreghiciu
My blog: http://adreghiciu.wordpress.com
http://sonatype.com - Sonatype - The Maven Company
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.

_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to