[Geoserver-devel] Nightly builds now -Xmx2048m

GeoServer GeoServer Developer
1

I increased the nightly build heap to -Xmx2048m to fix them. I usually need this flag to build -PcommunityRelease locally. It does seem excessive.

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

2

On Fri, Mar 18, 2016 at 1:40 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

I increased the nightly build heap to -Xmx2048m to fix them. I usually
need this flag to build -PcommunityRelease locally. It does seem excessive.

Wow yeah it does. Thanks for fixing the nightly builds.

Do you have any clue as to why it's going OOM, and if any particular module
is responsible for that?

Cheers
Andrea

--

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.

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

3

On 18/03/16 21:05, Andrea Aime wrote:

On Fri, Mar 18, 2016 at 1:40 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

I increased the nightly build heap to -Xmx2048m to fix them. I usually
need this flag to build -PcommunityRelease locally. It does seem excessive.

Wow yeah it does. Thanks for fixing the nightly builds.
Do you have any clue as to why it's going OOM, and if any particular module
is responsible for that?

Sorry, no idea. Perhaps it is related to running four concurrent build threads? Community modules are a more independent of each other so they might be more likely to build in parallel. In each thread javac may need to load most of the project into its classpath. Does maven-compiler-plugin use a separate classloader for each thread? But we fork javac so how can it be to blame? I also have the horrible feeling that jar collection is performed in memory. It is not the tests failing as these are a forked subprocess and we see OOME when building with -DskipTests -PcommunityRelease.

I will try a build with -X and see if I can spot the culprit.

Kind regards,

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

4

On 20/03/16 11:10, Ben Caradoc-Davies wrote:

I will try a build with -X and see if I can spot the culprit.

Concurrent git-commit-id-plugin looks like the culprit. Local tests suggest upgrading from 2.0.4 to 2.2.0 (with major jgit dependency version upgrade) fixes the problem.

Kind regards,
Ben.

[INFO] --- git-commit-id-plugin:2.0.4:revision (default) @ gs-jdbcstore ---
[DEBUG] Configuring mojo pl.project13.maven:git-commit-id-plugin:2.0.4:revision from plugin realm ClassRealm[plugin>pl.project13.maven:git-commit-id-plugin:2.0.4, parent: sun.misc.Launcher$AppClassLoader@anonymised.com]
[DEBUG] Configuring mojo 'pl.project13.maven:git-commit-id-plugin:2.0.4:revision' with basic configurator -->
[DEBUG] (s) dateFormat = dd.MM.yyyy '@' HH:mm:ss z
[ERROR] GC overhead limit exceeded -> [Help 1]
java.lang.OutOfMemoryError: GC overhead limit exceeded
  at org.eclipse.jgit.storage.file.PackIndexV2.<init>(PackIndexV2.java:130)
  at org.eclipse.jgit.storage.file.PackIndex.read(PackIndex.java:137)
  at org.eclipse.jgit.storage.file.PackIndex.open(PackIndex.java:96)
  at org.eclipse.jgit.storage.file.PackFile.idx(PackFile.java:159)
  at org.eclipse.jgit.storage.file.PackFile.get(PackFile.java:226)
  at org.eclipse.jgit.storage.file.ObjectDirectory.openObject1(ObjectDirectory.java:439)
  at org.eclipse.jgit.storage.file.FileObjectDatabase.openObjectImpl1(FileObjectDatabase.java:183)
  at org.eclipse.jgit.storage.file.FileObjectDatabase.openObject(FileObjectDatabase.java:157)
  at org.eclipse.jgit.storage.file.WindowCursor.open(WindowCursor.java:122)
  at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:228)
  at org.eclipse.jgit.revwalk.RevWalk.parseAny(RevWalk.java:811)
  at org.eclipse.jgit.revwalk.RevWalk.parseCommit(RevWalk.java:724)
  at pl.project13.maven.git.GitCommitIdMojo.loadGitData(GitCommitIdMojo.java:284)
  at pl.project13.maven.git.GitCommitIdMojo.execute(GitCommitIdMojo.java:170)
  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
  at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
  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.MojoExecutor.executeForkedExecutions(MojoExecutor.java:352)
  at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:197)
  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.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
  at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:181)
  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  at java.lang.Thread.run(Thread.java:745)
[ERROR] java.lang.OutOfMemoryError: GC overhead limit exceeded
java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: GC overhead limit exceeded
  at java.util.concurrent.FutureTask.report(FutureTask.java:122)
  at java.util.concurrent.FutureTask.get(FutureTask.java:192)
  at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.multiThreadedProjectTaskSegmentBuild(MultiThreadedBuilder.java:130)
  at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder.build(MultiThreadedBuilder.java:91)
  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:863)
  at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
  at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:498)
  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: java.lang.OutOfMemoryError: GC overhead limit exceeded
  at org.eclipse.jgit.storage.file.PackIndexV2.<init>(PackIndexV2.java:130)
  at org.eclipse.jgit.storage.file.PackIndex.read(PackIndex.java:137)
  at org.eclipse.jgit.storage.file.PackIndex.open(PackIndex.java:96)
  at org.eclipse.jgit.storage.file.PackFile.idx(PackFile.java:159)
  at org.eclipse.jgit.storage.file.PackFile.get(PackFile.java:226)
  at org.eclipse.jgit.storage.file.ObjectDirectory.openObject1(ObjectDirectory.java:439)
  at org.eclipse.jgit.storage.file.FileObjectDatabase.openObjectImpl1(FileObjectDatabase.java:183)
  at org.eclipse.jgit.storage.file.FileObjectDatabase.openObject(FileObjectDatabase.java:157)
  at org.eclipse.jgit.storage.file.WindowCursor.open(WindowCursor.java:122)
  at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:228)
  at org.eclipse.jgit.revwalk.RevWalk.parseAny(RevWalk.java:811)
  at org.eclipse.jgit.revwalk.RevWalk.parseCommit(RevWalk.java:724)
  at pl.project13.maven.git.GitCommitIdMojo.loadGitData(GitCommitIdMojo.java:284)
  at pl.project13.maven.git.GitCommitIdMojo.execute(GitCommitIdMojo.java:170)
  at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
  at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
  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.MojoExecutor.executeForkedExecutions(MojoExecutor.java:352)
  at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:197)
  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.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:185)
  at org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:181)
  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  at java.lang.Thread.run(Thread.java:745)
[DEBUG] (s) dotGitDirectory = /home/ben/geoserver/src with spaces/geoserver/src/community/jdbcstore/.git
[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/OutOfMemoryError
[DEBUG] (f) failOnNoGitDirectory = false
[DEBUG] (f) generateGitPropertiesFile = false
[DEBUG] (f) generateGitPropertiesFilename = src/main/resources/git.properties
[DEBUG] (s) prefix = build
[DEBUG] (f) project = MavenProject: org.geoserver.community:gs-jdbcstore:2.9-SNAPSHOT @ /home/ben/geoserver/src with spaces/geoserver/src/community/jdbcstore/pom.xml
[DEBUG] (f) skipPoms = false
[DEBUG] (s) verbose = false
[DEBUG] -- end configuration --
[INFO] [GitCommitIdMojo] Running on '/home/ben/geoserver/src with spaces/geoserver/.git' repository...
[INFO] [GitCommitIdMojo] Initializing properties...
[INFO] [GitCommitIdMojo] Using maven project properties...
[INFO] [GitCommitIdMojo] Loading data from git repository...
[INFO] [GitCommitIdMojo] ------------------git properties loaded------------------
[INFO] [GitCommitIdMojo] build.commit.message.short = [GEOS-7444] Handle unmarshalling of GridGeometry2D objects when the JSON/XML definition follows an arbitrary order
[INFO] [GitCommitIdMojo] build.build.user.email = ben@anonymised.com
[INFO] [GitCommitIdMojo] build.hudsonId = -1
[INFO] [GitCommitIdMojo] build.commit.time = 20.03.2016 @ 03:21:31 NZDT
[INFO] [GitCommitIdMojo] build.timestamp = 19-Mar-2016 22:10
[INFO] [GitCommitIdMojo] build.build.time = 20.03.2016 @ 11:15:52 NZDT
[INFO] [GitCommitIdMojo] build.branch = master
[INFO] [GitCommitIdMojo] build.commit.user.email = cesar.izq@anonymised.com
[INFO] [GitCommitIdMojo] build.build.user.name = Ben Caradoc-Davies
[INFO] [GitCommitIdMojo] build.commit.user.name = dispiste
[INFO] [GitCommitIdMojo] build.commit.id.abbrev = 8f02d32
[INFO] [GitCommitIdMojo] build.commit.id = 8f02d3218a535183a1cfee59dbda37457a8541d9
[INFO] [GitCommitIdMojo] build.commit.message.full = [GEOS-7444] Handle unmarshalling of GridGeometry2D objects when the JSON/XML definition follows an arbitrary order

[INFO] [GitCommitIdMojo] ---------------------------------------------------------
[INFO] [GitCommitIdMojo] Finished running.
[INFO]
[INFO] <<< maven-source-plugin:2.2.1:test-jar (attach-sources) < generate-sources @ gs-jdbcstore <<<
[INFO]
[INFO] --- maven-source-plugin:2.2.1:test-jar (attach-sources) @ gs-jdbcstore ---
[DEBUG] Configuring mojo org.apache.maven.plugins:maven-source-plugin:2.2.1:test-jar from plugin realm ClassRealm[plugin>org.apache.maven.plugins:maven-source-plugin:2.2.1, parent: sun.misc.Launcher$AppClassLoader@anonymised.com]
Destroying 2 processes
Destroying process..
Destroyed 2 processes

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

5

OK, so I have broken all the builds (master, 2.8.x, and 2.7.x). We can either:

(1) upgrade ares to Maven 3.1.1 or later (requires Boundless assistance (I use and recommend Maven 3.3.9 (latest stable))), or

(2) downgrade git-commit-id-plugin to 2.0.4 and build nightlies with -Xmx2048m

No good deed goes unpunished.

Kind regards,
Ben.

On 20/03/16 11:52, Ben Caradoc-Davies wrote:

Concurrent git-commit-id-plugin looks like the culprit. Local tests
suggest upgrading from 2.0.4 to 2.2.0 (with major jgit dependency
version upgrade) fixes the problem.

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

6

Ooh, I broke GeoSolutions (Maven 3.0.5) as well. Sorry about that.

Would you guys prefer to upgrade Maven (and make Maven 3.1.1+ a hard requirement) or should I revert my pom changes?

Kind regards,
Ben.

On 20/03/16 12:24, Ben Caradoc-Davies wrote:

OK, so I have broken all the builds (master, 2.8.x, and 2.7.x). We can
either:

(1) upgrade ares to Maven 3.1.1 or later (requires Boundless assistance
(I use and recommend Maven 3.3.9 (latest stable))), or

(2) downgrade git-commit-id-plugin to 2.0.4 and build nightlies with
-Xmx2048m

No good deed goes unpunished.

Kind regards,
Ben.

On 20/03/16 11:52, Ben Caradoc-Davies wrote:

Concurrent git-commit-id-plugin looks like the culprit. Local tests
suggest upgrading from 2.0.4 to 2.2.0 (with major jgit dependency
version upgrade) fixes the problem.

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

7

An alternative is to downgrade git-commit-id-plugin to a 2.1.x that works with Maven 3.0.x, if such a version exists.

Kind regards,
Ben.

On 20/03/16 12:58, Ben Caradoc-Davies wrote:

Ooh, I broke GeoSolutions (Maven 3.0.5) as well. Sorry about that.

Would you guys prefer to upgrade Maven (and make Maven 3.1.1+ a hard
requirement) or should I revert my pom changes?

Kind regards,
Ben.

On 20/03/16 12:24, Ben Caradoc-Davies wrote:

OK, so I have broken all the builds (master, 2.8.x, and 2.7.x). We can
either:

(1) upgrade ares to Maven 3.1.1 or later (requires Boundless assistance
(I use and recommend Maven 3.3.9 (latest stable))), or

(2) downgrade git-commit-id-plugin to 2.0.4 and build nightlies with
-Xmx2048m

No good deed goes unpunished.

Kind regards,
Ben.

On 20/03/16 11:52, Ben Caradoc-Davies wrote:

Concurrent git-commit-id-plugin looks like the culprit. Local tests
suggest upgrading from 2.0.4 to 2.2.0 (with major jgit dependency
version upgrade) fixes the problem.

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

8

Chris can we update maven for Ben? Andrea also has ssh access.

On Sat, Mar 19, 2016 at 5:35 PM Ben Caradoc-Davies <ben@anonymised.com> wrote:

An alternative is to downgrade git-commit-id-plugin to a 2.1.x that
works with Maven 3.0.x, if such a version exists.

Kind regards,
Ben.

On 20/03/16 12:58, Ben Caradoc-Davies wrote:

Ooh, I broke GeoSolutions (Maven 3.0.5) as well. Sorry about that.

Would you guys prefer to upgrade Maven (and make Maven 3.1.1+ a hard
requirement) or should I revert my pom changes?

Kind regards,
Ben.

On 20/03/16 12:24, Ben Caradoc-Davies wrote:

OK, so I have broken all the builds (master, 2.8.x, and 2.7.x). We can
either:

(1) upgrade ares to Maven 3.1.1 or later (requires Boundless assistance
(I use and recommend Maven 3.3.9 (latest stable))), or

(2) downgrade git-commit-id-plugin to 2.0.4 and build nightlies with
-Xmx2048m

No good deed goes unpunished.

Kind regards,
Ben.

On 20/03/16 11:52, Ben Caradoc-Davies wrote:

Concurrent git-commit-id-plugin looks like the culprit. Local tests
suggest upgrading from 2.0.4 to 2.2.0 (with major jgit dependency
version upgrade) fixes the problem.

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

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=278785231&iu=/4140

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

–

–
Jody Garnett

9

Testing (a bisection search) indicates that git-commit-id-plugin 2.1.13 is the most recent version that is compatible with Maven 3.0.4.

I am running a build to see if this version fixes the -PcommunityRelease build. I am hopeful as it also should get the new jgit major version (same as 2.2.0).

If the build succeeds I will immediately push to 2.8.x and kick 2.8.x, 2.8.x nightly, and 2.8.x cite so Andrea has a working build for release. I will also push to 2.7.x and master.

Kind regards,
Ben.

On 20/03/16 13:33, Ben Caradoc-Davies wrote:

An alternative is to downgrade git-commit-id-plugin to a 2.1.x that
works with Maven 3.0.x, if such a version exists.

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

10

Thanks, Jody. An upgrade later this week would be welcome.

Chris, please wait for Andrea's feedback as he is making the GeoTools 14.3 and GeoServer 2.8.3 releases today and a Maven upgrade may interrupt this process.

We also need community agreement that we require Maven 3.1.1 or later as GeoServer currently builds with 3.0.4.

Kind regards,
Ben.

On 20/03/16 18:18, Jody Garnett wrote:

Chris can we update maven for Ben? Andrea also has ssh access.

On Sat, Mar 19, 2016 at 5:35 PM Ben Caradoc-Davies <ben@anonymised.com> wrote:

An alternative is to downgrade git-commit-id-plugin to a 2.1.x that
works with Maven 3.0.x, if such a version exists.

Kind regards,
Ben.

On 20/03/16 12:58, Ben Caradoc-Davies wrote:

Ooh, I broke GeoSolutions (Maven 3.0.5) as well. Sorry about that.

Would you guys prefer to upgrade Maven (and make Maven 3.1.1+ a hard
requirement) or should I revert my pom changes?

Kind regards,
Ben.

On 20/03/16 12:24, Ben Caradoc-Davies wrote:

OK, so I have broken all the builds (master, 2.8.x, and 2.7.x). We can
either:

(1) upgrade ares to Maven 3.1.1 or later (requires Boundless assistance
(I use and recommend Maven 3.3.9 (latest stable))), or

(2) downgrade git-commit-id-plugin to 2.0.4 and build nightlies with
-Xmx2048m

No good deed goes unpunished.

Kind regards,
Ben.

On 20/03/16 11:52, Ben Caradoc-Davies wrote:

Concurrent git-commit-id-plugin looks like the culprit. Local tests
suggest upgrading from 2.0.4 to 2.2.0 (with major jgit dependency
version upgrade) fixes the problem.

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

------------------------------------------------------------------------------
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=278785231&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

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

11

Done.

On 20/03/16 19:38, Ben Caradoc-Davies wrote:

If the build succeeds I will immediately push to 2.8.x and kick 2.8.x,
2.8.x nightly, and 2.8.x cite so Andrea has a working build for release.
I will also push to 2.7.x and master.

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

12

The build server is still a wall of red… oh well, in the meantime I have one GML
related fix to make (regression due to the fast GML encoder, it can be turned off
with a system variable of course, but still, the default config won’t work for 3D data).

Let’s see if the build server recovers in the meantime, if not, I may not be able to
work on the release until the next weekend (aka Easter).

Cheers
Andrea

···

On Sun, Mar 20, 2016 at 7:52 AM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Done.

On 20/03/16 19:38, Ben Caradoc-Davies wrote:

If the build succeeds I will immediately push to 2.8.x and kick 2.8.x,
2.8.x nightly, and 2.8.x cite so Andrea has a working build for release.
I will also push to 2.7.x and master.

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

–

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

13

There is a queue but they should be back soon. 2.8.x nightly failed with a weird gs-params-extractor dependency error I have not seen before:

[ERROR] Failed to execute goal on project gs-params-extractor: Could not resolve dependencies for project org.geoserver.community:gs-params-extractor:jar:2.8-SNAPSHOT: The following artifacts could not be resolved: org.wicketstuff:htmlvalidator:jar:1.2, javax.media:jai_core:jar:1.1.3, javax.media:jai_codec:jar:1.1.3, javax.media:jai_imageio:jar:1.1: Could not find artifact org.wicketstuff:htmlvalidator:jar:1.2 in central (http://repo.maven.apache.org/maven2) -> [Help 1]

Ideas? I do not see how this could be related to my *cough* improvements.

Kind regards,
Ben.

On 20/03/16 21:25, Andrea Aime wrote:

The build server is still a wall of red... oh well, in the meantime I have
one GML
related fix to make (regression due to the fast GML encoder, it can be
turned off
with a system variable of course, but still, the default config won't work
for 3D data).

Let's see if the build server recovers in the meantime, if not, I may not
be able to
work on the release until the next weekend (aka Easter).

Cheers
Andrea

On Sun, Mar 20, 2016 at 7:52 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Done.

On 20/03/16 19:38, Ben Caradoc-Davies wrote:

If the build succeeds I will immediately push to 2.8.x and kick 2.8.x,
2.8.x nightly, and 2.8.x cite so Andrea has a working build for release.
I will also push to 2.7.x and master.

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

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

14

Chris,

it is not the Maven Integration plugin but the local version of Maven itself that might require an upgrade.

Jenkins is currently configured to invoke a local installation of Maven installed in /opt/apache-maven-3.0.4 . We are considering whether we want to upgrade Jenkins to use a later version of Maven. Fortunately I found a workaround that fixed the builds I broke so this upgrade is no longer urgent.

Thank you for getting back to us. We will let you know, if we decide to proceed, which version to install. The use of /opt means that ares can have multiple versions installed concurrently; we can then select between them using ares Jenkins system or job configuration.

Kind regards,
Ben.

On 22/03/16 15:12, Christian Del Pino wrote:

Hello Jody and Ben,

Apologies for the late reply.

Are you referring to the Maven Integration plugin for Jenkins? If so,
according to Ares, version 2.1 of the plugin is installed. Version 2.10 of
the Maven plugin is available for installation.

Please let me know when you would like this plugin upgraded.

Regards,
Chris

On Sun, Mar 20, 2016 at 2:42 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Thanks, Jody. An upgrade later this week would be welcome.

Chris, please wait for Andrea's feedback as he is making the GeoTools 14.3
and GeoServer 2.8.3 releases today and a Maven upgrade may interrupt this
process.

We also need community agreement that we require Maven 3.1.1 or later as
GeoServer currently builds with 3.0.4.

Kind regards,
Ben.

On 20/03/16 18:18, Jody Garnett wrote:

Chris can we update maven for Ben? Andrea also has ssh access.

On Sat, Mar 19, 2016 at 5:35 PM Ben Caradoc-Davies <ben@anonymised.com>
wrote:

An alternative is to downgrade git-commit-id-plugin to a 2.1.x that

works with Maven 3.0.x, if such a version exists.

Kind regards,
Ben.

On 20/03/16 12:58, Ben Caradoc-Davies wrote:

Ooh, I broke GeoSolutions (Maven 3.0.5) as well. Sorry about that.

Would you guys prefer to upgrade Maven (and make Maven 3.1.1+ a hard
requirement) or should I revert my pom changes?

Kind regards,
Ben.

On 20/03/16 12:24, Ben Caradoc-Davies wrote:

OK, so I have broken all the builds (master, 2.8.x, and 2.7.x). We can
either:

(1) upgrade ares to Maven 3.1.1 or later (requires Boundless assistance
(I use and recommend Maven 3.3.9 (latest stable))), or

(2) downgrade git-commit-id-plugin to 2.0.4 and build nightlies with
-Xmx2048m

No good deed goes unpunished.

Kind regards,
Ben.

On 20/03/16 11:52, Ben Caradoc-Davies wrote:

Concurrent git-commit-id-plugin looks like the culprit. Local tests
suggest upgrading from 2.0.4 to 2.2.0 (with major jgit dependency
version upgrade) fixes the problem.

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

------------------------------------------------------------------------------
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=278785231&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

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

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

15

Chris,

at today's committee meeting we agreed to upgrade ares to Maven 3.3.9.

Please install Maven 3.3.9 in /opt on ares (alongside the old 3.0.4):
http://www-us.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz

I will switch our builds to use the new Maven after Andrea has completed the release of GeoServer 2.8.3.

Kind regards,
Ben.

On 22/03/16 15:32, Ben Caradoc-Davies wrote:

Chris,

it is not the Maven Integration plugin but the local version of Maven
itself that might require an upgrade.

Jenkins is currently configured to invoke a local installation of Maven
installed in /opt/apache-maven-3.0.4 . We are considering whether we
want to upgrade Jenkins to use a later version of Maven. Fortunately I
found a workaround that fixed the builds I broke so this upgrade is no
longer urgent.

Thank you for getting back to us. We will let you know, if we decide to
proceed, which version to install. The use of /opt means that ares can
have multiple versions installed concurrently; we can then select
between them using ares Jenkins system or job configuration.

Kind regards,
Ben.

On 22/03/16 15:12, Christian Del Pino wrote:

Hello Jody and Ben,

Apologies for the late reply.

Are you referring to the Maven Integration plugin for Jenkins? If so,
according to Ares, version 2.1 of the plugin is installed. Version
2.10 of
the Maven plugin is available for installation.

Please let me know when you would like this plugin upgraded.

Regards,
Chris

On Sun, Mar 20, 2016 at 2:42 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Thanks, Jody. An upgrade later this week would be welcome.

Chris, please wait for Andrea's feedback as he is making the GeoTools
14.3
and GeoServer 2.8.3 releases today and a Maven upgrade may interrupt
this
process.

We also need community agreement that we require Maven 3.1.1 or later as
GeoServer currently builds with 3.0.4.

Kind regards,
Ben.

On 20/03/16 18:18, Jody Garnett wrote:

Chris can we update maven for Ben? Andrea also has ssh access.

On Sat, Mar 19, 2016 at 5:35 PM Ben Caradoc-Davies <ben@anonymised.com>
wrote:

An alternative is to downgrade git-commit-id-plugin to a 2.1.x that

works with Maven 3.0.x, if such a version exists.

Kind regards,
Ben.

On 20/03/16 12:58, Ben Caradoc-Davies wrote:

Ooh, I broke GeoSolutions (Maven 3.0.5) as well. Sorry about that.

Would you guys prefer to upgrade Maven (and make Maven 3.1.1+ a hard
requirement) or should I revert my pom changes?

Kind regards,
Ben.

On 20/03/16 12:24, Ben Caradoc-Davies wrote:

OK, so I have broken all the builds (master, 2.8.x, and 2.7.x).
We can
either:

(1) upgrade ares to Maven 3.1.1 or later (requires Boundless
assistance
(I use and recommend Maven 3.3.9 (latest stable))), or

(2) downgrade git-commit-id-plugin to 2.0.4 and build nightlies with
-Xmx2048m

No good deed goes unpunished.

Kind regards,
Ben.

On 20/03/16 11:52, Ben Caradoc-Davies wrote:

Concurrent git-commit-id-plugin looks like the culprit. Local tests
suggest upgrading from 2.0.4 to 2.2.0 (with major jgit dependency
version upgrade) fixes the problem.

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

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

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=278785231&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

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

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

16

Hello Ben,

Maven 3.3.9 has been installed on Ares. Please let me know if you have any issues.

Regards,
Chris

···

On Tue, Mar 22, 2016 at 5:23 PM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Chris,

at today’s committee meeting we agreed to upgrade ares to Maven 3.3.9.

Please install Maven 3.3.9 in /opt on ares (alongside the old 3.0.4):
http://www-us.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz

I will switch our builds to use the new Maven after Andrea has completed the release of GeoServer 2.8.3.

Kind regards,
Ben.

On 22/03/16 15:32, Ben Caradoc-Davies wrote:

Chris,

it is not the Maven Integration plugin but the local version of Maven
itself that might require an upgrade.

Jenkins is currently configured to invoke a local installation of Maven
installed in /opt/apache-maven-3.0.4 . We are considering whether we
want to upgrade Jenkins to use a later version of Maven. Fortunately I
found a workaround that fixed the builds I broke so this upgrade is no
longer urgent.

Thank you for getting back to us. We will let you know, if we decide to
proceed, which version to install. The use of /opt means that ares can
have multiple versions installed concurrently; we can then select
between them using ares Jenkins system or job configuration.

Kind regards,
Ben.

On 22/03/16 15:12, Christian Del Pino wrote:

Hello Jody and Ben,

Apologies for the late reply.

Are you referring to the Maven Integration plugin for Jenkins? If so,
according to Ares, version 2.1 of the plugin is installed. Version
2.10 of
the Maven plugin is available for installation.

Please let me know when you would like this plugin upgraded.

Regards,
Chris

On Sun, Mar 20, 2016 at 2:42 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Thanks, Jody. An upgrade later this week would be welcome.

Chris, please wait for Andrea’s feedback as he is making the GeoTools
14.3
and GeoServer 2.8.3 releases today and a Maven upgrade may interrupt
this
process.

We also need community agreement that we require Maven 3.1.1 or later as
GeoServer currently builds with 3.0.4.

Kind regards,
Ben.

On 20/03/16 18:18, Jody Garnett wrote:

Chris can we update maven for Ben? Andrea also has ssh access.

On Sat, Mar 19, 2016 at 5:35 PM Ben Caradoc-Davies <ben@anonymised.com>
wrote:

An alternative is to downgrade git-commit-id-plugin to a 2.1.x that

works with Maven 3.0.x, if such a version exists.

Kind regards,
Ben.

On 20/03/16 12:58, Ben Caradoc-Davies wrote:

Ooh, I broke GeoSolutions (Maven 3.0.5) as well. Sorry about that.

Would you guys prefer to upgrade Maven (and make Maven 3.1.1+ a hard
requirement) or should I revert my pom changes?

Kind regards,
Ben.

On 20/03/16 12:24, Ben Caradoc-Davies wrote:

OK, so I have broken all the builds (master, 2.8.x, and 2.7.x).
We can
either:

(1) upgrade ares to Maven 3.1.1 or later (requires Boundless
assistance
(I use and recommend Maven 3.3.9 (latest stable))), or

(2) downgrade git-commit-id-plugin to 2.0.4 and build nightlies with
-Xmx2048m

No good deed goes unpunished.

Kind regards,
Ben.

On 20/03/16 11:52, Ben Caradoc-Davies wrote:

Concurrent git-commit-id-plugin looks like the culprit. Local tests
suggest upgrading from 2.0.4 to 2.2.0 (with major jgit dependency
version upgrade) fixes the problem.

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

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=278785231&iu=/4140

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

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

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

–

Christian Del Pino

DevOps Engineer

Boundless | www.boundlessgeo.com
Email: cdelpino@anonymised.com

17

Thanks very much, Chris.

Kind regards,
Ben.

On 23/03/16 14:43, Christian Del Pino wrote:

Hello Ben,

Maven 3.3.9 has been installed on Ares. Please let me know if you have any
issues.

Regards,
Chris

On Tue, Mar 22, 2016 at 5:23 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Chris,

at today's committee meeting we agreed to upgrade ares to Maven 3.3.9.

Please install Maven 3.3.9 in /opt on ares (alongside the old 3.0.4):

http://www-us.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz

I will switch our builds to use the new Maven after Andrea has completed
the release of GeoServer 2.8.3.

Kind regards,
Ben.

On 22/03/16 15:32, Ben Caradoc-Davies wrote:

Chris,

it is not the Maven Integration plugin but the local version of Maven
itself that might require an upgrade.

Jenkins is currently configured to invoke a local installation of Maven
installed in /opt/apache-maven-3.0.4 . We are considering whether we
want to upgrade Jenkins to use a later version of Maven. Fortunately I
found a workaround that fixed the builds I broke so this upgrade is no
longer urgent.

Thank you for getting back to us. We will let you know, if we decide to
proceed, which version to install. The use of /opt means that ares can
have multiple versions installed concurrently; we can then select
between them using ares Jenkins system or job configuration.

Kind regards,
Ben.

On 22/03/16 15:12, Christian Del Pino wrote:

Hello Jody and Ben,

Apologies for the late reply.

Are you referring to the Maven Integration plugin for Jenkins? If so,
according to Ares, version 2.1 of the plugin is installed. Version
2.10 of
the Maven plugin is available for installation.

Please let me know when you would like this plugin upgraded.

Regards,
Chris

On Sun, Mar 20, 2016 at 2:42 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Thanks, Jody. An upgrade later this week would be welcome.

Chris, please wait for Andrea's feedback as he is making the GeoTools
14.3
and GeoServer 2.8.3 releases today and a Maven upgrade may interrupt
this
process.

We also need community agreement that we require Maven 3.1.1 or later as
GeoServer currently builds with 3.0.4.

Kind regards,
Ben.

On 20/03/16 18:18, Jody Garnett wrote:

Chris can we update maven for Ben? Andrea also has ssh access.

On Sat, Mar 19, 2016 at 5:35 PM Ben Caradoc-Davies <ben@anonymised.com>
wrote:

An alternative is to downgrade git-commit-id-plugin to a 2.1.x that

works with Maven 3.0.x, if such a version exists.

Kind regards,
Ben.

On 20/03/16 12:58, Ben Caradoc-Davies wrote:

Ooh, I broke GeoSolutions (Maven 3.0.5) as well. Sorry about that.

Would you guys prefer to upgrade Maven (and make Maven 3.1.1+ a hard
requirement) or should I revert my pom changes?

Kind regards,
Ben.

On 20/03/16 12:24, Ben Caradoc-Davies wrote:

OK, so I have broken all the builds (master, 2.8.x, and 2.7.x).

We can
either:

(1) upgrade ares to Maven 3.1.1 or later (requires Boundless
assistance
(I use and recommend Maven 3.3.9 (latest stable))), or

(2) downgrade git-commit-id-plugin to 2.0.4 and build nightlies with
-Xmx2048m

No good deed goes unpunished.

Kind regards,
Ben.

On 20/03/16 11:52, Ben Caradoc-Davies wrote:

Concurrent git-commit-id-plugin looks like the culprit. Local tests

suggest upgrading from 2.0.4 to 2.2.0 (with major jgit dependency
version upgrade) fixes the problem.

--

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

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

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=278785231&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--

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

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

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