So I've made some progress on the MapML support. I've a got a stub in for the documentation (more to be added this week), and i see that it is live on the docs website. I'd like to get the MapML module added to the nightly build. I think I've figured out what I need to do, created an assembly descriptor xml, add mapml to the communityRelease profile, and add it as a dependency of the community/release module? Am I allowed to do this? What is the maven command to actually build the community modules (so that I can test my changes before I commit)?
On a side note, the MapML module makes use of the Spring-oxm module, and I noticed that the version of this is pinned to 3.0.5 in the geoserver top-level pom dependencyManagement, while other spring components use spring.version=5.1.1.RELEASE - the only other module that I see using spring-oxm is geofence. I don't need the newer version, but I'm curious if this version mismatch is intentional or accidental?
Thanks,
Chris
--
Chris Hodgson
Refractions Research
Suite 419 – 1207 Douglas Street
Victoria, British Columbia
Canada, V8W 2E7
1-250-383-3022
http://www.refractions.net
So I’ve made some progress on the MapML support. I’ve a got a stub in
for the documentation (more to be added this week), and i see that it is
live on the docs website. I’d like to get the MapML module added to the
nightly build. I think I’ve figured out what I need to do, created an
assembly descriptor xml, add mapml to the communityRelease profile, and
add it as a dependency of the community/release module?
Yes
Am I allowed to do this?
As long as it does not break the build, yes 
What is the maven command to actually build the community modules (so that I can test my changes before I commit)?
Get in the community modules root:
- mvn clean install -PcommunityRelease -DskipTests (community modules tests are never run, you need to graduate to extension for that to happen)
- mvn assembly:attached
- check in target/release
On a side note, the MapML module makes use of the Spring-oxm module, and
I noticed that the version of this is pinned to 3.0.5 in the geoserver
top-level pom dependencyManagement, while other spring components use
spring.version=5.1.1.RELEASE - the only other module that I see using
spring-oxm is geofence. I don’t need the newer version, but I’m curious
if this version mismatch is intentional or accidental?
Not sure, but it can be intentional, GeoFence core is depending on old library versions and upgrading it
is not a small task.
Cheers
Andrea
···
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.