[fdo-internals] RE: [mapguide-internals] FDO Provider naming change with King Oracle

Sun Sep 27 08:26:35 EDT 2009

I should have replied to this earlier.  I guess I can understand that
position, though it was unfortunate that the change between Haris' release
and the FDO project release wasn't picked up on earlier; this is going to
inconvenience a lot of people.
Regardless, there are two procedures users in this position can follow
(manually upgrade their provider definitions or change the entry in their
local providers.xml file), so I'm OK with this approach.

Jason
2009/9/23 Greg Boone <greg.boone at autodesk.com>

> Regardless of what is being released on the sl-king site, I don't at all
> feel comfortable changing the provider name is a x.x.1 point release that
> has existed for two official releases.
>
> Greg
>
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:
> mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Zac Spitzer
> Sent: Wednesday, September 23, 2009 12:35 PM
> To: FDO Internals Mail List
> Cc: MapGuide Internals Mail List
> Subject: Re: [fdo-internals] RE: [mapguide-internals] FDO Provider naming
> change with King Oracle
>
> a lot of users would have used the more frequently updated
> sl-king builds i believe which had differing naming instructions,
> ie King.Oracle
>
> http://www.sl-king.com/fdooracle/download/README.txt
>
>
>
> On Thu, Sep 24, 2009 at 2:27 AM, Greg Boone <greg.boone at autodesk.com>
> wrote:
> > So I finally got around to looking into this further. It seems that the
> official FDO 3.3 and 3.4 releases were published with the King Oracle
> Provider name being OSGeo.KingOracle. See Revision 4404. The switch to
> King.Oracle was incorrectly done in revision 4457. This change was incorrect
> because it no longer matched the name as published in FDO 3.3 and 3.4.
> >
> > At this point I don't see the solution being to changes the name in the
> .xml file. I see the solution being to revert the name change made in 4457
> to the name found in 4404 and leaving the .xml as is. Otherwise, the
> published provider name would change from FDO 3.3/3.4 to FDO 3.4.1.
> >
> > Greg
> >
> > -----Original Message-----
> > From: mapguide-internals-bounces at lists.osgeo.org [mailto:
> mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
> > Sent: Tuesday, August 04, 2009 9:06 AM
> > To: MapGuide Internals Mail List; FDO Internals Mail List
> > Subject: RE: [fdo-internals] RE: [mapguide-internals] FDO Provider naming
> change with King Oracle
> >
> > OK. I will make that change and post a patch.
> >
> > -----Original Message-----
> > From: mapguide-internals-bounces at lists.osgeo.org [mailto:
> mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
> > Sent: Monday, August 03, 2009 2:06 AM
> > To: FDO Internals Mail List; MapGuide Internals Mail List
> > Subject: RE: [fdo-internals] RE: [mapguide-internals] FDO Provider naming
> change with King Oracle
> >
> > Ah,
> >
> > thanks Greg.
> >
> > The existing name was King.Oracle.x.y
> >
> > This file currently has it as OSGeo.KingOracle.x.y
> >
> >
> http://trac.osgeo.org/fdo/browser/branches/3.4/providers.windows.template.xml
> >
> > If possible, I think it would be best to go back to the King.Oracle.x.y
> naming in this file to reduce impact for users who have been using this
> provider since before it was being bundled in the FDO and MapGuide
> installers, and to match the internal name of the provider.
> >
> > Jason
> >
> > -----Original Message-----
> > From: fdo-internals-bounces at lists.osgeo.org [mailto:
> fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
> > Sent: Monday, July 27, 2009 7:14 AM
> > To: FDO Internals Mail List; MapGuide Internals Mail List
> > Subject: RE: [fdo-internals] RE: [mapguide-internals] FDO Provider naming
> change with King Oracle
> >
> > The name change may possibly have occurred when porting the trunk code
> back to the 3.4 branch.
> >
> >        Revision: 4457
> >        Author: gregboone
> >        Date: 6:07:10 PM, Thursday, March 19, 2009
> >        Message:
> >        Ticket #45: Ported Latest KingOracle Submission to 3.4 Branch
> >
> > What is the name expected to be? We can revert this change and release a
> patch if needed.
> >
> > Greg.
> >
> >
> > -----Original Message-----
> > From: fdo-internals-bounces at lists.osgeo.org [mailto:
> fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
> > Sent: Monday, July 27, 2009 5:20 AM
> > To: MapGuide Internals Mail List; FDO Internals Mail List
> > Subject: [fdo-internals] RE: [mapguide-internals] FDO Provider naming
> change with King Oracle
> >
> > That kinda sucks for existing users...
> >
> > I wonder if this was an intentional change in fdo, or an accidental
> rename in the template?  I'm tempted to revert to the old value in the
> MapGuide setup just to limit impact on our users.
> >
> > Jason
> >
> > -----Original Message-----
> > From: Jackie Ng
> > Sent: Monday, July 27, 2009 1:19 AM
> > Subject: RE: [mapguide-internals] FDO Provider naming change with King
> Oracle
> >
> >
> > /me thinks that this information is not actually used when building the
> FDO
> > distribution, seeing as the providers.xml template calls it
> OSGeo.KingOracle
> >
> >
> http://trac.osgeo.org/fdo/browser/branches/3.4/providers.windows.template.xml
> >
> > - Jackie
> >
> >
> > Jason Birch wrote:
> >>
> >> Is that in the latest build only?
> >>
> >> It looks like it's still called King.Oracle in the provider source, so I
> >> wonder if it's just an oversight in the installer.
> >>
> >>
> http://trac.osgeo.org/fdo/browser/branches/3.4/Providers/KingOracle/src/Provider/KgOraProvider.h
> >>
> >> Jason
> >>
> >> -----Original Message-----
> >> From: Zac Spitzer
> >> Sent: Monday, July 27, 2009 12:46 AM
> >> To: MapGuide Internals Mail List
> >> Subject: [mapguide-internals] FDO Provider naming change with King
> Oracle
> >>
> >> Just been playing with King Oracle and the 2.1 beta and discovered
> >> that the naming has changed from King.Oracle to OSGeo.KingOracle
> >>
> >> which broke a lot of my feature sources, probably a good one for the
> >> release notes. a quick edit of the xml solved the problem
> > _______________________________________________
> > fdo-internals mailing list
> > fdo-internals at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/fdo-internals
> > _______________________________________________
> > fdo-internals mailing list
> > fdo-internals at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/fdo-internals
> > _______________________________________________
> > mapguide-internals mailing list
> > mapguide-internals at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> > _______________________________________________
> > mapguide-internals mailing list
> > mapguide-internals at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> > _______________________________________________
> > fdo-internals mailing list
> > fdo-internals at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/fdo-internals
> >
>
>
>
> --
> Zac Spitzer -
> http://zacster.blogspot.com
> +61 405 847 168
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>