Re: [Geoserver-devel] geofence spring-4-upgrade

Thanks, I will kick the build and run cite tests again. -- Jody Garnett On 18 April 2016 at 08:38, Andrea Aime wrote: > Hi Jody, > this is a well known intermittent failure, has been keeping us company for > years. > I've tried to fix it in the past, but never

Re: [Geoserver-devel] geofence spring-4-upgrade

Hi Jody, this is a well known intermittent failure, has been keeping us company for years. I've tried to fix it in the past, but never managed to reproduce it locally Cheers Andrea On Mon, Apr 18, 2016 at 5:31 PM, Jody Garnett wrote: > Although based on the log #2399 >

Re: [Geoserver-devel] geofence spring-4-upgrade

Although based on the log #2399 I cannot determine how your change would of broken the build - ests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.451 sec <<< FAILURE!

Re: [Geoserver-devel] geofence spring-4-upgrade

Sadly that commit has broken the build? I am prepared to release the last stable configuration prior to your commit - but I get the impression you would like to nail this down for the beta? version = 2.9-SNAPSHOT git revision = a378428ece7e22a9910648e45d4c01f5e6bd5a58 git branch = master build

Re: [Geoserver-devel] geofence spring-4-upgrade

Hi Ben, GeoFence 3.2.0 tagged and deployed: https://github.com/geoserver/geofence/commit/4e173c993cd4ac393321d1c89cf0dc958089d820 GeoServer dependency updated as needed: https://github.com/geoserver/geoserver/commit/c1782bd8e0b9d7e585aca8d15ec854f1e26a8101 Cheers, Emanuele Alle

Re: [Geoserver-devel] geofence spring-4-upgrade

Hello all, 2016-04-11 19:24 GMT+02:00 Niels Charlier : > Hello Damiano, > > I do use OpenLDAP. It seems to me that it definitely won't work without > the patch either. This box must simply always be checked with > ActiveDirectory. I think the thing to do here would be to give

Re: [Geoserver-devel] geofence spring-4-upgrade

Hello Damiano, I do use OpenLDAP. It seems to me that it definitely won't work without the patch either. This box must simply always be checked with ActiveDirectory. I think the thing to do here would be to give readable error feedback for the user. Regards Niels On 11-04-16 19:21, Damiano

Re: [Geoserver-devel] geofence spring-4-upgrade

Hi Niels, I tried to apply your patch and configure the auth provider with "Bind user before searching for groups" unchecked but I got an exception: org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is

Re: [Geoserver-devel] geofence spring-4-upgrade

Hey Simone and Damiano, You might want to apply my patch for LDAP first to solve a small issue I encountered while testing with OpenLDAP. The issue was that an exception was thrown when attempting to log on without having "Bind user before searching for groups" ticked. The reason was that it

Re: [Geoserver-devel] geofence spring-4-upgrade

Ciao Jody, as per the email he sent on the list, Damiano Giampaoli has been tasked to manual test active directory and cas (in that order). I am hoping to hear something about LDAP within tomorrow. Regards, Simone Giannecchini == GeoServer Professional Services from the experts! Visit

Re: [Geoserver-devel] geofence spring-4-upgrade

I still nobody doing rest api against docs? I am willing to work on that (or part of it). Regards Niels On 05-04-16 23:51, Jody Garnett wrote: You can always check the wiki page for latest testing status, put your initial next to

Re: [Geoserver-devel] geofence spring-4-upgrade

You can always check the wiki page for latest testing status, put your initial next to any open line item for testing. I had only short-listed on LDAP implementation for testing - Niels has been testing OpenLDAP - so testing of active

Re: [Geoserver-devel] geofence spring-4-upgrade

Hi Ben, > Would you > consider making a (for example) GeoFence 3.2.0 release and updating the > GeoServer modules to depend it before GeoServer 2.9-beta2? Sure, will do. Cheers, Emanuele Alle 22:27:54 di Tuesday 5 April 2016, Ben Caradoc-Davies ha scritto: > Emanuele, > > we discussed

Re: [Geoserver-devel] geofence spring-4-upgrade

Emanuele, we discussed the GeoFence SNAPSHOT dependency at today's committee meeting. As the GeoServer modules are community modules, there is no prohibition on SNAPSHOT dependencies, but we recommend using release dependencies to improve reproducibility and maintainability. Would you

Re: [Geoserver-devel] geofence spring-4-upgrade

Hi Jody, speaking of closer, what's the status of the other manual testing? Is there anything else you could use a helping hand on? E.g., CAS, LDAP against active directory? Cheers Andrea On Tue, Apr 5, 2016 at 7:07 PM, Jody Garnett wrote: > Thank you! Updating the

Re: [Geoserver-devel] geofence spring-4-upgrade

Thank you! Updating the wiki page based on your email - makes me feel like we are a lot closer. -- Jody Garnett On 5 April 2016 at 09:46, Emanuele Tajariol wrote: > At the time I wrote the mail, I was only referring to Jenkins building and > running tests successfully. >

Re: [Geoserver-devel] geofence spring-4-upgrade

Dear Jody, we have done also done a decent extent of manual testing. There is one thing which is pending, after the wicket upgrade we lost the drag and drop functionality for the geofence intergated GUI but we want it back asap but it's tricky. One of our guys, Nuno will follow up shortly on this

Re: [Geoserver-devel] geofence spring-4-upgrade

At the time I wrote the mail, I was only referring to Jenkins building and running tests successfully. We then performed some manual testing, both with GeoFence standalone, and with the embedded version, and both are behaving as they should. Cheers, Emanuele Alle 18:38:33 di Tuesday 5

Re: [Geoserver-devel] geofence spring-4-upgrade

When you say "quite satisfied" - do you mean mean it builds, or have you been in position to test. I am updating the wiki page and would like to know if the two geoserver community modules simply build, or if they pass tests. -- Jody Garnett On 31 March 2016 at 04:46, Emanuele Tajariol

Re: [Geoserver-devel] geofence spring-4-upgrade

Thanks, Emanuele. We will probably need a release of geofence for GeoServer 2.9-beta2 and later releases. I am not sure how strict we should be with community module dependencies. The committee should discuss at the meeting next week. Kind regards, Ben. On 01/04/16 00:46, Emanuele Tajariol

Re: [Geoserver-devel] geofence spring-4-upgrade

Hi, - branched geofence 3.1.x (Geoserver 2.8 depends on it) - merged the spring4 branch onto master - bumped geofence master to 3.2-SNAPSHOT - fixed the geofence deploy on ares (the jenkins job was not deploying the artifacts ) - bumped the geofence dep on geoserver to 3.2-SNAPSHOT Jenkins

Re: [Geoserver-devel] geofence spring-4-upgrade

On 31/03/16 11:51, Emanuele Tajariol wrote: >> The geoserver-master build now fails because the corresponding changes >> in the geofence 3.1-spring4 branch have not yet been merged: >> https://github.com/geoserver/geofence/tree/3.1-spring4 > Uhm... quite a big change anyway > I wonder if it's

Re: [Geoserver-devel] geofence spring-4-upgrade

> The geoserver-master build now fails because the corresponding changes > in the geofence 3.1-spring4 branch have not yet been merged: > https://github.com/geoserver/geofence/tree/3.1-spring4 Uhm... quite a big change anyway I wonder if it's the case to bump to version 3.2 for geofence.

Re: [Geoserver-devel] geofence spring-4-upgrade

On 31/03/16 05:59, Emanuele Tajariol wrote: >> Can you apply this fix to master and we can delete the spring-4-upgrade >> branch. > Sure, > here it is > > Cheers, > Emanuele The geoserver-master build

Re: [Geoserver-devel] geofence spring-4-upgrade

> Can you apply this fix to master and we can delete the spring-4-upgrade > branch. Sure, here it is Cheers, Emanuele Alle 17:51:16 di Wednesday 30 March 2016, Jody Garnett ha scritto: > That is

Re: [Geoserver-devel] geofence spring-4-upgrade

That is great Emanuele, hunting down your commit so we can all learn from it: On noes - you placed the commit on the spring-4-upgrade branch which has now been merged to master. Fix spring4 porting for geofence community modules

Re: [Geoserver-devel] geofence spring-4-upgrade

> tell that the REST module is broken. Just committed a fix for that. It seems that the @Produces annotations are a bit more picky now. Cheers, Emanuele Alle 13:58:54 di Wednesday 30 March 2016, Emanuele Tajariol ha scritto: > Hi, > > I created a branch for the porting of GeoFence to

Re: [Geoserver-devel] geofence spring-4-upgrade

Hi, I created a branch for the porting of GeoFence to Spring 4. You can find it here: https://github.com/geoserver/geofence/tree/3.1-spring4 I also committed some changes to the community modules to allow them to build properly:

Re: [Geoserver-devel] geofence spring-4-upgrade

Thanks Emanuele, Kevin and I have some time to help out - if we can be of assistance. I would like to merge the geoserver and geowebcache spring-4-update branches to master, can we do so today or will that disrupt your plans? -- Jody Garnett On 22 March 2016 at 03:34, Emanuele Tajariol

Re: [Geoserver-devel] geofence spring-4-upgrade

Hi Jody, I'm starting giving a look to the GeoFence migration to spring4. More on this once I understand better how much this upgrade will impact on the existing code and deps. Cheers, Emanuele Alle 00:03:40 di Tuesday 22 March 2016, Jody Garnett ha scritto: > I am not quite sure on how

Re: [Geoserver-devel] geofence spring-4-upgrade

The geofence codebase is split up into two projects, each with their own set of properties controlling version numbers: src/gui.pom.xml src/services/pom.xml