date:20151221

Thanks, Simone. Confirmed fixed.

Kind regards,
Ben.

On 22/12/15 03:35, Simone Giannecchini wrote:
> I just installed it and kicked a build.

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

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

Re: [Geoserver-devel] GeoServer release publish fail for 2.7.5?

Those files were all changed by my Java 8 upgrade on master. I think we 
have a race condition in release-publish because it switches to master 
and pulls (when I think it should only fetch) even when it is on a 
non-master branch. If files that are processed in the release job 
(release tag updates in poms and installers) are changed on master 
between the running of release and release-publish, there may be a conflict.

I do not think this is a problem caused by Jody's concurrent release.

Andrea, I agree with your proposed solution: Ian, please try rerunning 
the release job. Hopefully that will clear the workspace and resolve the 
conflict.

Kind regards,
Ben.

On 22/12/15 09:26, Andrea Aime wrote:
> Hi,
> I might be wrong, but I see Jody releasing too... and I don't think that
> two releases can go out in parallel, as release and release-publish
> retain some state on a local checkout on the build server.
>
> If that's the case, you may have to redo the release job too to
> re-instate the correct state for _your_ release.
>
> Then again... maybe I'm wrong and it's something else (but don't know what)
>
> Cheers
> Andrea
>
>
> On Mon, Dec 21, 2015 at 6:12 PM, Ian Turton  wrote:
>
>> Does anyone know why the git checkout on jenkins if failing for the 2.7.5
>> release?
>>
>>
>> http://ares.opengeo.org/jenkins/view/release/job/geoserver-release-publish/47/console
>>
>> I don't recall ever having a problem with this step before
>>
>> Ian
>>
>> --
>> Ian Turton
>>
>>
>> --
>>
>> ___
>> 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
>

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

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

Re: [Geoserver-devel] [Geotools-devel] Jira-release job fails

On 22/12/15 02:21, Andrea Aime wrote:
> If you have doubts other have made mistakes

No, just a discussion of how to check in the context of a manual Jira 
release. I am happy for a release manager to check any fixVersions I 
set. I am just suggesting one way it might be done.

> So yes, the commit is not in 2.7.5 and the ticket it's thus correctly
> tagged for 2.7.6 (unless Ian needs to rebuild from a newer revision, but
> it does not seem that's the case).

Great!

Kind regards,

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

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

Re: [Geoserver-devel] Fail build LegacyConfigurationImporter in Eclipse mars for Windows and Java8...

I have same issue on startup with geowebcache.
About of first build error, this works for me (and for test 
units):"info.setUpdateSequence( (long) get( global, "updateSequence", int.class 
) );"
 
Best regardsAlvaro

  De: Daniele Romagnoli 
 Para: A Huarte  
CC: Andrea Aime ; 
"geoserver-devel@lists.sourceforge.net" 
 Enviado: Lunes 21 de diciembre de 2015 17:41
 Asunto: Re: [Geoserver-devel] Fail build LegacyConfigurationImporter in 
Eclipse mars for Windows and Java8...
   
I have same issue.I was building GS master with maven using JDK 7, getting 
this:[INFO] BUILD FAILURE[INFO] 
[INFO] 
Total time: 6.150 s[INFO] Finished at: 2015-12-21T15:40:46+01:00[INFO] Final 
Memory: 41M/369M[INFO] 
[ERROR] 
Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) 
on project gs-platform: Compilation failure[ERROR] Failure executing javac,  
but could not parse the error:[ERROR] javac: invalid target release: 1.8
Therefore, I have switched to use Java8 and the maven build was fine.Moving to 
eclipse (with Java 8 in the buildpath and 1.8 compiler compliance level), I got 
that compiling error.So I have temporarly set 1.7 compiler compliance level to 
build. At the moment I have a different issue with the startup (is creating an 
empty geowebcache-diskquota.xml file, resullting into an initialization error) 
but I think it's not related to that. I'll do some more checks on this.
Cheers,Daniele



On Mon, Dec 21, 2015 at 3:20 PM, A Huarte  wrote:

Thanks Andrea, I will check this error when migration to Java 8 is completed.I 
will still use Java7 until that day.
Alvaro
INFO:Eclipse Java EE IDE for Web Developers (Mars.1 Release (4.5.1)) + Java(TM) 
SE Runtime Environment (build 1.8.0_66-b18) + Windows 7 x64:All fine except 
only this simple error.

  De: Andrea Aime 
 Para: A Huarte  
CC: "geoserver-devel@lists.sourceforge.net" 

 Enviado: Lunes 21 de diciembre de 2015 14:25
 Asunto: Re: [Geoserver-devel] Fail build LegacyConfigurationImporter in 
Eclipse mars for Windows and Java8...
  
You are probably wrong using Java 8, GeoServer is still supposed to be built 
with Java 7 ;-)
Jokes aside, Ben is upgrading GeoServer to Java 8 in these days, and Eclipse 
has its owncompiler that sometimes different behavior than the official Java 
one.
I'd suggest to revisit once the migration to Java 8 on Maven + standard Java 8 
has completed,and then verify if there is any Eclipse specific oddity left.In 
the meantime, I suggest you also get a JDK 7, that's the one you will have to 
use toverify anything for the 2.8.x and 2.7.x branches actually builds
CheersAndrea

On Mon, Dec 21, 2015 at 2:00 PM, A Huarte  wrote:

Hi, I have updated my geoserver repo to current master repo.
It builds ok from windows console with maven, but when I create the eclipse 
projects and I load them in Eclipse Mars (Windows 7 - x64), I get the error 
"Type mismatch: cannot convert from Integer to long" in line ...
https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/config/util/LegacyConfigurationImporter.java#L115


The current method of GeoServerInfo class accepts a long 
value:https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/config/GeoServerInfo.java#L253

I can change the code to:info.setUpdateSequence( get( global, "updateSequence", 
int.class ) );

Eclipse builds ok, but really where I am wrong?

Thanks in advance.Alvaro
--

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





-- 
==GeoServer Professional Services from the experts! Visithttp://goo.gl/it488V 
for more information.==

Geosolutions' Winter Holidays from 24/12 to 6/1

Ing. Andrea Aime 
@geowolfTechnical Lead
GeoSolutions S.A.S.Via Poggio alle Viti 118755054  Massarosa (LU)Italyphone: 
+39 0584 962313fax: +39 0584 1660272mob: +39  339 8844549
http://www.geo-solutions.ithttp://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003Le 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

Re: [Geoserver-devel] a bit stuck on 2.9-M0 release

On 21/12/15 14:49, Emanuele Tajariol wrote:
>> Also, the current GS master does not build against GF master (compile
>> >failure in gs-geofence on ares); I am investigating because I want a
>> >clean build before switching to Java 8.
> Should be fixed now. Please let me know.

Thanks, Emanuele. Confirmed fixed.

Kind regards,

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

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

Re: [Geoserver-devel] GeoServer release publish fail for 2.7.5?

Hi,
I might be wrong, but I see Jody releasing too... and I don't think that
two releases can go out in parallel, as release and release-publish
retain some state on a local checkout on the build server.

If that's the case, you may have to redo the release job too to
re-instate the correct state for _your_ release.

Then again... maybe I'm wrong and it's something else (but don't know what)

Cheers
Andrea

On Mon, Dec 21, 2015 at 6:12 PM, Ian Turton  wrote:

> Does anyone know why the git checkout on jenkins if failing for the 2.7.5
> release?
>
>
> http://ares.opengeo.org/jenkins/view/release/job/geoserver-release-publish/47/console
>
> I don't recall ever having a problem with this step before
>
> Ian
>
> --
> Ian Turton
>
>
> --
>
> ___
> 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/it488V for more information.
==

*Geosolutions' Winter Holidays from 24/12 to 6/1*

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

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

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

Re: [Geoserver-devel] a bit stuck on 2.9-M0 release

Mac DMG fails to startup:

WARNING: Module not found [ssl]
>
> 2015-12-21 16:29:10.299:INFO::startup executor: Logging initialized @6598ms
>
> 2015-12-21 16:29:10.456:INFO:oejs.Server:startup executor:
>> jetty-9.2.13.v20150730
>
> 2015-12-21 16:29:10.470:INFO:oejdp.ScanningAppProvider:startup executor:
>> Deployment monitor
>> [file:/Applications/GeoServer.app/Contents/Java/webapps/] at interval 1
>
> 2015-12-21 16:29:11.307:INFO:oejw.StandardDescriptorProcessor:startup
>> executor: NO JSP Support for /geoserver, did not find
>> org.eclipse.jetty.jsp.JettyJspServlet
>
> 2015-12-21 16:29:11.613:WARN:oejuc.AbstractLifeCycle:startup executor:
>> FAILED 
>> o.e.j.w.WebAppContext@2e901f36{/geoserver,file:/Applications/GeoServer.app/Contents/Java/webapps/geoserver/,STARTING}{/geoserver}:
>> java.lang.NoClassDefFoundError: Could not initialize class
>> javax.media.jai.JAI
>
> java.lang.NoClassDefFoundError: Could not initialize class
>> javax.media.jai.JAI
>
> at
>> org.geoserver.GeoserverInitStartupListener.contextInitialized(GeoserverInitStartupListener.java:88)
>
> at
>> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
>
>
Anyone else want to give it a go?

--
Jody Garnett

On 21 December 2015 at 16:27, Jody Garnett  wrote:

> Now unstuck - thanks for the help aaime :)
>
> Preflight downloads available:
> http://ares.boundlessgeo.com/geoserver/release/2.9-M0/
>
> --
> Jody Garnett
>
> On 20 December 2015 at 16:05, Jody Garnett  wrote:
>
>> Kevin was able to upload GWC to SF, but it has not appeared on
>> repo.boundlessgeo.com - I am going to try and manually upload the jars
>> and see if I can resume the build process.
>> --
>> Jody Garnett
>>
>
>
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] a bit stuck on 2.9-M0 release

Now unstuck - thanks for the help aaime :)

Preflight downloads available:
http://ares.boundlessgeo.com/geoserver/release/2.9-M0/

--
Jody Garnett

On 20 December 2015 at 16:05, Jody Garnett  wrote:

> Kevin was able to upload GWC to SF, but it has not appeared on
> repo.boundlessgeo.com - I am going to try and manually upload the jars
> and see if I can resume the build process.
> --
> Jody Garnett
>
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] (jdbc) resource store: platform additions

Thanks Neils, that approach matches my idea - I had in mind placing a
listener on each style directory - and had hoped that we had relatively few
other folders to track.  I particular I was designing for a clustered
environment and had hoped cluster workload could be sharded a bit by
workspace (so each node may only end up actively watching a couple style
directories...)

I thought I had a single listener list and path matching to handle event
notification. The add/remove listener methods on a single resource were an
illusion (as resource if often a flyweight object).

public void addListener(ResourceListener listener) {
FileSystemResourceStore.this.addListener( file, path, listener
);
}

Which called through to:

public synchronized void addListener(File file, String path,
ResourceListener listener) {
if( watcher == null ){
watcher = new FileSystemWatcher();
}
watcher.addListener( file, path, listener );
}

>From my perspective listeners methods are available on individual
resources, but I expect the resources to be fly weights and not be
responsible for that state themselves.

I cannot really see the difference between this and how the other
clustering solutions get away with just registering a catalog listener?

I double checked and was a bit disappointed not to find anything more then
a catalog listener in the clustering solutions - but I guess it makes
sense. Can I turn this question around? Is there any advantage to having a
single "cluster event dispatch" that could be used by JDBCConfig,
JDBCResourceStore and the clustered WPS implementation?



--
Jody Garnett

On 21 December 2015 at 02:38, Niels Charlier  wrote:

> Alright. What the clustering modules do is simply registering itself as a
> CatalogListener and then dispatch events to other geoserver instances. This
> is a fine strategy for the catalog, I don't see any reason to change it.
>
> The problem is that with resources, listeners are always placed on a
> particular resource. I guess there is one way to do it using a similar
> strategy which I hadn't thought of before (and, admittedly, a fourth option
> to the list I previously claimed was exhaustive) and that to let the
> hazelcast module register as a listener to the Root resource (which should
> receive a notification for every change), rather than implementing a
> ResourceNotificationDispatcher. However, that would be first of all a much
> uglier, more round-about and more bug-prone way of doing things than what I
> did.  Furthermore, what I did places code that is likely reusable by other
> implementations of stores/clusters in a shared space.
>
> Regards
> Niels
>
>
> On 19-12-15 01:03, Jody Garnett wrote:
>
> Comments inline on event distribution ... and then we should be good to
> go.  If it helps I think we can seperate event notification (generating
> events/listening for events) from event distribution (in a cluster,
> recorded in an audit log).
>
> On 18 December 2015 at 07:04, Niels Charlier  wrote:
>
>> no problem: because this isn't being enforced. The ResourceStore already
>> provides the API needed for adding handlers to resources and this remains
>> unaltered, the programmer who uses Resources need not worry about the
>> existence of the ResourceWatcher as they never need to use it.  Alternative
>> implementations of ResourceStore may choose to use it, which would be
>> recommended if they wish to support clustering, but that is all.
>
>
> So the missing bit for me is the hazelcast and jms plugins - they both
> implement an interface for event distribution. I expected JDBCResoruceStore
> work to integrate smoothly with that ... but had not looked into the
> details.
>
> Two questions:
>>> - If you are really focused on event dispatch can we rename the
>>> interface to match?
>>>
>> Sure, ResourceNotificationDispatcher then.
>
>
> Thanks that helps keep my head from exploding.
>
>
>> - Should we have an event dispatch mechanism that works in a similar
>>> fashion for catalog and resource change events?
>>>
>>
>
>> Bit confused, resource change events is what we are talking about.
>> Catalog: good point. I don't know if there is a mechanism in place for
>> distributing these in a  clustered environment, but if not we do need such
>> a mechanism. It is possible this can be solved with a different mechanism.
>
>
> There is a mechanism, and two implementations. I would like to combine
> forces rather than duplicate.
>
> Implementations:
>
> -
> https://github.com/geoserver/geoserver/tree/master/src/community/hz-cluster
> -
> https://github.com/geoserver/geoserver/tree/master/src/community/jms-cluster
>
> Can you take a moment to look at those and tell me what you think?
>
>
>
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net

[Geoserver-devel] Jira-release job fails

2015-12-21 Thread Ian Turton

It seems that both GeoTools and GeoServer's release-jira jobs fail (and
have been failing  for 9 and 6 months) - I assume this is related to the
change of jira hosting, is there a new script or manual step that I need to
run before hitting publish for the new releases?

Cheers

Ian

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

[Geoserver-devel] Allowing range of values as the default value for dimensions

Hi,
I'm currently working on an improvement for the dimensions support in
GeoServer
that I would like to share.

Currently our default value support is rather generic, stored in this class
and subject
to different policies:

https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/catalog/DimensionDefaultValueSetting.java

The default value is stored as a String, and it's up to the strategy to
decide what to do with it.
In all cases though, it's a single value, never a range, and that poses
some limitations and make
some interesting use cases not possible.

In particular, when using the FIXED policy, that uses the reference value
as the
default value, it would be nice to allow usage of a range instead of a
single value.
This is made especially interesting by our current ability to express a
range using
relative expressions, like:

PT36H/PRESENT

See this for an example:
http://docs.geoserver.org/latest/en/user/services/wms/time.html#specifying-a-relative-interval

Mind, this is unrelated to whether or not the actual dimension is range
based, or not,
as it makes a lot of sense also the dimensions that are not range based.

The idea is to extend a bit the UI so that it allows the choice of a single
value, or range
using the well known range syntax (just relaxing the validators to allow
also ranges),
and then making sure the code dealing with dimension can handle ranges.

In several places it already can, since the user can invariably enter a
single value
or a range already, but others know they are dealing with the default value
and
are enforcing a single value representation instead, those need to be
amended too.

This improvement is going to be implemented on master, with an interest in
backport
later.

Do you see any problems with it?

Cheers
Andrea

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

*Geosolutions' Winter Holidays from 24/12 to 6/1*

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

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

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

Re: [Geoserver-devel] (jdbc) resource store: platform additions

2015-12-21 Thread Niels Charlier

Alright. What the clustering modules do is simply registering itself as 
a CatalogListener and then dispatch events to other geoserver instances. 
This is a fine strategy for the catalog, I don't see any reason to 
change it.


The problem is that with resources, listeners are always placed on a 
particular resource. I guess there is one way to do it using a similar 
strategy which I hadn't thought of before (and, admittedly, a fourth 
option to the list I previously claimed was exhaustive) and that to let 
the hazelcast module register as a listener to the Root resource (which 
should receive a notification for every change), rather than 
implementing a ResourceNotificationDispatcher. However, that would be 
first of all a much uglier, more round-about and more bug-prone way of 
doing things than what I did.  Furthermore, what I did places code that 
is likely reusable by other implementations of stores/clusters in a 
shared space.


Regards
Niels

On 19-12-15 01:03, Jody Garnett wrote:
Comments inline on event distribution ... and then we should be good 
to go.  If it helps I think we can seperate event notification 
(generating events/listening for events) from event distribution (in a 
cluster, recorded in an audit log).


On 18 December 2015 at 07:04, Niels Charlier > wrote:


no problem: because this isn't being enforced. The ResourceStore
already provides the API needed for adding handlers to resources
and this remains unaltered, the programmer who uses Resources need
not worry about the existence of the ResourceWatcher as they never
need to use it.  Alternative implementations of ResourceStore may
choose to use it, which would be recommended if they wish to
support clustering, but that is all.


So the missing bit for me is the hazelcast and jms plugins - they both 
implement an interface for event distribution. I expected 
JDBCResoruceStore work to integrate smoothly with that ... but had not 
looked into the details.


Two questions:
- If you are really focused on event dispatch can we rename
the interface to match?

Sure, ResourceNotificationDispatcher then.


Thanks that helps keep my head from exploding.

- Should we have an event dispatch mechanism that works in a
similar fashion for catalog and resource change events?

Bit confused, resource change events is what we are talking about.
Catalog: good point. I don't know if there is a mechanism in place
for distributing these in a clustered environment, but if not we
do need such a mechanism. It is possible this can be solved with a
different mechanism.


There is a mechanism, and two implementations. I would like to combine 
forces rather than duplicate.


Implementations:

- 
https://github.com/geoserver/geoserver/tree/master/src/community/hz-cluster
- 
https://github.com/geoserver/geoserver/tree/master/src/community/jms-cluster


Can you take a moment to look at those and tell me what you think?


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

Re: [Geoserver-devel] [Geotools-devel] Jira-release job fails

On Mon, Dec 21, 2015 at 12:33 PM, Ben Caradoc-Davies 
wrote:

> I see no tag for 2.7.5 in GitHub nor a call for artifact testing. Are you
> sure this issue was omitted? In the release procedure, release in Jira is
> the first step. If the steps were performed out of order and you are sure
> 2.7.5 has been tagged successfully, then 2.7.6 is fine if you are sure your
> issue is not fixed in 2.7.5.
>

The "first step" has been skipped for months, the others are carried out in
sequence, starting from a fixed revision,
provided as a parameter to the build server
That is the revision that gets tagged when performing "release publish",
which is the very last step in the release process.

Ian has already made the testing artifacts based on that revision.
If you have doubts other have made mistakes here is a procedure for you to
double check that,
without publicly pointing fingers, wasting other people time, and keep on
advancing doubts even
when the others tell you it's fine:
* Get the testing artifacts (the bin one)
* Unpack them locally
* Grab one GeoServer jar, reach for META-INF/MANIFEST.MF and get the
revision out of it:

Manifest-Version: 1.0
Build-Timestamp: 19-Dec-2015 11:32
Implementation-Title: REST Configuration Service Module
Implementation-Version: 2.7.5
*Git-Revision: 26f0e9f908fcc279652e0c2622db1028469be16e*
Built-By: jenkins
Specification-Vendor: The Open Planning Project
Application-Name:
GeoServerModule: core
Created-By: Apache Maven 3.0.4
Implementation-Vendor: The Open Planning Project
Iteration-Name:
Implementation-Vendor-Id: org.geoserver
Build-Jdk: 1.7.0_51
Project-Version: 2.7.5
Specification-Title: REST Configuration Service Module
Specification-Version: 2.7.5
Archiver-Version: Plexus Archiver

As an alternative, reach to the build job used to build the artifacts
and check its parameters:
http://ares.boundlessgeo.com/jenkins/view/release/job/geoserver-release/91/parameters/

Now that you have the revision, compare with the commit logs on 2.7.x:

https://github.com/geoserver/geoserver/commits/2.7.x

So yes, the commit is not in 2.7.5 and the ticket it's thus correctly
tagged for 2.7.6 (unless Ian needs to rebuild from a newer revision, but
it does not seem that's the case).

Cheers
Andrea

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

*Geosolutions' Winter Holidays from 24/12 to 6/1*

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

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

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

Re: [Geoserver-devel] Fail build LegacyConfigurationImporter in Eclipse mars for Windows and Java8...

You are probably wrong using Java 8, GeoServer is still supposed to be
built with Java 7 ;-)

Jokes aside, Ben is upgrading GeoServer to Java 8 in these days, and
Eclipse has its own
compiler that sometimes different behavior than the official Java one.

I'd suggest to revisit once the migration to Java 8 on Maven + standard
Java 8 has completed,
and then verify if there is any Eclipse specific oddity left.
In the meantime, I suggest you also get a JDK 7, that's the one you will
have to use to
verify anything for the 2.8.x and 2.7.x branches actually builds

Cheers
Andrea

On Mon, Dec 21, 2015 at 2:00 PM, A Huarte  wrote:

> Hi, I have updated my geoserver repo to current master repo.
>
> It builds ok from windows console with maven, but when I create the
> eclipse projects and I load them in Eclipse Mars (Windows 7 - x64), I get
> the error "Type mismatch: cannot convert from Integer to long" in line ...
>
>
> https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/config/util/LegacyConfigurationImporter.java#L115
>
>
> The current method of GeoServerInfo class accepts a long value:
>
> https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/config/GeoServerInfo.java#L253
>
> I can change the code to:
> info.setUpdateSequence( get( global, "updateSequence", int.class ) );
>
> Eclipse builds ok, but really where I am wrong?
>
> Thanks in advance.
> Alvaro
>
>
> --
>
> ___
> 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/it488V for more information.
==

*Geosolutions' Winter Holidays from 24/12 to 6/1*

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

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

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

Re: [Geoserver-devel] Build failed in Jenkins: GeoServer-Master #2480

2015-12-21 Thread Simone Giannecchini

I just installed it and kicked a build.
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 Poggio alle Viti 1187
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 Mon, Dec 21, 2015 at 8:34 AM, Ben Caradoc-Davies  wrote:
> We need JDK 8 on winbu...@geo-solutions.it. Only JDK 6 and JDK 7 are
> installed and I lack the permissions to install JDK 8.
>
> Kind regards,
> Ben.
>
>
> On 21/12/15 18:54, winbu...@geo-solutions.it wrote:
>>
>> Caused by: org.apache.maven.plugin.CompilationFailureException:
>> Compilation failure
>> Failure executing javac,  but could not parse the error:
>> javac: invalid target release: 1.8
>> Usage: javac  
>> use -help for a list of possible options
>
>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited 
> New Zealand

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

Re: [Geoserver-devel] Fail build LegacyConfigurationImporter in Eclipse mars for Windows and Java8...

Thanks Andrea, I will check this error when migration to Java 8 is completed.I 
will still use Java7 until that day.
Alvaro
INFO:Eclipse Java EE IDE for Web Developers (Mars.1 Release (4.5.1)) + Java(TM) 
SE Runtime Environment (build 1.8.0_66-b18) + Windows 7 x64:All fine except 
only this simple error.

  De: Andrea Aime 
 Para: A Huarte  
CC: "geoserver-devel@lists.sourceforge.net" 

 Enviado: Lunes 21 de diciembre de 2015 14:25
 Asunto: Re: [Geoserver-devel] Fail build LegacyConfigurationImporter in 
Eclipse mars for Windows and Java8...
   
You are probably wrong using Java 8, GeoServer is still supposed to be built 
with Java 7 ;-)
Jokes aside, Ben is upgrading GeoServer to Java 8 in these days, and Eclipse 
has its owncompiler that sometimes different behavior than the official Java 
one.
I'd suggest to revisit once the migration to Java 8 on Maven + standard Java 8 
has completed,and then verify if there is any Eclipse specific oddity left.In 
the meantime, I suggest you also get a JDK 7, that's the one you will have to 
use toverify anything for the 2.8.x and 2.7.x branches actually builds
CheersAndrea

On Mon, Dec 21, 2015 at 2:00 PM, A Huarte  wrote:

Hi, I have updated my geoserver repo to current master repo.
It builds ok from windows console with maven, but when I create the eclipse 
projects and I load them in Eclipse Mars (Windows 7 - x64), I get the error 
"Type mismatch: cannot convert from Integer to long" in line ...
https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/config/util/LegacyConfigurationImporter.java#L115


The current method of GeoServerInfo class accepts a long 
value:https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/config/GeoServerInfo.java#L253

I can change the code to:info.setUpdateSequence( get( global, "updateSequence", 
int.class ) );

Eclipse builds ok, but really where I am wrong?

Thanks in advance.Alvaro
--

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





-- 
==GeoServer Professional Services from the experts! Visithttp://goo.gl/it488V 
for more information.==

Geosolutions' Winter Holidays from 24/12 to 6/1

Ing. Andrea Aime 
@geowolfTechnical Lead
GeoSolutions S.A.S.Via Poggio alle Viti 118755054  Massarosa (LU)Italyphone: 
+39 0584 962313fax: +39 0584 1660272mob: +39  339 8844549
http://www.geo-solutions.ithttp://twitter.com/geosolutions_it
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003Le 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.
---

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

Re: [Geoserver-devel] (jdbc) resource store: platform additions

Sounds excellent, thanks for your hard work.

--
Jody Garnett

On 21 December 2015 at 02:12, Niels Charlier  wrote:

> I'd suggest merging ResourceLoader and GeoServerDataDirectory. Both of
> them provide mostly a lot of convenience methods and a little bit of extra
> logic on top of the ResourceStore. We can remove a lot of the depecrated
> stuff now.
>
>
> On 19-12-15 01:43, Jody Garnett wrote:
>
> And utility methods ...
>
> 2) New utility methods
>>>
>>> Resources.toURL( resource )
>>>  - makes a lot of sense and reads better in the code
>>>
>>> I am not too worried about additional utility methods, instead I am
>>> concerned about changes to objects we may have to implement (such as
>>> GeoServerResourceLoader).
>>>
>>> GeoServerResourceLoader.fromURL(String url)
>>> GeoServerResourceLoader.fromURL(URL url)
>>> - yeah I know you did not write this - just added one that takes a URL
>>> (do you really need both?)
>>>
>>
>> Yes, you do. The fromURL(String) method accepts things that would be
>> rejected by a normal URL parser, abolishing it would be a serious
>> regression causing many configurations to fail.
>>
>> Oh, I forgot to mention. I did NOT add one that takes a URL. This method
>> was merely moved from another spot (GeoServerDataDirectory). An illogical
>> spot, the only reason for it being there is because it is being used there.
>> None of this URL stuff is new, this is just refactoring, moving things
>> together that belong together and make them consistent.
>
>
> Okay now we are making sense :)
>
> Here is the annoying difference in class responsibility (you can also
> check the javadocs):
> * GeoServerResourceLoader is supposed to obtain a resource from the
> configuration system (even if that is a JDBC blob).
> * GeoServerDataDirectory is supposed to *be* the GEOSERVER_DATA_DIRECTORY.
>
> So this is why they were seperate - I like us gradually gathering up all
> the useful methods in GeoServerResourceLoader. This "fromURL" is always
> going to be strange because it is used resolve data references
>
> public Resource fromPath(String path) {
>>>return Resources.fromPath(path, resources.get(Paths.BASE));
>>> }
>>>
>>>   So no need to add helper method here use:
>>> Resource r = Resources.fromPath( path, loader.get(Paths.BASE));
>>>
>>>   Only thing I can think of is that you are trying to hide the fact we
>>> have a DATA_DIRECTORY used as starting point?
>>>
>>
>> These are pure convenience methods. I made them in analogy to the
>> previously already existing GeoServerResourceLoader.url convenience method,
>> which works on the exact same principle and was already there. If you
>> insist they can be removed, but I personally don't see the harm and I find
>> them neater to use than having to call Paths.BASE etc... But it's up to
>> you, say the word.
>>
>
> Keep them, but be very clear about what they do :)
>
> But really we should chat next month about removing deprecated methods so
> this API is less complex over time.
>
>
>
>
>
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] (jdbc) resource store: platform additions

Jody,

have your questions been addressed to your satisfaction? Are we ready to 
merge PR #1361 as it is now?
https://github.com/geoserver/geoserver/pull/1361

Kind regards,
Ben.

On 22/12/15 15:06, Jody Garnett wrote:
> Sounds excellent, thanks for your hard work.

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

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

Re: [Geoserver-devel] a bit stuck on 2.9-M0 release

Looking in installed DMG application:

WEB-INF/lib contains:

jai_codec-1.1.3.jar
jai_core-1.1.3.jar
jai_imageio-1.1.jar

Going to try the bin download ... same problem:

java.lang.NoClassDefFoundError: Could not initialize class
javax.media.jai.JAI
at
org.geoserver.GeoserverInitStartupListener.contextInitialized(GeoserverInitStartupListener.java:88)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)




--
Jody Garnett

On 21 December 2015 at 16:31, Jody Garnett  wrote:

> Mac DMG fails to startup:
>
> WARNING: Module not found [ssl]
>>
>> 2015-12-21 16:29:10.299:INFO::startup executor: Logging initialized
>>> @6598ms
>>
>> 2015-12-21 16:29:10.456:INFO:oejs.Server:startup executor:
>>> jetty-9.2.13.v20150730
>>
>> 2015-12-21 16:29:10.470:INFO:oejdp.ScanningAppProvider:startup executor:
>>> Deployment monitor
>>> [file:/Applications/GeoServer.app/Contents/Java/webapps/] at interval 1
>>
>> 2015-12-21 16:29:11.307:INFO:oejw.StandardDescriptorProcessor:startup
>>> executor: NO JSP Support for /geoserver, did not find
>>> org.eclipse.jetty.jsp.JettyJspServlet
>>
>> 2015-12-21 16:29:11.613:WARN:oejuc.AbstractLifeCycle:startup executor:
>>> FAILED 
>>> o.e.j.w.WebAppContext@2e901f36{/geoserver,file:/Applications/GeoServer.app/Contents/Java/webapps/geoserver/,STARTING}{/geoserver}:
>>> java.lang.NoClassDefFoundError: Could not initialize class
>>> javax.media.jai.JAI
>>
>> java.lang.NoClassDefFoundError: Could not initialize class
>>> javax.media.jai.JAI
>>
>> at
>>> org.geoserver.GeoserverInitStartupListener.contextInitialized(GeoserverInitStartupListener.java:88)
>>
>> at
>>> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
>>
>>
> Anyone else want to give it a go?
>
> --
> Jody Garnett
>
> On 21 December 2015 at 16:27, Jody Garnett  wrote:
>
>> Now unstuck - thanks for the help aaime :)
>>
>> Preflight downloads available:
>> http://ares.boundlessgeo.com/geoserver/release/2.9-M0/
>>
>> --
>> Jody Garnett
>>
>> On 20 December 2015 at 16:05, Jody Garnett 
>> wrote:
>>
>>> Kevin was able to upload GWC to SF, but it has not appeared on
>>> repo.boundlessgeo.com - I am going to try and manually upload the jars
>>> and see if I can resume the build process.
>>> --
>>> Jody Garnett
>>>
>>
>>
>
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] (jdbc) resource store: platform additions

2015-12-21 Thread Niels Charlier

I'd suggest merging ResourceLoader and GeoServerDataDirectory. Both of 
them provide mostly a lot of convenience methods and a little bit of 
extra logic on top of the ResourceStore. We can remove a lot of the 
depecrated stuff now.


On 19-12-15 01:43, Jody Garnett wrote:

And utility methods ...

2) New utility methods

Resources.toURL( resource )
 - makes a lot of sense and reads better in the code

I am not too worried about additional utility methods, instead
I am concerned about changes to objects we may have to
implement (such as GeoServerResourceLoader).

GeoServerResourceLoader.fromURL(String url)
GeoServerResourceLoader.fromURL(URL url)
- yeah I know you did not write this - just added one that
takes a URL (do you really need both?)


Yes, you do. The fromURL(String) method accepts things that would
be rejected by a normal URL parser, abolishing it would be a
serious regression causing many configurations to fail.

Oh, I forgot to mention. I did NOT add one that takes a URL. This
method was merely moved from another spot
(GeoServerDataDirectory). An illogical spot, the only reason for
it being there is because it is being used there. None of this URL
stuff is new, this is just refactoring, moving things together
that belong together and make them consistent.


Okay now we are making sense :)

Here is the annoying difference in class responsibility (you can also 
check the javadocs):
* GeoServerResourceLoader is supposed to obtain a resource from the 
configuration system (even if that is a JDBC blob).

* GeoServerDataDirectory is supposed to *be* the GEOSERVER_DATA_DIRECTORY.

So this is why they were seperate - I like us gradually gathering up 
all the useful methods in GeoServerResourceLoader. This "fromURL" is 
always going to be strange because it is used resolve data references


  public Resource fromPath(String path) {
   return Resources.fromPath(path, resources.get(Paths.BASE));
}

  So no need to add helper method here use:
Resource r = Resources.fromPath( path,
loader.get(Paths.BASE));

  Only thing I can think of is that you are trying to hide the
fact we have a DATA_DIRECTORY used as starting point?


These are pure convenience methods. I made them in analogy to the
previously already existing GeoServerResourceLoader.url
convenience method, which works on the exact same principle and
was already there. If you insist they can be removed, but I
personally don't see the harm and I find them neater to use than
having to call Paths.BASE etc... But it's up to you, say the word.


Keep them, but be very clear about what they do :)

But really we should chat next month about removing deprecated methods 
so this API is less complex over time.






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

[Geoserver-devel] Jenkins build is back to normal : geoserver-2.7.x-nightly #304

2015-12-21 Thread monitor

See 


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

Re: [Geoserver-devel] [Geotools-devel] Jira-release job fails

On Mon, Dec 21, 2015 at 12:16 PM, Ben Caradoc-Davies 
wrote:

> Looks like there is already a GS 2.7.6 version (naughty, naughty, Jira
> makes is far too easy for an administrator to inadvertently add a
> version); someone has an issue for it:
> https://osgeo-org.atlassian.net/browse/GEOS-7353
> Comment here suggests Andrea backported to 2.7.x, so check GitHub
> commits to confirm and change the fixVersion from 2.7.6 to 2.7.5:
> https://github.com/geoserver/geoserver/pull/1375

Since GeoServer 2.7.5 was already out I had to mark the new ticket
for 2.7.6, even if 2.7.5 was not released in Jira.
Can you explain what's wrong with that?

Cheers
Andrea

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

*Geosolutions' Winter Holidays from 24/12 to 6/1*

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

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

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

[Geoserver-devel] Build failed in Jenkins: GeoServer-Master » Core Platform Module #2481

See 


--
[...truncated 571 lines...]
[DEBUG]  org.apache.maven.doxia:doxia-sink-api:jar:1.0-alpha-7:compile
[DEBUG]   org.apache.maven:maven-repository-metadata:jar:2.0.6:compile
[DEBUG]   org.apache.maven:maven-error-diagnostics:jar:2.0.6:compile
[DEBUG]   commons-cli:commons-cli:jar:1.0:compile
[DEBUG]   org.apache.maven:maven-plugin-descriptor:jar:2.0.6:compile
[DEBUG]   
org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4:compile
[DEBUG]   classworlds:classworlds:jar:1.1:compile
[DEBUG]org.apache.maven:maven-artifact:jar:2.0.6:compile
[DEBUG]org.apache.maven:maven-settings:jar:2.0.6:compile
[DEBUG]org.apache.maven:maven-model:jar:2.0.6:compile
[DEBUG]org.apache.maven:maven-monitor:jar:2.0.6:compile
[DEBUG]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:compile
[DEBUG]   junit:junit:jar:3.8.1:compile
[DEBUG]org.codehaus.plexus:plexus-utils:jar:2.0.5:compile
[DEBUG]org.apache.maven.shared:maven-filtering:jar:1.1:compile
[DEBUG]   org.sonatype.plexus:plexus-build-api:jar:0.0.4:compile
[DEBUG]org.codehaus.plexus:plexus-interpolation:jar:1.13:compile
[DEBUG] Created new class realm 
plugin>org.apache.maven.plugins:maven-resources-plugin:2.6
[DEBUG] Importing foreign packages into class realm 
plugin>org.apache.maven.plugins:maven-resources-plugin:2.6
[DEBUG]   Imported:  < project>org.geoserver:geoserver:2.9-SNAPSHOT
[DEBUG] Populating class realm 
plugin>org.apache.maven.plugins:maven-resources-plugin:2.6
[DEBUG]   Included: org.apache.maven.plugins:maven-resources-plugin:jar:2.6
[DEBUG]   Included: org.apache.maven.reporting:maven-reporting-api:jar:2.0.6
[DEBUG]   Included: org.apache.maven.doxia:doxia-sink-api:jar:1.0-alpha-7
[DEBUG]   Included: commons-cli:commons-cli:jar:1.0
[DEBUG]   Included: org.codehaus.plexus:plexus-interactivity-api:jar:1.0-alpha-4
[DEBUG]   Included: junit:junit:jar:3.8.1
[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:2.0.5
[DEBUG]   Included: org.apache.maven.shared:maven-filtering:jar:1.1
[DEBUG]   Included: org.sonatype.plexus:plexus-build-api:jar:0.0.4
[DEBUG]   Included: org.codehaus.plexus:plexus-interpolation:jar:1.13
[DEBUG]   Excluded: org.apache.maven:maven-plugin-api:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-project:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-profile:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-artifact-manager:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-registry:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-core:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-parameter-documenter:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-repository-metadata:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-error-diagnostics:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-plugin-descriptor:jar:2.0.6
[DEBUG]   Excluded: classworlds:classworlds:jar:1.1
[DEBUG]   Excluded: org.apache.maven:maven-artifact:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-settings:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-model:jar:2.0.6
[DEBUG]   Excluded: org.apache.maven:maven-monitor:jar:2.0.6
[DEBUG]   Excluded: 
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1
[DEBUG] Configuring mojo 
org.apache.maven.plugins:maven-resources-plugin:2.6:resources from plugin realm 
ClassRealm[plugin>org.apache.maven.plugins:maven-resources-plugin:2.6, parent: 
sun.misc.Launcher$AppClassLoader@baf1915]
[DEBUG] Configuring mojo 
'org.apache.maven.plugins:maven-resources-plugin:2.6:resources' with basic 
configurator -->
[DEBUG]   (f) buildFilters = []
[DEBUG]   (f) encoding = UTF-8
[DEBUG]   (f) escapeWindowsPaths = true
[DEBUG]   (s) includeEmptyDirs = false
[DEBUG]   (s) outputDirectory = 

[DEBUG]   (s) overwrite = false
[DEBUG]   (f) project = MavenProject: org.geoserver:gs-platform:2.9-SNAPSHOT @ 

[DEBUG]   (s) resources = [Resource {targetPath: null, filtering: false, 
FileSet {directory: 

 PatternSet [includes: {**/*.txt, **/*.sql, **/*.html, **/*.xml, **/*.utf, 
**/*.properties, **/*.template, **/*.serialized, **/*.xsd, META-INF/*.jai, 
META-INF/mailcap, META-INF/services/**, applicationContext.xml, **/*.ftl, 
**/*.css, **/*.js, **/*.png, **/*.gif, **/*.sld, **/*.ico, **/*.json}, 
excludes: {**/doc-files/**, org/geotools/resources/i18n/**/*.properties}]}}, 
Resource {targetPath: null, filtering: false, FileSet {directory:

[Geoserver-devel] Build failed in Jenkins: GeoServer-Master #2481

See 

--
[...truncated 2988 lines...]
[INFO] KML support for GeoServer . SKIPPED
[INFO] GeoWebCache (GWC) Module .. SKIPPED
[INFO] REST Support Module ... SKIPPED
[INFO] REST Configuration Service Module . SKIPPED
[INFO] GeoServer Web Modules . SKIPPED
[INFO] Core UI Module  SKIPPED
[INFO] WMS UI Module . SKIPPED
[INFO] GWC UI Module . SKIPPED
[INFO] WFS UI Module . SKIPPED
[INFO] Demoes Module . SKIPPED
[INFO] WCS UI Module . SKIPPED
[INFO] Security UI Modules ... SKIPPED
[INFO] Security UI Core Module ... SKIPPED
[INFO] Security UI JDBC Module ... SKIPPED
[INFO] Security UI LDAP Module ... SKIPPED
[INFO] REST UI Module  SKIPPED
[INFO] GeoServer Web Application . SKIPPED
[INFO] Community Space ... SKIPPED
[INFO] GeoServer Extensions .. SKIPPED
[INFO] Application Schema Support  SKIPPED
[INFO] Application Schema Integration Test ... SKIPPED
[INFO] Sample DataAccess Integration Test  SKIPPED
[INFO] ArcSDE DataStore Extension  SKIPPED
[INFO] GeoSearch Index Module  SKIPPED
[INFO] H2 DataStore Extension  SKIPPED
[INFO] SQL Server DataStore Extension  SKIPPED
[INFO] Oracle DataStore Extension  SKIPPED
[INFO] MySQL DataStore Extension . SKIPPED
[INFO] DB2 DataStore Extension ... SKIPPED
[INFO] ImageMap Output Format  SKIPPED
[INFO] ImageI/O-Ext GDAL Coverage Extension .. SKIPPED
[INFO] JP2K Coverage Extension ... SKIPPED
[INFO] OGR parent  SKIPPED
[INFO] OGR CORE .. SKIPPED
[INFO] OGR WFS ... SKIPPED
[INFO] Web Processing Service parent . SKIPPED
[INFO] Web Processing Service Module . SKIPPED
[INFO] OGR WPS ... SKIPPED
[INFO] Excel Output Format ... SKIPPED
[INFO] Chart external graphics support ... SKIPPED
[INFO] Feature Generalization Extension .. SKIPPED
[INFO] Image Mosaic JDBC Extension ... SKIPPED
[INFO] OWS request flow controller ... SKIPPED
[INFO] Web process status sharing with Hazelcast . SKIPPED
[INFO] Web Processing Service GUI  SKIPPED
[INFO] GeoServer Layer Querying filter functions . SKIPPED
[INFO] Teradata DataStore Extension .. SKIPPED
[INFO] GeoServer Monitor Extensions .. SKIPPED
[INFO] Core Monitor Extension  SKIPPED
[INFO] Monitor Hibernate Extension ... SKIPPED
[INFO] GeoServer Security Extension Modules .. SKIPPED
[INFO] GeoServer CAS Security Module . SKIPPED
[INFO] GeoServer Security Extension Web Modules .. SKIPPED
[INFO] GeoServer CAS Security Web Module . SKIPPED
[INFO] XLST based WFS output format .. SKIPPED
[INFO] GeoServer INSPIRE Extensions .. SKIPPED
[INFO] GeoServer CSS Styling . SKIPPED
[INFO] Catalog Services for the Web parent ... SKIPPED
[INFO] Catalog Services for the Web interfaces ... SKIPPED
[INFO] Catalog Services for the Web - Simple CatalogStore implementation  
SKIPPED
[INFO] Catalog Services for the Web core module .. SKIPPED
[INFO] CSW UI Module . SKIPPED
[INFO] DXF WFS output format and WPS PPIO  SKIPPED
[INFO] DXF WFS output format . SKIPPED
[INFO] DXF WPS PPIO .. SKIPPED
[INFO] Printing Module ... SKIPPED
[INFO] GeoServer WCS 2.0 Earth Observation Extensions  SKIPPED
[INFO] Web Coverage Service 2.0 Earth Observation extensions  SKIPPED
[INFO] Web Coverage Service 2.0 Earth Observation GUI extension  SKIPPED
[INFO] GeoServer libjpeg-turbo Module  SKIPPED
[INFO] GeoServer Data Importer ... SKIPPED
[INFO] Importer Core Module .. SKIPPED

[Geoserver-devel] [JIRA] (GEOS-7359) "Tile layers" page crashes with GWC_DISKQUOTA_DISABLED set to true

2015-12-21 Thread Maciej Filocha (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Maciej Filocha created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-7359  
 
 
  "Tile layers" page crashes with GWC_DISKQUOTA_DISABLED set to true   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.8.1  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Configuration, GWC  
 
 
Created: 
 21/Dec/15 10:29 AM  
 
 
Environment: 
 CentOS 6.7, Tomcat7  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Maciej Filocha  
 

  
 
 
 
 

 
 Setting GWC_DISKQUOTA_DISABLED variable to "true" causes Tile Caching/Tile Layers page to crash every time with an error "Oops, something went wrong". org.apache.wicket.WicketRuntimeException: Error attaching this container for rendering: [MarkupContainer [Component id = 1]] at org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1765) at org.apache.wicket.Component.onBeforeRender(Component.java:3946) at org.apache.wicket.Component.internalBeforeRender(Component.java:1071) at org.apache.wicket.Component.beforeRender(Component.java:1105) at org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1753) at org.apache.wicket.Component.onBeforeRender(Component.java:3946) at org.apache.wicket.markup.repeater.AbstractRepeater.onBeforeRender(AbstractRepeater.java:151) at org.apache.wicket.markup.repeater.AbstractPageableView.onBeforeRender(AbstractPageableView.java:121) at org.apache.wicket.Component.internalBeforeRender(Component.java:1071) at org.apache.wicket.Component.beforeRender(Component.java:1105) at org.apache.wicket.MarkupContainer.onBeforeRenderChildren(MarkupContainer.java:1753) at org.apache.wicket.Component.onBeforeRender(Component.java:3946) at

Re: [Geoserver-devel] [Geotools-devel] Jira-release job fails

Ian,

yes, the Jira API changed when we moved from Codehaus and the Python 
script is broken. Not as smooth as your last releases in 2014.

The undocumented manual procedure is to for each project:

- Manually perform the release in Administration / Versions and release 
the version using the "..." on the right-hand side

- Create the next unreleased version for the series (13.6 and 2.7.6 in 
your case.

- Search for problematic fixVersions, that is, Unresolved issues (Open, 
In Progress, or Reopened) for the released version and read the 
comments. Was the issue really resolved for this version? If so, leave 
the fixVersion, otherwise remove it. fixVersion means was fixed; this is 
not an aspirational field. If you are really puritanical you can check 
all issues to make sure no Resolved issues were Won't-Fix: these should 
have no fixVersions. This is more than the script ever did but is worth 
the effort for a good quality changelog. And on maintenance the effort 
is tiny.

GeoTools 13.5:
https://osgeo-org.atlassian.net/projects/GEOT/versions/12000

For this issue with fixVersion 13.5 Torben wrote: "I was not able to 
backport to 13.x due to API incompatibility." so remove 13.5 from 
fixVersions (you can also search the git log of 13.x for the issue):
https://osgeo-org.atlassian.net/browse/GEOT-5318

GeoServer 2.7.5:
https://osgeo-org.atlassian.net/projects/GEOS/versions/11902

Looks like there is already a GS 2.7.6 version (naughty, naughty, Jira 
makes is far too easy for an administrator to inadvertently add a 
version); someone has an issue for it:
https://osgeo-org.atlassian.net/browse/GEOS-7353
Comment here suggests Andrea backported to 2.7.x, so check GitHub 
commits to confirm and change the fixVersion from 2.7.6 to 2.7.5:
https://github.com/geoserver/geoserver/pull/1375

All the issues for 2.7.5 are resolved so just release the version and 
you have your changelog.

Kind regards,
Ben.

On 21/12/15 21:19, Ian Turton wrote:
> It seems that both GeoTools and GeoServer's release-jira jobs fail (and
> have been failing  for 9 and 6 months) - I assume this is related to the
> change of jira hosting, is there a new script or manual step that I need to
> run before hitting publish for the new releases?
>
> Cheers
>
> Ian
>
>
>
> --
>
>
>
> ___
> GeoTools-Devel mailing list
> geotools-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

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

Re: [Geoserver-devel] (jdbc) resource store: platform additions

Looks like the methods have been addressed, still circling a bit on the
event notification.

What is your impression Niels?

--
Jody Garnett

On 21 December 2015 at 18:26, Ben Caradoc-Davies  wrote:

> Jody,
>
> have your questions been addressed to your satisfaction? Are we ready to
> merge PR #1361 as it is now?
> https://github.com/geoserver/geoserver/pull/1361
>
> Kind regards,
> Ben.
>
> On 22/12/15 15:06, Jody Garnett wrote:
>
>> Sounds excellent, thanks for your hard work.
>>
>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited 
> New Zealand
>
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] [Geotools-devel] Jira-release job fails

On 22/12/15 00:21, Andrea Aime wrote:
> On Mon, Dec 21, 2015 at 12:16 PM, Ben Caradoc-Davies 
> wrote:
>> Looks like there is already a GS 2.7.6 version (naughty, naughty, Jira
>> makes is far too easy for an administrator to inadvertently add a
>> version); someone has an issue for it:
>> https://osgeo-org.atlassian.net/browse/GEOS-7353
>> Comment here suggests Andrea backported to 2.7.x, so check GitHub
>> commits to confirm and change the fixVersion from 2.7.6 to 2.7.5:
>> https://github.com/geoserver/geoserver/pull/1375
>
> Since GeoServer 2.7.5 was already out I had to mark the new ticket
> for 2.7.6, even if 2.7.5 was not released in Jira.
> Can you explain what's wrong with that?

I see no tag for 2.7.5 in GitHub nor a call for artifact testing. Are 
you sure this issue was omitted? In the release procedure, release in 
Jira is the first step. If the steps were performed out of order and you 
are sure 2.7.5 has been tagged successfully, then 2.7.6 is fine if you 
are sure your issue is not fixed in 2.7.5.

I see this release job for 2.7.5:
http://ares.boundlessgeo.com/jenkins/view/release/job/geoserver-release/91/consoleText

But a release job can be re-run and a new tag can be made, for example, 
if there is a problem with the build. Only the publish step pushes the 
tag to GitHub.

Kind regards,

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

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

[Geoserver-devel] GEOS-7349: GeoJSON geometry and geometry_name inconsistent on multi-geometry features

2015-12-21 Thread Andreas Watermeyer

Hi GeoServer-Developers,

Andrea Aime asked me to involve this mailing list regarding the
following issue & pull request:
https://osgeo-org.atlassian.net/browse/GEOS-7349
https://github.com/geoserver/geoserver/pull/1370

Context:
- GeoServer WFS-Response with outputFormat=JSON
- FeatureType with multiple geometries
- any of the geometries might be null
- the JSON contains one "geometry" attribute, which might be null,
according to the spec
- the JSON contains one "geometry_name" attribute, which defines the
name of the attribute providing the value for the above
- GeoTools FeatureTypes have a "default geometry"

Question:
- What is the desired behaviour if the default geometry of the feature is null?

Solutions:
1) write "null" to the JSON "geometry" field and write the name of the
default geometry attribute to "geometry_name"
Pro: The value of the "geometry_name" field will be the name of the
GeoTools default geometry attribute, consistently across all features
of a feature type.

2) Serialize the first not-null geometry of the feature to the JSON
"geometry" field and write the corresponding field name to
"geometry_name"
Pro: The JSON default geometry will be populated more often than in
1). This makes it more likely for the feature to be displayed
out-of-the-box, like in OpenLayers.

Currently, in this case the "geometry_name" does not correspond to the
value of "geometry".

I can offer to fix this issue. Please given me a feedback which way you prefer.

Best regards,
Andreas


-- 
Andreas

ITS Telco Services GmbH
GIS Services & Solutions
Telecommunications Division
Dillenburger Str. 77
D-51105 Köln
Tel.: +49 (0)221 820 07 00
Fax : +49 (0)221 820 07 22
Mail: i...@its-telco.de
Web : http://www.its-telco.de

Sitz der Gesellschaft: Köln
Amtsgericht Köln, HRB 59310
Geschäftsführer: Gunnar Haack, Ralf Petersilka, Michael Schnepf, Kai
Schriewer, Ludger Schulte


Diese E-Mail enthält vertrauliche Informationen. Wenn Sie nicht der
richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese
E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
E-Mail ist nicht gestattet.

This e-mail may contain confidential information. If you are not the
intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of the material in
this e-mail is strictly forbidden.

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

Re: [Geoserver-devel] Fail build LegacyConfigurationImporter in Eclipse mars for Windows and Java8...

Sorry, I sent an unfinished mail I meant
 "I can change the code to:info.setUpdateSequence( get( global, 
"updateSequence", long.class ) ); "
Alvaro
  De: A Huarte 
 Para: "geoserver-devel@lists.sourceforge.net" 
 
 Enviado: Lunes 21 de diciembre de 2015 14:00
 Asunto: Fail build LegacyConfigurationImporter in Eclipse mars for Windows and 
Java8...
   
Hi, I have updated my geoserver repo to current master repo.
It builds ok from windows console with maven, but when I create the eclipse 
projects and I load them in Eclipse Mars (Windows 7 - x64), I get the error 
"Type mismatch: cannot convert from Integer to long" in line ...
https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/config/util/LegacyConfigurationImporter.java#L115


The current method of GeoServerInfo class accepts a long 
value:https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/config/GeoServerInfo.java#L253

I can change the code to:info.setUpdateSequence( get( global, "updateSequence", 
int.class ) );

Eclipse builds ok, but really where I am wrong?

Thanks in advance.Alvaro

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

Re: [Geoserver-devel] [Geotools-devel] Jira-release job fails

And this is what I recommend when encountering issues with an unexpected 
fixVersion:

On 22/12/15 00:16, Ben Caradoc-Davies wrote:
> so check GitHub commits to confirm

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

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

[Geoserver-devel] Fail build LegacyConfigurationImporter in Eclipse mars for Windows and Java8...

Hi, I have updated my geoserver repo to current master repo.
It builds ok from windows console with maven, but when I create the eclipse 
projects and I load them in Eclipse Mars (Windows 7 - x64), I get the error 
"Type mismatch: cannot convert from Integer to long" in line ...
https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/config/util/LegacyConfigurationImporter.java#L115


The current method of GeoServerInfo class accepts a long 
value:https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/config/GeoServerInfo.java#L253

I can change the code to:info.setUpdateSequence( get( global, "updateSequence", 
int.class ) );

Eclipse builds ok, but really where I am wrong?

Thanks in advance.Alvaro--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Jenkins build is back to normal : geoserver-2.8.x-nightly #90

2015-12-21 Thread monitor

See 


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

Re: [Geoserver-devel] Fail build LegacyConfigurationImporter in Eclipse mars for Windows and Java8...

2015-12-21 Thread Daniele Romagnoli

I have same issue.
I was building GS master with maven using JDK 7, getting this:
[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 6.150 s
[INFO] Finished at: 2015-12-21T15:40:46+01:00
[INFO] Final Memory: 41M/369M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project gs-platform: Compilation failure
[ERROR] Failure executing javac,  but could not parse the error:
[ERROR] javac: invalid target release: 1.8

Therefore, I have switched to use Java8 and the maven build was fine.
Moving to eclipse (with Java 8 in the buildpath and 1.8 compiler compliance
level), I got that compiling error.
So I have temporarly set 1.7 compiler compliance level to build.
At the moment I have a different issue with the startup (is creating an
empty geowebcache-diskquota.xml file, resullting into an initialization
error) but I think it's not related to that. I'll do some more checks on
this.

Cheers,
Daniele




On Mon, Dec 21, 2015 at 3:20 PM, A Huarte  wrote:

> Thanks Andrea, I will check this error when migration to Java 8 is
> completed.
> I will still use Java7 until that day.
>
> Alvaro
>
> INFO:
> Eclipse Java EE IDE for Web Developers (Mars.1 Release (4.5.1)) + Java(TM)
> SE Runtime Environment (build 1.8.0_66-b18) + Windows 7 x64:
> All fine except only this simple error.
>
>
> --
> *De:* Andrea Aime 
> *Para:* A Huarte 
> *CC:* "geoserver-devel@lists.sourceforge.net" <
> geoserver-devel@lists.sourceforge.net>
> *Enviado:* Lunes 21 de diciembre de 2015 14:25
> *Asunto:* Re: [Geoserver-devel] Fail build LegacyConfigurationImporter in
> Eclipse mars for Windows and Java8...
>
> You are probably wrong using Java 8, GeoServer is still supposed to be
> built with Java 7 ;-)
>
> Jokes aside, Ben is upgrading GeoServer to Java 8 in these days, and
> Eclipse has its own
> compiler that sometimes different behavior than the official Java one.
>
> I'd suggest to revisit once the migration to Java 8 on Maven + standard
> Java 8 has completed,
> and then verify if there is any Eclipse specific oddity left.
> In the meantime, I suggest you also get a JDK 7, that's the one you will
> have to use to
> verify anything for the 2.8.x and 2.7.x branches actually builds
>
> Cheers
> Andrea
>
>
> On Mon, Dec 21, 2015 at 2:00 PM, A Huarte  wrote:
>
> Hi, I have updated my geoserver repo to current master repo.
>
> It builds ok from windows console with maven, but when I create the
> eclipse projects and I load them in Eclipse Mars (Windows 7 - x64), I get
> the error "Type mismatch: cannot convert from Integer to long" in line ...
>
>
> https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/config/util/LegacyConfigurationImporter.java#L115
>
>
> The current method of GeoServerInfo class accepts a long value:
>
> https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/config/GeoServerInfo.java#L253
>
> I can change the code to:
> info.setUpdateSequence( get( global, "updateSequence", int.class ) );
>
> Eclipse builds ok, but really where I am wrong?
>
> Thanks in advance.
> Alvaro
>
>
> --
>
> ___
> 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/it488V for more information.
> ==
>
> *Geosolutions' Winter Holidays from 24/12 to 6/1*
>
> 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
>
> *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

[Geoserver-devel] Build failure on Java 8, Linux

Hi,
I'm seeing this failure on a clean master checkout, building with Oracle
JDK 8:


[INFO] Security UI Core Module  FAILURE [03:00
min]

Tests in error:
  testRemoveWithRoles(org.geoserver.security.web.user.UserListPageTest):
org.geoserver.security.web.user.SelectionUserRemovalLink$1.access$0(Lorg/geoserver/security/web/user/SelectionUserRemovalLink$1;)Lorg/geoserver/security/web/user/SelectionUserRemovalLink;
  testRemove(org.geoserver.security.web.user.UserListPageTest):
org.geoserver.security.web.user.SelectionUserRemovalLink$1.access$0(Lorg/geoserver/security/web/user/SelectionUserRemovalLink$1;)Lorg/geoserver/security/web/user/SelectionUserRemovalLink;

However if I run it from Eclipse using Java 8 there are no problems... at
first
I thought it was due to a different execution order, but we have pegged down
the execution order in the main pom.xml :

 maven-surefire-plugin
2.12.3

 alphabetical

So hum... not sure... anyone else seeing it?

Cheers
Andrea

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

*Geosolutions' Winter Holidays from 24/12 to 6/1*

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

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

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

Re: [Geoserver-devel] Build failure on Java 8, Linux

Ah,
another interesting bit... the failure seems to be intermittent... actually
only got it only once
in 3 builds so far... duh...

Cheers
Andrea


On Mon, Dec 21, 2015 at 4:01 PM, Andrea Aime 
wrote:

> Hi,
> I'm seeing this failure on a clean master checkout, building with Oracle
> JDK 8:
>
>
> [INFO] Security UI Core Module  FAILURE [03:00
> min]
>
> Tests in error:
>   testRemoveWithRoles(org.geoserver.security.web.user.UserListPageTest):
> org.geoserver.security.web.user.SelectionUserRemovalLink$1.access$0(Lorg/geoserver/security/web/user/SelectionUserRemovalLink$1;)Lorg/geoserver/security/web/user/SelectionUserRemovalLink;
>   testRemove(org.geoserver.security.web.user.UserListPageTest):
> org.geoserver.security.web.user.SelectionUserRemovalLink$1.access$0(Lorg/geoserver/security/web/user/SelectionUserRemovalLink$1;)Lorg/geoserver/security/web/user/SelectionUserRemovalLink;
>
> However if I run it from Eclipse using Java 8 there are no problems... at
> first
> I thought it was due to a different execution order, but we have pegged
> down
> the execution order in the main pom.xml :
>
>  maven-surefire-plugin
> 2.12.3
> 
>  alphabetical
>
> So hum... not sure... anyone else seeing it?
>
> Cheers
> Andrea
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> ==
>
> *Geosolutions' Winter Holidays from 24/12 to 6/1*
>
> 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
>
> *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.
>
> ---
>



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

*Geosolutions' Winter Holidays from 24/12 to 6/1*

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

*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

[Geoserver-devel] Jenkins build is back to normal : GeoServer-Master #2482

See 


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

[Geoserver-devel] Jenkins build is back to normal : GeoServer-Master » Core Platform Module #2482