[GeoNode-devel] Upgrade to GeoServer 2.9
Erik Merkle
emerkle at boundlessgeo.com
Mon Jul 11 07:15:54 PDT 2016
Alessio,
I'm sorry I misunderstood what you were asking the first time. The GeoGig
jars (Locationtech GeoGig jars) are being published to the Boundless Maven
repository at https://repos.boundlessgeo.com/snapshot. That is, all of the
*org.locationtech.geogig* jars. The plugin itself, was not being published,
until this weekend when I merged it into the 2.9 and master branches of
GeoServer. It appears that the plugin jar (*gs-geogig*) is being published
to the Boundless repos as well. To use it in a maven POM, you should only
have to add something like this:
<dependency>
<groupId>org.geoserver.community</groupId>
<artifactId>gs-geogig</artifactId>
<version>2.9-SNAPSHOT</version>
</dependency>
As long as you have the Boundless repos in your dependency management
section.
The shaded jar reference you mentioned is no longer needed. We stopped
shading the jar once we put the plugin into the GeoServer community
modules, in the main GeoServer github repo. The shaded jar stuff was for
the old Boundless github repo, which we aren't using any more.
Is GeoNode expecting to use a shaded all-in-one JAR for the GeoServer
plugin? Since we moved the plugin to the GeoServer community modules
section, the normal assembly process has been building a ZIP bundle of the
plugin, along with all the necessary JARs not included in an out-of-the-box
GeoServer install. So you should be able to use that process, and unzip the
resulting plugin bundle into a GeoServer WEB-INF/lib directory and be good
to go. No need to use a shaded JAR any more, at least not for a standard
GeoServer install.
Since the plugin is not a shaded JAR any more, there isn't a single JAR
that could be published to a Maven repository. However, the Boundless
nightly GeoServer builds do expose the community module bundles built via
the web. For the plugin for GeoGig, you can access the latest nightly build
here:
http://ares.boundlessgeo.com/geoserver/2.9.x/community-latest/
And specifically for the GeoGig plugin:
http://ares.boundlessgeo.com/geoserver/2.9.x/community-latest/geoserver-2.9-SNAPSHOT-geogig-plugin.zip
So you can choose how you want to get it.
- Download the bundle from the nightly Boundless builds
- Run the community module assembly process from a local checkout of the
latest GeoServer 2.9.x branch
- Pull in the GeoServer plugin for GeoGig dependency into your POM and
assemble from that (I've not done this, so I don't know if there are any
hidden issues with this method)
And all these notes should be applicable to the GeoServer master/2.10
version as well. Just change *2.9-SNAPSHOT* to *2.10-SNAPSHOT*, and *2.9.x*
to *master*.
Again, sorry for the confusion. Hope this helps. And please keep
the conversation going if there are still questions.
Erik Merkle
On Mon, Jul 11, 2016 at 4:35 AM, Alessio Fabiani <
alessio.fabiani at geo-solutions.it> wrote:
> Hello Erik,
> thanks for your work.
>
> Currently GeoNode requires
>
> <dependency>
> <groupId>org.opengeo.geoserver</groupId>
> <artifactId>gs-geogig</artifactId>
> <version>${gsgeogig.version}</version>
> <classifier>shaded-plugin</classifier>
> </dependency>
>
> to build.
>
> In order to move the thigs faster I currently did:
>
> 1. Pushed the gs-geogig JARs into the GeoSolutions public maven repository
> (http://maven.geo-solutions.it)
> Those should be pushed into the boundless webdav ones. I must admit that
> currently is not quite clear to me how is the policy to publish community
> plugins JARs automatically from the CI. Maybe they must be added to the
> "communityRelease" profile, but I have to ask.
>
> 2. Since I didn't find any maven builder extension to create the shaded
> JAR, I currently slightly modified the geoserver-geonode POM.XML as follows
>
>
> <!-- Updated geogit to geogig
> -->
> <dependency>
> <groupId>org.opengeo.geoserver</groupId>
> <artifactId>gs-geogig</artifactId>
> <version>${gsgeogig.version}</version>
> <!-- classifier>shaded-plugin</classifier -->
> <!-- exclusions>
>
> <exclusion><groupId>org.locationtech.geogig</groupId><artifactId>geogig-geotools</artifactId></exclusion>
>
> <exclusion><groupId>org.locationtech.geogig</groupId><artifactId>geogig-core</artifactId></exclusion>
>
> <exclusion><groupId>org.locationtech.geogig</groupId><artifactId>geogig-cli</artifactId></exclusion>
>
> <exclusion><groupId>org.locationtech.geogig</groupId><artifactId>geogig-mongodb</artifactId></exclusion>
>
> <exclusion><groupId>org.locationtech.geogig</groupId><artifactId>geogig-sqlite-xerial</artifactId></exclusion>
>
> <exclusion><groupId>org.locationtech.geogig</groupId><artifactId>geogig-sqlite-core</artifactId></exclusion>
>
> <exclusion><groupId>org.locationtech.geogig</groupId><artifactId>geogig-metrics</artifactId></exclusion>
>
> <exclusion><groupId>org.locationtech.geogig</groupId><artifactId>geogig-bdbje</artifactId></exclusion>
>
> <exclusion><groupId>org.locationtech.geogig</groupId><artifactId>geogig-web-api</artifactId></exclusion>
>
> <exclusion><groupId>org.locationtech.geogig</groupId><artifactId>geogig-osm</artifactId></exclusion>
>
> <exclusion><groupId>com.jolbox</groupId><artifactId>bonecp</artifactId></exclusion>
> </exclusions -->
> </dependency>
> <dependency>
> <groupId>ch.qos.logback</groupId>
> <artifactId>logback-core</artifactId>
> <version>${logback.version}</version>
> </dependency>
> <dependency>
> <groupId>ch.qos.logback</groupId>
> <artifactId>logback-classic</artifactId>
> <version>${logback.version}</version>
> </dependency>
> <dependency>
> <groupId>org.locationtech.geogig</groupId>
> <artifactId>geogig-cli</artifactId>
> <version>${geogig.version}</version>
> </dependency>
> <dependency>
> <groupId>org.locationtech.geogig</groupId>
> <artifactId>geogig-geotools</artifactId>
> <version>${geogig.version}</version>
> </dependency>
> <dependency>
> <groupId>org.locationtech.geogig</groupId>
> <artifactId>geogig-datastore</artifactId>
> <version>${geogig.version}</version>
> </dependency>
> <dependency>
> <groupId>org.locationtech.geogig</groupId>
> <artifactId>geogig-web-api</artifactId>
> <version>${geogig.version}</version>
> </dependency>
> <dependency>
> <groupId>org.locationtech.geogig</groupId>
> <artifactId>geogig-osm</artifactId>
> <version>${geogig.version}</version>
> </dependency>
> <dependency>
> <groupId>org.locationtech.geogig</groupId>
> <artifactId>geogig-postgres</artifactId>
> <version>${geogig.version}</version>
> </dependency>
> <dependency>
> <!-- required by gs-geogig but declares it as provided to avoid gt
> version clashes -->
> <groupId>org.geotools.jdbc</groupId>
> <artifactId>gt-jdbc-spatialite</artifactId>
> <version>${geotools.version}</version>
> </dependency>
> <dependency>
> <!-- required by gs-geogig but declares it as provided to avoid gt
> version clashes -->
> <groupId>org.geotools</groupId>
> <artifactId>gt-geopkg</artifactId>
> <version>${geotools.version}</version>
> </dependency>
>
> The build is successfull and the tests too. Please let me know if I did
> something wrong or if I forgot/missed something.
> Again I guess this is a side-effect of the missing automatic build of the
> gs-geogig plugin from the GeoServer Jenkins (unless in the past the shaded
> JAR has been build and published manually by boundless itself).
>
> Conclusions
> =============
> The update to GeoServer 2.9 for the GeoNode extension is now working and
> is ready to be pushed on.
> My idea is to move on the process and in the meantime clarify and (if
> needed) fix the two points above and eventually commit the changes after
> the merge.
>
>
> I look forward for you feedbacks/indications.
>
> Thanks again,
> -A.
>
>
>
>
>
> Best Regards,
> Alessio Fabiani.
>
> ==
> GeoServer Professional Services from the experts!
> Visit http://goo.gl/it488V for more information.
> ==
>
> Ing. Alessio Fabiani
> @alfa7691
> Founder/Technical Lead
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 331 6233686
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>
>
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
>
> ---------------------------------------------------------------------
>
> On Sat, Jul 9, 2016 at 6:57 AM, Erik Merkle <emerkle at boundlessgeo.com>
> wrote:
>
>> All,
>>
>> The GeoServer plugin for GeoGig has been merged into both the 2.9.x
>> branch of GeoServer as well as the master branch (GeoServer 2.10). The
>> GeoGig jars are on the Boundless repos as well. Hopefully this removes any
>> GeoGig related roadblocks for the upgrade.
>>
>> Regards,
>> Erik
>>
>> On Fri, Jul 8, 2016 at 9:14 AM, Erik Merkle <emerkle at boundlessgeo.com>
>> wrote:
>>
>>> Alessio,
>>>
>>> The latest stable GeoGig jars are already being pushed to the Boundless
>>> repo here:
>>>
>>> https://repo.boundlessgeo.com/snapshot
>>>
>>> The 1.0-SNAPSHOT version is stable and what the plugin is using (the
>>> plugin for GS 2.8 uses 1.0-SNAPSHOT and 2.9 and master will use the same
>>> GeoGig 1.0-SNAPSHOT version as soon as I get the PRs merged). You can build
>>> against the GeoGig jars by adding something like this to your POM:
>>>
>>> <dependency>
>>> <groupId>org.locationtech.geogig</groupId>
>>> <artifactId>geogig-web-api</artifactId>
>>> <version>1.0-SNAPSHOT</version>
>>> </dependency>
>>>
>>> There is also a Release Candidate version in the Boundless Artifactory
>>> here:
>>>
>>> https://repo.boundlessgeo.com/release
>>>
>>> But the latest release is version 1.0-RC2, dated early April.
>>>
>>> As for the plugin, I've got it all working for GS 2.9 and GS 2.10
>>> (master), just need to finish up a few functional tests and the PRs will be
>>> created.
>>>
>>> Regards,
>>>
>>> Erik
>>>
>>>
>>>
>>>
>>> On Fri, Jul 8, 2016 at 2:41 AM, Alessio Fabiani <
>>> alessio.fabiani at geo-solutions.it> wrote:
>>>
>>>> Very good,
>>>> thanks for your help.
>>>>
>>>> Is there a way to push the geogig jars on the boundless maven repo when
>>>> ready too?
>>>>
>>>> Thenaks again and kind regards,
>>>> -A.
>>>>
>>>>
>>>> Best Regards,
>>>> Alessio Fabiani.
>>>>
>>>> ==
>>>> GeoServer Professional Services from the experts!
>>>> Visit http://goo.gl/it488V for more information.
>>>> ==
>>>>
>>>> Ing. Alessio Fabiani
>>>> @alfa7691
>>>> Founder/Technical Lead
>>>>
>>>> GeoSolutions S.A.S.
>>>> Via di Montramito 3/A
>>>> 55054 Massarosa (LU)
>>>> Italy
>>>> phone: +39 0584 962313
>>>> fax: +39 0584 1660272
>>>> mob: +39 331 6233686
>>>>
>>>> http://www.geo-solutions.it
>>>> http://twitter.com/geosolutions_it
>>>>
>>>> -------------------------------------------------------
>>>>
>>>> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>>>>
>>>> Le informazioni contenute in questo messaggio di posta elettronica e/o
>>>> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
>>>> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
>>>> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
>>>> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
>>>> darcene notizia via e-mail e di procedere alla distruzione del messaggio
>>>> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
>>>> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
>>>> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
>>>> principi dettati dal D.Lgs. 196/2003.
>>>>
>>>>
>>>>
>>>> The information in this message and/or attachments, is intended solely
>>>> for the attention and use of the named addressee(s) and may be confidential
>>>> or proprietary in nature or covered by the provisions of privacy act
>>>> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
>>>> Code).Any use not in accord with its purpose, any disclosure, reproduction,
>>>> copying, distribution, or either dissemination, either whole or partial, is
>>>> strictly forbidden except previous formal approval of the named
>>>> addressee(s). If you are not the intended recipient, please contact
>>>> immediately the sender by telephone, fax or e-mail and delete the
>>>> information in this message that has been received in error. The sender
>>>> does not give any warranty or accept liability as the content, accuracy or
>>>> completeness of sent messages and accepts no responsibility for changes
>>>> made after they were sent or for other risks which arise as a result of
>>>> e-mail transmission, viruses, etc.
>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>> On Fri, Jul 8, 2016 at 3:46 AM, Erik Merkle <emerkle at boundlessgeo.com>
>>>> wrote:
>>>>
>>>>> I think I have the plugin for GeoGig ported over to GeoServer 2.9 and
>>>>> master (2.10). I'm finishing up some testing on them and as soon as I'm
>>>>> finished, I'll submit the PRs. Getting the plugin into the master branch on
>>>>> GeoServer should keep the plugin from causing issues with upgrading to
>>>>> GeoNode to use GeoServer 2.10, when that time comes.
>>>>>
>>>>> Erik Merkle
>>>>>
>>>>>
>>>>> On Thu, Jul 7, 2016 at 11:40 AM, Erik Merkle <emerkle at boundlessgeo.com
>>>>> > wrote:
>>>>>
>>>>>> All,
>>>>>>
>>>>>> I've started to look at getting the plugin for GeoGig ported over
>>>>>> from GeoServer 2.8.x to 2.9.x. Most of the issues are related to the Wicket
>>>>>> version changes and seem to be fairly easy to address. I hope to have it
>>>>>> ported over soon and I'll update the mailing list with my progress.
>>>>>>
>>>>>> Regards,
>>>>>> Erik Merkle
>>>>>>
>>>>>> On Thu, Jul 7, 2016 at 9:44 AM, Jeffrey Johnson <ortelius at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> +1 on moving to 2.9 with just a PR and ensuring the build works
>>>>>>> properly on build.geonode.org
>>>>>>>
>>>>>>> +100 to boundless and geosolutions coordinating on these issues :)
>>>>>>>
>>>>>>> +1000 on moving to a default geoserver build that doesnt require
>>>>>>> this plugin
>>>>>>>
>>>>>>> On Thu, Jul 7, 2016 at 7:40 AM, Alessio Fabiani <
>>>>>>> alessio.fabiani at geo-solutions.it> wrote:
>>>>>>>
>>>>>>>> Hi Daniel,
>>>>>>>> we can discuss when you are available during our both working hours
>>>>>>>> I guess. My timezone is Rome - Italy one.
>>>>>>>>
>>>>>>>> Thanks for your support.
>>>>>>>>
>>>>>>>> Best Regards,
>>>>>>>> Alessio Fabiani.
>>>>>>>>
>>>>>>>> ==
>>>>>>>> GeoServer Professional Services from the experts!
>>>>>>>> Visit http://goo.gl/it488V for more information.
>>>>>>>> ==
>>>>>>>>
>>>>>>>> Ing. Alessio Fabiani
>>>>>>>> @alfa7691
>>>>>>>> Founder/Technical Lead
>>>>>>>>
>>>>>>>> GeoSolutions S.A.S.
>>>>>>>> Via di Montramito 3/A
>>>>>>>> 55054 Massarosa (LU)
>>>>>>>> Italy
>>>>>>>> phone: +39 0584 962313
>>>>>>>> fax: +39 0584 1660272
>>>>>>>> mob: +39 331 6233686
>>>>>>>>
>>>>>>>> http://www.geo-solutions.it
>>>>>>>> http://twitter.com/geosolutions_it
>>>>>>>>
>>>>>>>> -------------------------------------------------------
>>>>>>>>
>>>>>>>> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>>>>>>>>
>>>>>>>> Le informazioni contenute in questo messaggio di posta elettronica
>>>>>>>> e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
>>>>>>>> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
>>>>>>>> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
>>>>>>>> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
>>>>>>>> darcene notizia via e-mail e di procedere alla distruzione del messaggio
>>>>>>>> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
>>>>>>>> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
>>>>>>>> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
>>>>>>>> principi dettati dal D.Lgs. 196/2003.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The information in this message and/or attachments, is intended
>>>>>>>> solely for the attention and use of the named addressee(s) and may be
>>>>>>>> confidential or proprietary in nature or covered by the provisions of
>>>>>>>> privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data
>>>>>>>> Protection Code).Any use not in accord with its purpose, any disclosure,
>>>>>>>> reproduction, copying, distribution, or either dissemination, either whole
>>>>>>>> or partial, is strictly forbidden except previous formal approval of the
>>>>>>>> named addressee(s). If you are not the intended recipient, please contact
>>>>>>>> immediately the sender by telephone, fax or e-mail and delete the
>>>>>>>> information in this message that has been received in error. The sender
>>>>>>>> does not give any warranty or accept liability as the content, accuracy or
>>>>>>>> completeness of sent messages and accepts no responsibility for changes
>>>>>>>> made after they were sent or for other risks which arise as a result of
>>>>>>>> e-mail transmission, viruses, etc.
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>
>>>>>>>> On Thu, Jul 7, 2016 at 4:09 PM, Daniel Berry <
>>>>>>>> dberry at boundlessgeo.com> wrote:
>>>>>>>>
>>>>>>>>> Alessio,
>>>>>>>>>
>>>>>>>>> I would think an issue and PR would be sufficient. We should add
>>>>>>>>> what new features or changes are included though.
>>>>>>>>>
>>>>>>>>> regarding the following
>>>>>>>>>
>>>>>>>>> "*We need boundless to fix geogig 2.9.x version which is
>>>>>>>>> currently broken. We need geogig JARs to be pushed on a public maven
>>>>>>>>> repository, otherwise GeoServer won't compile. Is there someone from
>>>>>>>>> boundless which can eventually help us with this task?"*
>>>>>>>>>
>>>>>>>>> We sure can, Erik Merkle is currently researching the level of
>>>>>>>>> effort for GeoGig 2.9.x extension. This would be great if we
>>>>>>>>> could include this in the GeoNode 2.5 release. Would you like to schedule a
>>>>>>>>> time to discuss?
>>>>>>>>>
>>>>>>>>> Respectfully,
>>>>>>>>>
>>>>>>>>> Daniel Berry
>>>>>>>>>
>>>>>>>>> On Thu, Jul 7, 2016 at 8:13 AM, Alessio Fabiani <
>>>>>>>>> alessio.fabiani at geo-solutions.it> wrote:
>>>>>>>>>
>>>>>>>>>> Dear all,
>>>>>>>>>>
>>>>>>>>>> I managed to succesfully update the geoserver-genode-ext to the
>>>>>>>>>> 2.9 version, but there are still two things to discuss:
>>>>>>>>>>
>>>>>>>>>> 1. Everyone is ok with this GeoServer version? Should we go
>>>>>>>>>> through a GNIP or an issue and PR are sufficient?
>>>>>>>>>>
>>>>>>>>>> 2. We need boulndless to fix geogig 2.9.x version which is
>>>>>>>>>> currently broken. We need geogid JARs to be pushed on a public maven
>>>>>>>>>> repository, otherwise GeoServer won't compile. Is there someone from
>>>>>>>>>> boundless which can eventually help us with this task?
>>>>>>>>>>
>>>>>>>>>> Best Regards,
>>>>>>>>>> Alessio Fabiani.
>>>>>>>>>>
>>>>>>>>>> ==
>>>>>>>>>> GeoServer Professional Services from the experts!
>>>>>>>>>> Visit http://goo.gl/it488V for more information.
>>>>>>>>>> ==
>>>>>>>>>>
>>>>>>>>>> Ing. Alessio Fabiani
>>>>>>>>>> @alfa7691
>>>>>>>>>> Founder/Technical Lead
>>>>>>>>>>
>>>>>>>>>> GeoSolutions S.A.S.
>>>>>>>>>> Via di Montramito 3/A
>>>>>>>>>> 55054 Massarosa (LU)
>>>>>>>>>> Italy
>>>>>>>>>> phone: +39 0584 962313
>>>>>>>>>> fax: +39 0584 1660272
>>>>>>>>>> mob: +39 331 6233686
>>>>>>>>>>
>>>>>>>>>> http://www.geo-solutions.it
>>>>>>>>>> http://twitter.com/geosolutions_it
>>>>>>>>>>
>>>>>>>>>> -------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>>>>>>>>>>
>>>>>>>>>> Le informazioni contenute in questo messaggio di posta
>>>>>>>>>> elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente
>>>>>>>>>> riservate. Il loro utilizzo è consentito esclusivamente al destinatario del
>>>>>>>>>> messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate
>>>>>>>>>> questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente
>>>>>>>>>> di darcene notizia via e-mail e di procedere alla distruzione del messaggio
>>>>>>>>>> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
>>>>>>>>>> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
>>>>>>>>>> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
>>>>>>>>>> principi dettati dal D.Lgs. 196/2003.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The information in this message and/or attachments, is intended
>>>>>>>>>> solely for the attention and use of the named addressee(s) and may be
>>>>>>>>>> confidential or proprietary in nature or covered by the provisions of
>>>>>>>>>> privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data
>>>>>>>>>> Protection Code).Any use not in accord with its purpose, any disclosure,
>>>>>>>>>> reproduction, copying, distribution, or either dissemination, either whole
>>>>>>>>>> or partial, is strictly forbidden except previous formal approval of the
>>>>>>>>>> named addressee(s). If you are not the intended recipient, please contact
>>>>>>>>>> immediately the sender by telephone, fax or e-mail and delete the
>>>>>>>>>> information in this message that has been received in error. The sender
>>>>>>>>>> does not give any warranty or accept liability as the content, accuracy or
>>>>>>>>>> completeness of sent messages and accepts no responsibility for changes
>>>>>>>>>> made after they were sent or for other risks which arise as a result of
>>>>>>>>>> e-mail transmission, viruses, etc.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> geonode-devel mailing list
>>>>>>>>>> geonode-devel at lists.osgeo.org
>>>>>>>>>> http://lists.osgeo.org/mailman/listinfo/geonode-devel
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Daniel Berry*
>>>>>>>>> Senior Software Engineer | Boundless
>>>>>>>>> dberry at boundlessgeo.com
>>>>>>>>> 512-468-3946 (cell)
>>>>>>>>> @boundlessgeo
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> geonode-devel mailing list
>>>>>>>> geonode-devel at lists.osgeo.org
>>>>>>>> http://lists.osgeo.org/mailman/listinfo/geonode-devel
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> geonode-devel mailing list
>>>>>>> geonode-devel at lists.osgeo.org
>>>>>>> http://lists.osgeo.org/mailman/listinfo/geonode-devel
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-devel/attachments/20160711/23c7ce13/attachment-0001.html>
More information about the geonode-devel
mailing list