<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Jeffrey,<div><br></div><div>are you referring to this repo <a href="https://github.com/GeoNode/geonode.github.com">https://github.com/GeoNode/geonode.github.com</a> ?</div><div><br></div><div>F.<br><div><div>Il giorno 25/giu/2015, alle ore 17:37, Jeffrey Johnson <<a href="mailto:ortelius@gmail.com">ortelius@gmail.com</a>> ha scritto:</div><br class="Apple-interchange-newline"><blockquote type="cite">Francesco (or anyone else), I wonder if you can send a Pull request<br>against the website to add to the gallery here<br><a href="http://geonode.org/gallery/">http://geonode.org/gallery/</a><br><br>On Thu, Jun 25, 2015 at 8:12 AM, Francesco Bartoli <xbartolone@gmail.com> wrote:<br><blockquote type="cite">Ciao Ariel,<br><br>yes I am :). I’m going to launch SDI for snow avalanche information<br>(http://geoavalanche.org) on top of GeoNode<br><br>F.<br><br>Il giorno 25/giu/2015, alle ore 17:00, Ariel Nunez<br><ingenieroariel@gmail.com> ha scritto:<br><br>Ciao Francesco,<br><br>Thanks for looking into this, are you the same Francesco that is behind<br>GeoBeyond? I have seen some of your writing when reading about open source<br>geo in italy.<br><br>Buon hacking,<br>-a<br><br>On Thu, Jun 25, 2015 at 8:59 AM, Francesco Bartoli <xbartolone@gmail.com><br>wrote:<br><blockquote type="cite"><br>Hi,<br><br>just a quick update. I find out the reason of failure:<br><br>Class GeoserverDataDirectory [1] is no longer present in the package<br>org.vfny.geoserver.global [2] and should be replaced by<br>GeoServerResourceLoader [3]<br><br>I’ll try to rebuild as soon as I can with this modifications<br><br>Francesco<br><br>[1]<br>https://github.com/GeoNode/geoserver-geonode-ext/blob/master/src/main/java/org/geonode/security/GeoNodeSecurityProvider.java#L85<br><br>[2]<br>https://github.com/geoserver/geoserver/tree/2.7.x/src/main/src/main/java/org/vfny/geoserver/global<br><br>[3]<br>https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/config/GeoServerDataDirectory.java#L64<br><br><br>Il giorno 25/giu/2015, alle ore 02:42, Francesco Bartoli<br><xbartolone@gmail.com> ha scritto:<br><br>Hi Paolo,<br><br>I have tried to upgrade geoserver-geonode-ext with alignment to the latest<br>stable 2.7.1. After minor issues in dependencies the build fails at this<br>point:<br><br>[ERROR] Failed to execute goal<br>org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile)<br>on project geonode-geoserver-ext: Compilation failure: Compilation failure:<br>[ERROR]<br>/Users/geobart/Development/geoserver-geonode-ext/src/main/java/org/geonode/security/GeoNodeSecurityProvider.java:[18,33]<br>cannot find symbol<br>[ERROR] symbol: class GeoserverDataDirectory<br>[ERROR] location: package org.vfny.geoserver.global<br>[ERROR]<br>/Users/geobart/Development/geoserver-geonode-ext/src/main/java/org/geonode/security/GeoNodeSecurityProvider.java:[85,44]<br>cannot find symbol<br>[ERROR] symbol: variable GeoserverDataDirectory<br>[ERROR] location: class org.geonode.security.GeoNodeSecurityProvider<br>[ERROR] -> [Help 1]<br>org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute<br>goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile<br>(default-compile) on project geonode-geoserver-ext: Compilation failure<br>at<br>org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)<br>at<br>org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)<br>at<br>org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)<br>at<br>org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)<br>at<br>org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)<br>at<br>org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)<br>at<br>org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)<br>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)<br>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)<br>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)<br>at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)<br>at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)<br>at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)<br>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)<br>at<br>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)<br>at<br>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)<br>at java.lang.reflect.Method.invoke(Method.java:606)<br>at<br>org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)<br>at<br>org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)<br>at<br>org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)<br>at<br>org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)<br>Caused by: org.apache.maven.plugin.compiler.CompilationFailureException:<br>Compilation failure<br>at<br>org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:858)<br>at<br>org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)<br>at<br>org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)<br>at<br>org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)<br>... 20 more<br>[ERROR]<br>[ERROR] Re-run Maven using the -X switch to enable full debug logging.<br>[ERROR]<br>[ERROR] For more information about the errors and possible solutions,<br>please read the following articles:<br>[ERROR] [Help 1]<br>http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException<br><br>Tomorrow I don’t have time to investigating more but if somebody can take<br>a look then I can retry the build. Anyway attached there is the POM used to<br>build<br><br>Cheers,<br>Francesco<br><pom.xml><br><br>Il giorno 24/giu/2015, alle ore 15:47, Paolo Corti <pcorti@gmail.com> ha<br>scritto:<br><br>Hi Simone<br><br>There are also a couple of other things that can be addressed before the<br>release if they are fixed in time otherwise will go to 2.4.1:<br>- notifications rework<br>- better cache management and invalidation for thumbnails and tiles<br>- Geoserver upgrade to 2.7<br><br><br>We should upgrade asap GeoServer as this recently discovered important<br>security vulnerability has been fixed only for 2.6.4 and 2.7.2 (we<br>should consider to repackage GeoServer for stable 2.0 imho):<br>https://osgeo-org.atlassian.net/browse/GEOS-7032<br><br>For the rest, migrations script [1] worked well for us (WFP), we are<br>extensively testing it and will go in production with 2.4 by the end<br>of the month.<br><br>Another think I would love to see in 2.4 is the gxp classify tool,<br>almost done by Matt I believe [2]<br><br>cheers<br>p<br><br>[1] https://github.com/capooti/geonode/tree/migration_from20_to_24<br>[2] https://github.com/boundlessgeo/gxp/pull/231/files#r31339623<br><br>--<br>Paolo Corti<br>Geospatial software developer<br>web: http://www.paolocorti.net<br>twitter: @capooti<br>skype: capooti<br>_______________________________________________<br>geonode-devel mailing list<br>geonode-devel@lists.osgeo.org<br>http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-devel<br><br><br><br><br>_______________________________________________<br>geonode-devel mailing list<br>geonode-devel@lists.osgeo.org<br>http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-devel<br><br></blockquote><br><br><br>_______________________________________________<br>geonode-devel mailing list<br>geonode-devel@lists.osgeo.org<br>http://lists.osgeo.org/cgi-bin/mailman/listinfo/geonode-devel<br><br></blockquote></blockquote></div><br></div></body></html>