[GeoNode-devel] GeoNode 2.4 status

Thu Jun 25 09:07:28 PDT 2015

Yep. You have to edit here and then publish. We really should change
the way this is setup and move to jekyll so its published
automatically on github with no extra steps. Anyone want to volunteer
to do some repo work here?

https://github.com/GeoNode/geonode.github.com/blob/master/pages/gallery/index.html

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