[Heads up] New Utils subproject

[Guillaume Nodet <gn...@gmail.com>]

I've just created a new Utils subproject.
The goal is to put there classes that can be reused and shared across
subprojects.  Each subproject can either embed the required packages or
import them as they want.
Currently, it includes the following packages:
  * org.apache.felix.utils.collection:  IteratorToEnumeration,
MapToDictionary
  * org.apache.felix.utils.filter: FilterImpl (a Filter implementation
supporting the subset / superset operators)
  * org.apache.felix.utils.log: Logger (a simple logger that delegates to
the Log service if present, stderr if not)
  * org.apache.felix.manifest: osgi headers parsing
  * org.apache.felix.version: VersionRange, VersionTable (cache of version),
VersionCleaner (to transform a string such as a maven version into a correct
osgi version)

If you have a similar class in on the subproject you're working on, please
consider switching to those version, enhancing if needed.  The goal is
really to share this code and come up with useful clases, so any use case
that's not covered needs to be.
Also, now is the time to refactor those classes as needed, once they'll be
release, it'll be a bit more difficult to incorporate major refactoring.

I'll work on bundlerepository and bundleplugin asap to leverage those
classes.

-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: [Heads up] New Utils subproject

[Marcel Offermans <ma...@luminis.nl>]

Makes a lot of sense, yes. If we really break backward compatibility we can always bump the major version of that jar file and people can depend on the exact version if they don't want to move to a new version.

On Mar 18, 2010, at 10:42 , Guillaume Nodet wrote:

> Sounds good.  I did not really envision to use this subproject as a real
> bundle either.  To ensure that we may want to not release it as a bundle but
> a plain jar.
> 
> On Thu, Mar 18, 2010 at 10:32, Marcel Offermans <marcel.offermans@luminis.nl
>> wrote:
> 
>> Hello Guillaume,
>> 
>> Great initiative. I think its good to have a common toolbox to get utility
>> classes from.
>> 
>> On Mar 18, 2010, at 9:49 , Guillaume Nodet wrote:
>> 
>>> Also, now is the time to refactor those classes as needed, once they'll
>> be
>>> release, it'll be a bit more difficult to incorporate major refactoring.
>> 
>> I am wondering if a collection of utility classes ever will have a "stable
>> API". My personal preference would be to release this as a library from
>> which individual bundles can take classes or packages, but not as a bundle
>> which exports its whole contents.
>> 
>> If a project then decides to share amongst a set of bundles what they take
>> from this toolbox, that's their responsibility.
>> 
>> Or at least do it like this until we are confident we have a "stable API".
>> 
>> Greetings, Marcel
>> 
>> 
> 
> 
> -- 
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com

Re: [Heads up] New Utils subproject

[Guillaume Nodet <gn...@gmail.com>]

Sounds good.  I did not really envision to use this subproject as a real
bundle either.  To ensure that we may want to not release it as a bundle but
a plain jar.

On Thu, Mar 18, 2010 at 10:32, Marcel Offermans <marcel.offermans@luminis.nl
> wrote:

> Hello Guillaume,
>
> Great initiative. I think its good to have a common toolbox to get utility
> classes from.
>
> On Mar 18, 2010, at 9:49 , Guillaume Nodet wrote:
>
> > Also, now is the time to refactor those classes as needed, once they'll
> be
> > release, it'll be a bit more difficult to incorporate major refactoring.
>
> I am wondering if a collection of utility classes ever will have a "stable
> API". My personal preference would be to release this as a library from
> which individual bundles can take classes or packages, but not as a bundle
> which exports its whole contents.
>
> If a project then decides to share amongst a set of bundles what they take
> from this toolbox, that's their responsibility.
>
> Or at least do it like this until we are confident we have a "stable API".
>
> Greetings, Marcel
>
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Re: [Heads up] New Utils subproject

[Marcel Offermans <ma...@luminis.nl>]

Hello Guillaume,

Great initiative. I think its good to have a common toolbox to get utility classes from.

On Mar 18, 2010, at 9:49 , Guillaume Nodet wrote:

> Also, now is the time to refactor those classes as needed, once they'll be
> release, it'll be a bit more difficult to incorporate major refactoring.

I am wondering if a collection of utility classes ever will have a "stable API". My personal preference would be to release this as a library from which individual bundles can take classes or packages, but not as a bundle which exports its whole contents.

If a project then decides to share amongst a set of bundles what they take from this toolbox, that's their responsibility.

Or at least do it like this until we are confident we have a "stable API".

Greetings, Marcel