[mapguide-internals] Motion: RFC129 - SWIG/IMake enhancements and enhanced Java wrapper API
jumpinjackie at gmail.com
Thu Jan 10 20:00:16 PST 2013
This doesn't affect any of the key areas that would require unanimous
ratification to implement:
* A new resource type
* A new schema revision
* A new mapagent operation
* A change in any public MapGuide API
So unlike RFC128 (which affected one or more of the above), ADSK can be free
to accept this into their 2.5 branch or not. I won't force the matter.
View this message in context: http://osgeo-org.1560.n6.nabble.com/Motion-RFC129-SWIG-IMake-enhancements-and-enhanced-Java-wrapper-API-tp5026528p5026820.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.
More information about the mapguide-internals