[Geoserver-devel] 2.6 release blocked, who can help?

GeoServer GeoServer Developer
1

Hi,
so Jody stated, in a deep enough nested thread that I fear nobody noticed,
that the 2.6-beta release is blocked, and he has no more time to work on it.

In a time boxed release model, and also given than in a month and a half
we should be releasing 2.6.0 at FOSS4G, this is a grave situation.

According to Jody:

  • the source build does not work
  • the installer fails on windows 7

Jody, I’ve looked at the builds and the artifacts, I see no build failures
(well, there is one in the groovy scripting extension, but has an easy fix, and does
not seem to interrupt the artifacts generation),
and the source files are here:

http://ares.boundlessgeo.com/geoserver/release/2.6-beta/geoserver-2.6-beta-src.zip

I had a quick look at the source file, it seems that the file contains
the core module sources, but not the extension file sources? Is that what you have
seen, or are there other issues?
I think this is hardly a blocker for a beta, and as far as I can see, it has
been like this forever, see for example:
http://sourceforge.net/projects/geoserver/files/GeoServer/2.5.1/geoserver-2.5.1-src.zip/download

http://sourceforge.net/projects/geoserver/files/GeoServer/2.4.0/geoserver-2.4.0-src.zip/download

http://sourceforge.net/projects/geoserver/files/GeoServer/2.3.0/geoserver-2.3.0-src.zip/download

So I’d just open a ticket to fix it, and move on.

About the windows installer, I’ve just tried the 2.6-beta installer on one of those Windows 7
VMs that Microsoft gives away to help people test the various versions of IE, where
I previously installed java 7, and indeed I’m getting permission issues.
However, I’ve removed the installer, and installed again with GeoServer running as a service,
and in that case it works fine.

I don’t see how is this specific to this release, I believe every other GeoServer
release has exactly the same issue, and we did not get one report about it on Jira
(http://jira.codehaus.org/issues/?jql=project%20%3D%20GEOS%20AND%20status%20%3D%20Open%20AND%20text%20~%20%22windows%22%20ORDER%20BY%20key%20DESC )
It should definitely be fixed, but I don’t see this as a blocker either, we should just tell
people to install as a service on Windows 7 for the time being and then find someone
that is proficient enough with Windows to fix the installer)

Jody, am I missing any other blocker?

Cheers
Andrea

–

==

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

==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

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

2

Thanks for starting a new thread Andrea, in the interest of time I did my own preflight testing.

The source download did not include pom.xml files and so on allowing a build, I expect the maven assembly for this artefact needs to be updated in response to our introduction of a “gs” prefix.

Contents of src folder:

community
extension
gs-gwc
gs-kml
gs-main
gs-ows
gs-platform
gs-rest
gs-restconfig
gs-security
gs-wcs
gs-wcs1_0
gs-wcs1_1
gs-wcs2_0
gs-wfs
gs-wms
pom.xml
VERSION.txt
web

I relied on this source download in the past in order to manually create a mac DMG.

···

Jody Garnett

On Wed, Jul 23, 2014 at 9:45 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi,
so Jody stated, in a deep enough nested thread that I fear nobody noticed,
that the 2.6-beta release is blocked, and he has no more time to work on it.

In a time boxed release model, and also given than in a month and a half
we should be releasing 2.6.0 at FOSS4G, this is a grave situation.

According to Jody:

  • the source build does not work
  • the installer fails on windows 7

Jody, I’ve looked at the builds and the artifacts, I see no build failures
(well, there is one in the groovy scripting extension, but has an easy fix, and does
not seem to interrupt the artifacts generation),
and the source files are here:

http://ares.boundlessgeo.com/geoserver/release/2.6-beta/geoserver-2.6-beta-src.zip

I had a quick look at the source file, it seems that the file contains
the core module sources, but not the extension file sources? Is that what you have
seen, or are there other issues?
I think this is hardly a blocker for a beta, and as far as I can see, it has
been like this forever, see for example:
http://sourceforge.net/projects/geoserver/files/GeoServer/2.5.1/geoserver-2.5.1-src.zip/download

http://sourceforge.net/projects/geoserver/files/GeoServer/2.4.0/geoserver-2.4.0-src.zip/download

http://sourceforge.net/projects/geoserver/files/GeoServer/2.3.0/geoserver-2.3.0-src.zip/download

So I’d just open a ticket to fix it, and move on.

About the windows installer, I’ve just tried the 2.6-beta installer on one of those Windows 7
VMs that Microsoft gives away to help people test the various versions of IE, where
I previously installed java 7, and indeed I’m getting permission issues.
However, I’ve removed the installer, and installed again with GeoServer running as a service,
and in that case it works fine.

I don’t see how is this specific to this release, I believe every other GeoServer
release has exactly the same issue, and we did not get one report about it on Jira
(http://jira.codehaus.org/issues/?jql=project%20%3D%20GEOS%20AND%20status%20%3D%20Open%20AND%20text%20~%20%22windows%22%20ORDER%20BY%20key%20DESC )
It should definitely be fixed, but I don’t see this as a blocker either, we should just tell
people to install as a service on Windows 7 for the time being and then find someone
that is proficient enough with Windows to fix the installer)

Jody, am I missing any other blocker?

Cheers
Andrea

–

==

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

==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

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

Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world’s largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds

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

3

On Wed, Jul 23, 2014 at 6:54 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

Thanks for starting a new thread Andrea, in the interest of time I did my
own preflight testing.

The source download did not include pom.xml files and so on allowing a
build, I expect the maven assembly for this artefact needs to be updated in
response to our introduction of a "gs" prefix.

Hmm... no, the prefixes are there in release/src.xml, and so is the
inclusion of the top level pom file... not sure what's
going on.
Justin, do you have a clue?

I relied on this source download in the past in order to manually create a
mac DMG.

Oh? I thought these were generated starting from the bin packages.

Btw, I've released 2.5.2 without the dmg, sure someone is going to complain,
but I don't think it's fair to block a release for the rest of the world
only because
there are issues on selected platforms, if the .war and .bin are working,
it should
be good enough, the rest should be treated as tickets to be fixed imho.

Cheers
Andrea

--

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

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

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

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

4

On Wed, Jul 23, 2014 at 7:01 PM, Andrea Aime <andrea.aime@anonymised.com>
wrote:

I relied on this source download in the past in order to manually create
a mac DMG.

Oh? I thought these were generated starting from the bin packages.

Confirmed, there is no need for the source package, the instructions speak
of using
the bin one:
https://github.com/geoserver/geoserver/tree/master/src/release/installer/mac
Seems pretty easy if one has a Mac and the bin file, a single script to run.

Cheers
Andrea

--

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

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

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

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

5

On Wed, Jul 23, 2014 at 7:01 PM, Andrea Aime <andrea.aime@anonymised.com>
wrote:

On Wed, Jul 23, 2014 at 6:54 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

Thanks for starting a new thread Andrea, in the interest of time I did my
own preflight testing.

The source download did not include pom.xml files and so on allowing a
build, I expect the maven assembly for this artefact needs to be updated in
response to our introduction of a "gs" prefix.

Hmm... no, the prefixes are there in release/src.xml, and so is the
inclusion of the top level pom file... not sure what's
going on.
Justin, do you have a clue?

Hey,
I've just tried running mvn assembly:attached (after running the -Prelease
build) on trunk,
and the generated src zip file does contain the main pom file:

aaime@anonymised.com:~/devel/git-gs/src/target/release/geoserver-2.6-SNAPSHOT$ ls
community gs-gwc gs-main gs-platform gs-restconfig gs-wcs
gs-wcs1_1 gs-wfs pom.xml web
extension gs-kml gs-ows gs-rest gs-security gs-wcs1_0
gs-wcs2_0 gs-wms VERSION.txt

Wondering why it does not in the release script.. investigating...

Cheers
Andrea

--

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

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

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

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

6

On Wed, Jul 23, 2014 at 7:12 PM, Andrea Aime <andrea.aime@anonymised.com>
wrote:

Hey,
I've just tried running mvn assembly:attached (after running the -Prelease
build) on trunk,
and the generated src zip file does contain the main pom file:

aaime@anonymised.com:~/devel/git-gs/src/target/release/geoserver-2.6-SNAPSHOT$ ls
community gs-gwc gs-main gs-platform gs-restconfig gs-wcs
gs-wcs1_1 gs-wfs pom.xml web
extension gs-kml gs-ows gs-rest gs-security gs-wcs1_0
gs-wcs2_0 gs-wms VERSION.txt

Wondering why it does not in the release script.. investigating...

Hey hey, wait a second, the geoserver-2.6-beta src zip does contain the pom
file??

aaime@anonymised.com:/tmp/geoserver-2.6-beta$ ls
community gs-gwc gs-main gs-platform gs-restconfig gs-wcs
gs-wcs1_1 gs-wfs pom.xml web
extension gs-kml gs-ows gs-rest gs-security gs-wcs1_0
gs-wcs2_0 gs-wms VERSION.txt

Ah, ok, now I see, the build does not work because the directories in the
src file have
the gs- prefix, whilst in the repository they do not have it, the packaging
script is
actually renaming them...

Cheers
Andrea

--

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

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

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

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

7

On Wed, Jul 23, 2014 at 7:17 PM, Andrea Aime <andrea.aime@anonymised.com>
wrote:

Ah, ok, now I see, the build does not work because the directories in the
src file have
the gs- prefix, whilst in the repository they do not have it, the
packaging script is
actually renaming them...

Ok, checked what geotools is doing (since it has the same layout and prefix)
and the assembly is just a lot simpler:

<assembly>
  <id>project</id>
  <formats>
    <format>zip</format>
  </formats>
  <fileSets>
    <fileSet>
      <directory>target</directory>
      <includes>
        <include>VERSION*</include>
      </includes>
    </fileSet>
    <fileSet>
      <directory>.</directory>
      <outputDirectory></outputDirectory>
      <useDefaultExcludes>true</useDefaultExcludes>
      <excludes>
        <exclude>**/target/**</exclude>
      </excludes>
    </fileSet>
  </fileSets>
</assembly>

We could do the same in GeoServer, that would solve the problem,
or, we could maybe stop overthinking it, and recognize github
is making a jolly good source zip for us, e.g. :
https://github.com/geoserver/geoserver/releases

zip and tar.gz of every tag, what's not to like?

We could just stop packaging the sources outselves, and point the download
links
to github.

What do you think?

Cheers
Andrea

--

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

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

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

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

8

On Wed, Jul 23, 2014 at 11:23 AM, Andrea Aime <andrea.aime@anonymised.com>
wrote:

On Wed, Jul 23, 2014 at 7:17 PM, Andrea Aime <andrea.aime@anonymised.com
> wrote:

Ah, ok, now I see, the build does not work because the directories in the
src file have
the gs- prefix, whilst in the repository they do not have it, the
packaging script is
actually renaming them...

Ok, checked what geotools is doing (since it has the same layout and
prefix)
and the assembly is just a lot simpler:

<assembly>
  <id>project</id>
  <formats>
    <format>zip</format>
  </formats>
  <fileSets>
    <fileSet>
      <directory>target</directory>
      <includes>
        <include>VERSION*</include>
      </includes>
    </fileSet>
    <fileSet>
      <directory>.</directory>
      <outputDirectory></outputDirectory>
      <useDefaultExcludes>true</useDefaultExcludes>
      <excludes>
        <exclude>**/target/**</exclude>
      </excludes>
    </fileSet>
  </fileSets>
</assembly>

We could do the same in GeoServer, that would solve the problem,
or, we could maybe stop overthinking it, and recognize github
is making a jolly good source zip for us, e.g. :
https://github.com/geoserver/geoserver/releases

zip and tar.gz of every tag, what's not to like?

We could just stop packaging the sources outselves, and point the download
links
to github.

What do you think?

I think this definitely makes the most sense. +1

Cheers
Andrea

--

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

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

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

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

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Justin Deoliveira
VP Engineering | Boundless <http://boundlessgeo.com/&gt;
jdeolive@anonymised.com
@boundlessgeo <http://twitter.com/boundlessgeo/&gt;

9

Sounds Good Andrea

Here is the file to change: https://github.com/geoserver/geoserver.github.io/blob/master/_layouts/release.html#L141

We already link to the tag a few lines down so it should be easy to do.

Jody

···

We could do the same in GeoServer, that would solve the problem,
or, we could maybe stop overthinking it, and recognize github
is making a jolly good source zip for us, e.g. :
https://github.com/geoserver/geoserver/releases

zip and tar.gz of every tag, what’s not to like?

We could just stop packaging the sources outselves, and point the download links
to github.

What do you think?

Cheers

Andrea

–

==

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

==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

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