Re: [udig-devel] udigLite: An OSGi-friendly subset

[Jody Garnett <jody.garnett@xxxxxxxxx>]

Hi again:

That time consuming process has a limit of two weeks; and a three day
limit before we can start applying the first patch. We have those
polices in place exactly to prevent organizaations such as yourself
needing to take a copy of the code base.

One thing that we do need to do is present our case clearly (not as a
conversation from the udig list where the benifit to geotools is lost
admit the rest of the messaage).

As for support of the GeoTools community we did line up support last
time; but by that point your branch may of already started.

So I am wanting to put this into GeoTools; it was first reported in
2005 (the conflict between FactorySPI and OSGi). The approach of
adding OSGi information to the manifest was tested as sound by the
JPOX team a few years later.

And more importantly you are not the only team to do the work; I hate
seeing duplication of effort.

Jody

On Fri, Mar 20, 2009 at 1:02 AM, Wellmann, Harald
<harald.wellmann@xxxxxxxxxx> wrote:
>> I "invited" you; let me know if you have any trouble.
>
> Thanks, I can log in! It might take a while for me to write a post, I'm
> busy with an ugly bug today...
>
>>
>> So here is a question for you -- *when* can we do this work?
>> I do not mind volunteering for something so strategic; but we
>> will need write a proposal and organze our lives so we have
>> some time in front of a computer to "apply" this branch of yours.
>>
>
> The first question really is: *what* exactly do we want to do, and how
> much support do we get from the Geotools side?
>
> Our geotools-osgi project does build all of Geotools, but only those
> libraries that are actually used by udigLite are osgfied, the rest is
> still plain old JARs.
>
> The set of Geotools libs required by uDig trunk will be larger than our
> subset, but still smaller than all of Geotools, I guess. So we would
> have to osgify at least the remaining uDig prerequisites in Geotools
> (and maybe some other third-party libs required by these).
>
> There are three options for that:
>
> 1) Continue using our geotools-osgi project at BerliOS.
> 2) Create a "Geotools osgified" branch within the scope of the uDig
> project
> 3) Get official Geotools support for doing this on a working branch of
> Geotools, with the perspective to end up in Geotools trunk.
>
> When I first raised the question last year, the feedback from the
> Geotools side was none too enthusiastic, and that's why I created the
> BerliOS clones, simply because I could not afford to let my employer
> depend on a time-consuming voting process in a community project.
>
> Of course number 3 would be the best solution...
>
> Best regards,
>
> Harald
>
> *******************************************
> innovative systems GmbH Navigation-Multimedia
> Geschaeftsfuehrung: Edwin Summers - Kevin Brown
> Sitz der Gesellschaft: Hamburg - Registergericht: Hamburg HRB 59980
>
> *******************************************
> Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
> This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden.
> *******************************************
> _______________________________________________
> User-friendly Desktop Internet GIS (uDig)
> http://udig.refractions.net
> http://lists.refractions.net/mailman/listinfo/udig-devel
>