[Geoserver-devel] geofence spring-4-upgrade

GeoServer GeoServer Developer
1

I am not quite sure on how we manage the geofence project, from the README I should take developer questions here.

I would like to start a spring-4-upgrade branch, coordinating with any interested developers here.

2

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 (has model and services-api as children)

I am not sure of the advantage of duplicating here, it does allow the codebase to produce two distinct projects with slightly different dependencies.

On the geoserver side the spring-4-upgrade branch has:

community/geofence/pom.xml

org.geoserver.geofence geofence-services-api ${gf.version} org.geoserver.geofence geofence-model ${gf.version}

community/geofence-server/pom.xml

org.geoserver.geofence geofence-services-impl ${gf.version}
···

–
Jody Garnett

On 21 March 2016 at 16:03, Jody Garnett <jody.garnett@anonymised.com> wrote:

I am not quite sure on how we manage the geofence project, from the README I should take developer questions here.

I would like to start a spring-4-upgrade branch, coordinating with any interested developers here.

–
Jody Garnett

3

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 we manage the geofence project, from the README
I should take developer questions here.

I would like to start a spring-4-upgrade branch, coordinating with any
interested developers here.

--

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

4

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?

···

On 22 March 2016 at 03:34, Emanuele Tajariol <etj@anonymised.com> wrote:

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 we manage the geofence project, from the README
I should take developer questions here.

I would like to start a spring-4-upgrade branch, coordinating with any
interested developers here.

–

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

–
Jody Garnett

5

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:
    https://github.com/geoserver/geoserver/commit/6014433cbe2fe2eeff2f4081863526ed1be8ca34

The normal build completes successfully, but the integration tests
(https://github.com/geoserver/geofence/wiki/Devs%3A-running-integration-tests)
tell that the REST module is broken.

The integration tests with geoserver (which tests the AccessManager performing
requests to geofence) are ok, but I have yet to test a real integration
running.

Posting news as soon as they are available.

   Cheers,
   Emanuele

Alle 11:34:52 di Tuesday 22 March 2016, Emanuele Tajariol ha scritto:

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 we manage the geofence project, from the
> README I should take developer questions here.
>
> I would like to start a spring-4-upgrade branch, coordinating with any
> interested developers here.

--

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

6

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 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:
   
https://github.com/geoserver/geoserver/commit/6014433cbe2fe2eeff2f40818635
26ed1be8ca34

The normal build completes successfully, but the integration tests
(https://github.com/geoserver/geofence/wiki/Devs%3A-running-integration-tes
ts) tell that the REST module is broken.

The integration tests with geoserver (which tests the AccessManager
performing requests to geofence) are ok, but I have yet to test a real
integration running.

Posting news as soon as they are available.

   Cheers,
   Emanuele

Alle 11:34:52 di Tuesday 22 March 2016, Emanuele Tajariol ha scritto:
> 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 we manage the geofence project, from the
> > README I should take developer questions here.
> >
> > I would like to start a spring-4-upgrade branch, coordinating with any
> > interested developers here.

--

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

7

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

Can you apply this fix to master and we can delete the spring-4-upgrade branch.

···

On 30 March 2016 at 07:43, Emanuele Tajariol <etj@anonymised.com> wrote:

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 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:

https://github.com/geoserver/geoserver/commit/6014433cbe2fe2eeff2f40818635
26ed1be8ca34

The normal build completes successfully, but the integration tests
(https://github.com/geoserver/geofence/wiki/Devs%3A-running-integration-tes
ts) tell that the REST module is broken.

The integration tests with geoserver (which tests the AccessManager
performing requests to geofence) are ok, but I have yet to test a real
integration running.

Posting news as soon as they are available.

Cheers,
Emanuele

Alle 11:34:52 di Tuesday 22 March 2016, Emanuele Tajariol ha scritto:

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 we manage the geofence project, from the
README I should take developer questions here.

I would like to start a spring-4-upgrade branch, coordinating with any
interested developers here.

–

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Jody Garnett

8

Can you apply this fix to master and we can delete the spring-4-upgrade
branch.

Sure,

here it is
<https://github.com/geoserver/geoserver/commit/9473b585770f068ec0c1374e68f19ddb13d8e8ef&gt;

   Cheers,
   Emanuele

Alle 17:51:16 di Wednesday 30 March 2016, Jody Garnett ha scritto:

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
<https://github.com/geoserver/geoserver/commit/6014433cbe2fe2eeff2f40818635
26ed1be8ca34>

Can you apply this fix to master and we can delete the spring-4-upgrade
branch.

--
Jody Garnett

On 30 March 2016 at 07:43, Emanuele Tajariol <etj@anonymised.com> wrote:
> > 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 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:
> https://github.com/geoserver/geoserver/commit/6014433cbe2fe2eeff2f4081863
> 5
>
> > 26ed1be8ca34
> >
> > The normal build completes successfully, but the integration tests
> > (
>
> https://github.com/geoserver/geofence/wiki/Devs%3A-running-integration-te
> s
>
> > ts) tell that the REST module is broken.
> >
> > The integration tests with geoserver (which tests the AccessManager
> > performing requests to geofence) are ok, but I have yet to test a real
> > integration running.
> >
> > Posting news as soon as they are available.
> >
> > Cheers,
> > Emanuele
> >
> > Alle 11:34:52 di Tuesday 22 March 2016, Emanuele Tajariol ha scritto:
> > > 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 we manage the geofence project, from the
> > > > README I should take developer questions here.
> > > >
> > > > I would like to start a spring-4-upgrade branch, coordinating with
>
> any
>
> > > > interested developers here.
>

--

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

9

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
<https://github.com/geoserver/geoserver/commit/9473b585770f068ec0c1374e68f19ddb13d8e8ef&gt;
    Cheers,
    Emanuele

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

Build failure:
http://ares.boundlessgeo.com/jenkins/job/geoserver-master/2346/changes

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

10

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.

Definitely we need a strategy for keeping the versions of GeoServer and
GeoFence somehow aligned.

   Cheers,
   Emanuele

Alle 00:00:34 di Thursday 31 March 2016, Ben Caradoc-Davies ha scritto:

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
> <https://github.com/geoserver/geoserver/commit/9473b585770f068ec0c1374e68
> f19ddb13d8e8ef>
>
> Cheers,
> Emanuele

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

Build failure:
http://ares.boundlessgeo.com/jenkins/job/geoserver-master/2346/changes

Kind regards,

--

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

11

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 the case to bump to version 3.2 for geofence.
Definitely we need a strategy for keeping the versions of GeoServer and
GeoFence somehow aligned.

I raised this issue when I noticed the snapshot dependency last year:
http://osgeo-org.1560.x6.nabble.com/a-bit-stuck-on-2-9-M0-release-td5242228.html

Jody wrote: "we do not need to stress until the beta :)". The beta is passed and beta2 approaches. Turn that smile upside down. :frowning:

We could build geofence releases into our release plan, which would allow more easy tracking of snapshots (like geowebcache), or you could make a geofence (for example) 3.1.0 release and the GeoServer community geofence modules could then depend on it. How often does geofence change? How active is development?

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

12

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 seems to be quite satisfied at the moment for both geofence-master and
geoserver-master :slight_smile:

   Cheers,
   Emanuele

Alle 00:51:39 di Thursday 31 March 2016, Emanuele Tajariol ha scritto:

> 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.

Definitely we need a strategy for keeping the versions of GeoServer and
GeoFence somehow aligned.

   Cheers,
   Emanuele

Alle 00:00:34 di Thursday 31 March 2016, Ben Caradoc-Davies ha scritto:
> 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
> > <https://github.com/geoserver/geoserver/commit/9473b585770f068ec0c1374e
> > 68 f19ddb13d8e8ef>
> >
> > Cheers,
> > Emanuele
>
> 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
>
> Build failure:
> http://ares.boundlessgeo.com/jenkins/job/geoserver-master/2346/changes
>
> Kind regards,

--

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

13

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 wrote:

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 seems to be quite satisfied at the moment for both geofence-master and
geoserver-master :slight_smile:

    Cheers,
    Emanuele

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

14

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.

···

On 31 March 2016 at 04:46, Emanuele Tajariol <etj@anonymised.com> wrote:

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 seems to be quite satisfied at the moment for both geofence-master and
geoserver-master :slight_smile:

Cheers,
Emanuele

Alle 00:51:39 di Thursday 31 March 2016, Emanuele Tajariol ha scritto:

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.

Definitely we need a strategy for keeping the versions of GeoServer and
GeoFence somehow aligned.

Cheers,
Emanuele

Alle 00:00:34 di Thursday 31 March 2016, Ben Caradoc-Davies ha scritto:

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
<https://github.com/geoserver/geoserver/commit/9473b585770f068ec0c1374e
68 f19ddb13d8e8ef>

Cheers,
Emanuele

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

Build failure:
http://ares.boundlessgeo.com/jenkins/job/geoserver-master/2346/changes

Kind regards,

–

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Jody Garnett

15

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 April 2016, Jody Garnett ha scritto:

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 <etj@anonymised.com> wrote:
> 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 seems to be quite satisfied at the moment for both
> geofence-master and
> geoserver-master :slight_smile:
>
> Cheers,
> Emanuele
>
> Alle 00:51:39 di Thursday 31 March 2016, Emanuele Tajariol ha scritto:
> > > 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.
> >
> > Definitely we need a strategy for keeping the versions of GeoServer and
> > GeoFence somehow aligned.
> >
> > Cheers,
> > Emanuele
> >
> > Alle 00:00:34 di Thursday 31 March 2016, Ben Caradoc-Davies ha scritto:
> > > 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
> > > > <
>
> https://github.com/geoserver/geoserver/commit/9473b585770f068ec0c1374e
>
> > > > 68 f19ddb13d8e8ef>
> > > >
> > > > Cheers,
> > > > Emanuele
> > >
> > > 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
> > >
> > > Build failure:
> > > http://ares.boundlessgeo.com/jenkins/job/geoserver-master/2346/change
> > > s
> > >
> > > Kind regards,
>
> --
> ==
> GeoServer Professional Services from the experts!
> Visit http://goo.gl/NWWaa2 for more information.
> ==
>
> Ing. Emanuele Tajariol
> 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 380 2116282
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
>
> -------------------------------------------------------------------------
> ----- Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

16

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 (it will open a
separate thread).

Regards,
Simone Giannecchini

GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

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 Tue, Apr 5, 2016 at 6:38 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

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 <etj@anonymised.com> wrote:

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 seems to be quite satisfied at the moment for both geofence-master
and
geoserver-master :slight_smile:

   Cheers,
   Emanuele

Alle 00:51:39 di Thursday 31 March 2016, Emanuele Tajariol ha scritto:
> > 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.
>
> Definitely we need a strategy for keeping the versions of GeoServer and
> GeoFence somehow aligned.
>
> Cheers,
> Emanuele
>
> Alle 00:00:34 di Thursday 31 March 2016, Ben Caradoc-Davies ha scritto:
> > 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
> > >
> > > <https://github.com/geoserver/geoserver/commit/9473b585770f068ec0c1374e
> > > 68 f19ddb13d8e8ef>
> > >
> > > Cheers,
> > > Emanuele
> >
> > 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
> >
> > Build failure:
> > http://ares.boundlessgeo.com/jenkins/job/geoserver-master/2346/changes
> >
> > Kind regards,

--

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

------------------------------------------------------------------------------

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

17

Thank you! Updating the wiki page based on your email - makes me feel like we are a lot closer.

···

On 5 April 2016 at 09:46, Emanuele Tajariol <etj@anonymised.com> wrote:

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 April 2016, Jody Garnett ha scritto:

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 <etj@anonymised.com> wrote:

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 seems to be quite satisfied at the moment for both
geofence-master and
geoserver-master :slight_smile:

Cheers,
Emanuele

Alle 00:51:39 di Thursday 31 March 2016, Emanuele Tajariol ha scritto:

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.

Definitely we need a strategy for keeping the versions of GeoServer and
GeoFence somehow aligned.

Cheers,
Emanuele

Alle 00:00:34 di Thursday 31 March 2016, Ben Caradoc-Davies ha scritto:

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
<

https://github.com/geoserver/geoserver/commit/9473b585770f068ec0c1374e

68 f19ddb13d8e8ef>

Cheers,
Emanuele

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

Build failure:
http://ares.boundlessgeo.com/jenkins/job/geoserver-master/2346/change
s

Kind regards,

–

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

----- Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

–
Jody Garnett

18

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 <jody.garnett@anonymised.com> wrote:

Thank you! Updating the wiki page based on your email - makes me feel like we are a lot closer.

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

–
Jody Garnett

On 5 April 2016 at 09:46, Emanuele Tajariol <etj@anonymised.com> wrote:

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 April 2016, Jody Garnett ha scritto:

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 <etj@anonymised.com> wrote:

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 seems to be quite satisfied at the moment for both
geofence-master and
geoserver-master :slight_smile:

Cheers,
Emanuele

Alle 00:51:39 di Thursday 31 March 2016, Emanuele Tajariol ha scritto:

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.

Definitely we need a strategy for keeping the versions of GeoServer and
GeoFence somehow aligned.

Cheers,
Emanuele

Alle 00:00:34 di Thursday 31 March 2016, Ben Caradoc-Davies ha scritto:

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
<

https://github.com/geoserver/geoserver/commit/9473b585770f068ec0c1374e

68 f19ddb13d8e8ef>

Cheers,
Emanuele

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

Build failure:
http://ares.boundlessgeo.com/jenkins/job/geoserver-master/2346/change
s

Kind regards,

–

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

----- Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

==
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

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.

19

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 consider making a (for example) GeoFence 3.2.0 release and updating the GeoServer modules to depend it before GeoServer 2.9-beta2?

Kind regards,
Ben.

On 01/04/16 10:03, Ben Caradoc-Davies wrote:

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 wrote:

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 seems to be quite satisfied at the moment for both geofence-master and
geoserver-master :slight_smile:

     Cheers,
     Emanuele

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

20

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 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
consider making a (for example) GeoFence 3.2.0 release and updating the
GeoServer modules to depend it before GeoServer 2.9-beta2?

Kind regards,
Ben.

On 01/04/16 10:03, Ben Caradoc-Davies wrote:
> 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.
>

--

GeoServer Professional Services from the experts!
Visit http://goo.gl/NWWaa2 for more information.

Ing. Emanuele Tajariol
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 380 2116282

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------