Re: [Geoserver-devel] Version control for local Geoserver Repository

2020-10-13 Thread Brad Hards 
Then just learn about git pull --rebase

 

Brad

 

From: maven apache  
Sent: Tuesday, 13 October 2020 6:59 PM
To: br...@frogmouth.net
Cc: Geoserver-devel 
Subject: Re: [Geoserver-devel] Version control for local Geoserver Repository

 

If the extension is completely separated from geoserver and modules, I can 
create a  new project, which makes geoserver and the other modules as  
dependencies,

 

However when I built the extension, there were some other modifications  for 
the geoserver codebase.  That's why I have to put my extension under a 
geoserver tree like `/src/extension/myext/...`

 

 

 

On Tue, Oct 13, 2020 at 2:53 PM mailto:br...@frogmouth.net> > wrote:

You could rebase your changes. Or just move your extension out of the tree.

 

Its your code - if it isn't going to be part of GeoServer do it however you 
like.

 

Brad.

 

On 13 Oct 2020 3:03 pm, maven apache mailto:apachemav...@gmail.com> > wrote:

I am building a local geoserver extension which does not have the plan to make 
it open source, and I only use that extension with geoserver myself. I think 
this does not breach the GPL License used by Geoserver. If yes, plesae let me 
know.

The extension started from a tag v2.17.0:

git pull https://github.com/geoserver/geoserver.git
git checkout -b local_branch 2.17.0
//coding for the extension

Now once we want to sync with the current stable version of geoserver: 2.18.0, 
I tried this:

git checkout master
git pull --tags
git checkout local_branch 
git merge 2.18.0

Now there are so many files changed/confliction because of the version changed 
in the pom.xml:

org.geoserver
geoserver
pom
2.18.0
GeoServer

I am afraid this may break the git history. 

Then I wonder how does geoserver handle this problem? Since every time a new 
stable version is released, the version number will be updated too. But I do 
not find the commits for the version update.

Even though I read the development guide at 
https://docs.geoserver.org/stable/en/developer/source.html#source-code, I still 
can not find a solution.

Any suggestions or the best practice for this customization workflow?

 

Thanks.

 

 

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

[Geoserver-devel] PSC meeting notes, October 13th 2020

2020-10-13 Thread Andrea Aime 
GeoTools / GeoServer PMC meeting - 2020-10-13Attending

Jukka Rahkonen

Andrea Aime

Jody Garnett

Kevin Smith
Actions from last meeting:

   -

   Jody: Switch GeoTools bin to use assembly, grab everything, folks who
   want custom units can use exclude (still todo?)
   -

   Andrea: remove bin release if assembly does not work (out backup plan)
   -

   Jody: Contact SAC to follow up with Tom on domain name transfer (any
   update? None waiting on Tom)


Agenda

   1.

   Build server update
   2.

   GeoServer October release?
   3.

   Unchecked branch update
   4.

   GWC parameter filters
   5.

   Chit chat

Actions

   -

   Jody to check the the GeoTools bin assembly
   -

   Andrea marching on in the unchecked branch

Build server update

Everything is building fine besides GeoFence, Nexus fixed.

Jody to turn on all the parallel builds again (gently!).

GeoServer October release

Skipping releases in October to go back on having a release per month, last
month we released both stable and maintenance.
Unchecked branch update

Spreadsheet here:
https://docs.google.com/spreadsheets/d/1voHK_V8ZdbN-yqqUkqrl0rJsLjqiOjmVwJkm1Fjd0z4/edit#gid=0

Started with 3000 warnings, down to 1000, should go down quickly to zero
from here.

Using IntelliJ to quickly locate the issues module by module.
GWC parameter filters

Landed on master to make parameter filters update more robust. Running in
production for a couple of weeks, we are backporting stuff.

DGGS progress

Clickhouse storage: https://github.com/geoserver/geoserver/pull/4535

Chit chat

OSGeo nominations, October 24 : https://wiki.osgeo.org/wiki/Election_2020

Any committers to nominate? https://www.osgeo.org/about/charter-members/

Foss4g-KO

   -

   anyone want to submit? Jody? Ian?




-- 

Regards, Andrea Aime

== 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
--- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] [Geotools-devel] GeoServer/GeoTools PMC Meeting at 16:30 UTC tomorrow

2020-10-13 Thread Andrea Aime 
Kevin went through the same. If you are all alone in a meeting, try
reconnecting

Cheers
Andrea

On Tue, Oct 13, 2020 at 6:34 PM Andrea Aime 
wrote:

> And then I re-joined, and there is Jukka and Jody too.
>
> Cheers
> Andrea
>
>
> On Tue, Oct 13, 2020 at 6:33 PM Andrea Aime 
> wrote:
>
>> Meeting on, but it's just me. Daylight savings is messing up with the
>> meeting time maybe?
>>
>> Cheers
>> Andrea
>>
>> On Tue, Oct 13, 2020 at 2:11 AM Torben Barsballe <
>> torbenbarsba...@gmail.com> wrote:
>>
>>> Reminder that the next PMC meeting is scheduled for tomorrow, October
>>> 13, at 16:30
>>> 
>>> UTC.
>>>
>>> You can join the meeting via Jitsi: https://meet.jit.si/GeoServerMeeting
>>>
>>> I have a conflicting meeting, and will be unable to attend.
>>>
>>> Cheers,
>>> --
>>> Torben Barsballe
>>> Professional Services Engineer
>>> Planet
>>> torben.barsba...@planet.com
>>> ___
>>> GeoTools-Devel mailing list
>>> geotools-de...@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>
>>
>>
>> --
>>
>> Regards, Andrea Aime
>>
>> == 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
>> --- *Con riferimento
>> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
>> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
>> circostanza inerente alla presente email (il suo contenuto, gli eventuali
>> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
>> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
>> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
>> sarei comunque grato se potesse darmene notizia. This email is intended
>> only for the person or entity to which it is addressed and may contain
>> information that is privileged, confidential or otherwise protected from
>> disclosure. We remind that - as provided by European Regulation 2016/679
>> “GDPR” - copying, dissemination or use of this e-mail or the information
>> herein by anyone other than the intended recipient is prohibited. If you
>> have received this email by mistake, please notify us immediately by
>> telephone or e-mail.*
>>
>
>
> --
>
> Regards, Andrea Aime
>
> == 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
> --- *Con riferimento
> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
> circostanza inerente alla presente email (il suo contenuto, gli eventuali
> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
> sarei comunque grato se potesse darmene notizia. This email is intended
> only for the person or entity to which it is addressed and may contain
> information that is privileged, confidential or otherwise protected from
> disclosure. We remind that - as provided by European Regulation 2016/679
> “GDPR” - copying, dissemination or use of this e-mail or the information
> herein by anyone other than the intended recipient is prohibited. If you
> have received this email by mistake, please notify us immediately by
> telephone or e-mail.*
>


-- 

Regards, Andrea Aime

== 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
--- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato

Re: [Geoserver-devel] [Geotools-devel] GeoServer/GeoTools PMC Meeting at 16:30 UTC tomorrow

2020-10-13 Thread Andrea Aime 
And then I re-joined, and there is Jukka and Jody too.

Cheers
Andrea


On Tue, Oct 13, 2020 at 6:33 PM Andrea Aime 
wrote:

> Meeting on, but it's just me. Daylight savings is messing up with the
> meeting time maybe?
>
> Cheers
> Andrea
>
> On Tue, Oct 13, 2020 at 2:11 AM Torben Barsballe <
> torbenbarsba...@gmail.com> wrote:
>
>> Reminder that the next PMC meeting is scheduled for tomorrow, October 13,
>> at 16:30
>> 
>> UTC.
>>
>> You can join the meeting via Jitsi: https://meet.jit.si/GeoServerMeeting
>>
>> I have a conflicting meeting, and will be unable to attend.
>>
>> Cheers,
>> --
>> Torben Barsballe
>> Professional Services Engineer
>> Planet
>> torben.barsba...@planet.com
>> ___
>> GeoTools-Devel mailing list
>> geotools-de...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>
>
> --
>
> Regards, Andrea Aime
>
> == 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
> --- *Con riferimento
> alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
> Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
> circostanza inerente alla presente email (il suo contenuto, gli eventuali
> allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
> destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
> errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
> sarei comunque grato se potesse darmene notizia. This email is intended
> only for the person or entity to which it is addressed and may contain
> information that is privileged, confidential or otherwise protected from
> disclosure. We remind that - as provided by European Regulation 2016/679
> “GDPR” - copying, dissemination or use of this e-mail or the information
> herein by anyone other than the intended recipient is prohibited. If you
> have received this email by mistake, please notify us immediately by
> telephone or e-mail.*
>


-- 

Regards, Andrea Aime

== 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
--- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] [Geotools-devel] GeoServer/GeoTools PMC Meeting at 16:30 UTC tomorrow

2020-10-13 Thread Andrea Aime 
Meeting on, but it's just me. Daylight savings is messing up with the
meeting time maybe?

Cheers
Andrea

On Tue, Oct 13, 2020 at 2:11 AM Torben Barsballe 
wrote:

> Reminder that the next PMC meeting is scheduled for tomorrow, October 13,
> at 16:30
> 
> UTC.
>
> You can join the meeting via Jitsi: https://meet.jit.si/GeoServerMeeting
>
> I have a conflicting meeting, and will be unable to attend.
>
> Cheers,
> --
> Torben Barsballe
> Professional Services Engineer
> Planet
> torben.barsba...@planet.com
> ___
> GeoTools-Devel mailing list
> geotools-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>


-- 

Regards, Andrea Aime

== 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
--- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] builds fixed, excepting geofence

2020-10-13 Thread Mark Prins 

On 12-10-2020 09:21, Jody Garnett wrote:

Okay, beyond that the next failure is:

  Transfer failed for

http://repo1.maven.org/maven2/org/geotools/gt-api/21-SNAPSHOT/gt-api-21-SNAPSHOT.pom
501 HTTPS Required -> [Help 1]


The 21-SNAPSHOTS are indeed no longer published anywhere, and the gt-api 
module was refactored away. Geofence will need to update ...


There's a 2-fold problem here (1. only https allowed, 2. no 21-SNAPSHOT 
anywhere)


I've updated most of these problems in PR:

https://github.com/geoserver/geofence/pull/153

which bumps commons-beanutils to the same version that is used in GeoTools

last thing I was running into was resolving

org.geoserver.geofence:geofence-gui-resources:jar:3.5-SNAPSHOT

in "geofence-gui-resources", not sure where that is to be found. Details:


[ERROR] Failed to execute goal on project geofence-gui-resources: Could 
not resolve dependencies for project 
org.geoserver.geofence:geofence-gui-resources:jar:3.5-SNAPSHOT: The 
following artifacts could not be resolved: 
it.geosolutions.geogwt.core:geogwt-resources:jar:0.4-SNAPSHOT, 
it.geosolutions.geogwt.widgets.map:maptoolbar:jar:0.4-SNAPSHOT, 
com.extjs:gxt:jar:2.2.5-gwt22: Could not find artifact 
it.geosolutions.geogwt.core:geogwt-resources:jar:0.4-SNAPSHOT in 
osgeo-snapshots (https://repo.osgeo.org/repository/snapshot/) -> [Help 1]

[ERROR]

perhaps one of the experts can join in.

Frankly (and without meaning any insult) the maven structure of the 
geofence project has quite a bit technical dept.


I'm willing to have a crack at cleaning up the Maven things once we have 
a stable build


Mark





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

[Geoserver-devel] [JIRA] (GEOS-9768) TIME dimension and CLIP WMS vendor parameter does not work in the same time

2020-10-13 Thread Charles-Henry COLIN (JIRA) 
Charles-Henry COLIN ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=5efce41d7295050bad6e99c0
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiZWY0MmRmYzU1NjVkNDNjM2FlN2YwYTZhNjA1MzdhOWEiLCJwIjoiaiJ9
 ) / Bug ( 
https://osgeo-org.atlassian.net/browse/GEOS-9768?atlOrigin=eyJpIjoiZWY0MmRmYzU1NjVkNDNjM2FlN2YwYTZhNjA1MzdhOWEiLCJwIjoiaiJ9
 ) GEOS-9768 ( 
https://osgeo-org.atlassian.net/browse/GEOS-9768?atlOrigin=eyJpIjoiZWY0MmRmYzU1NjVkNDNjM2FlN2YwYTZhNjA1MzdhOWEiLCJwIjoiaiJ9
 ) TIME dimension and CLIP WMS vendor parameter does not work in the same time 
( 
https://osgeo-org.atlassian.net/browse/GEOS-9768?atlOrigin=eyJpIjoiZWY0MmRmYzU1NjVkNDNjM2FlN2YwYTZhNjA1MzdhOWEiLCJwIjoiaiJ9
 )

Issue Type: Bug Affects Versions: 2.17.2 Assignee: Unassigned Attachments: 
Clip_image.png, mask.png Components: WMS Created: 13/Oct/20 12:03 PM 
Environment:

geoserver 2.17.2 install on windows server 2016

Priority: High Reporter: Charles-Henry COLIN ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=5efce41d7295050bad6e99c0
 )

I'm working with an imagemosaic store composed of geotiff multiband rasters all 
projected in EPSG:3857.
Rasters are compressed (DEFLATE) and store on the windows server Filesystem.
I'm rendering this store with a layergroup composed of the same layer but 
render differently twice.

The layer has a TIME dimension define in the index.properties file correctly 
and working fine.

In the WMS request I use the vendor parameter CLIP which is clipping my png 
return image with a polygon define correctly in SRID4326 with the extended 
parameter : SRID=4326;Polygone((.etc.)) and it works fine. (Just a small 
rendering issue that you can see in join file "Clip_image.png" where we see 
that contours are pixelized. From my opinion this is due to a CLIP method apply 
at a too early stage before bicubic interpolation is applied.)

The big issue is when you use both parameters in the same WMS request : 
TIME=-MM-DD/-MM-DD and CLIP=srid=4326;POLYGON((..)) it returns you 
the wrong image (at a wrong date) but correctly clipped. Actually this is 
strange because it returns always the image corresponding at the closest
date from now, no matter of your layer dimension TIME settings.

( 
https://osgeo-org.atlassian.net/browse/GEOS-9768#add-comment?atlOrigin=eyJpIjoiZWY0MmRmYzU1NjVkNDNjM2FlN2YwYTZhNjA1MzdhOWEiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-9768#add-comment?atlOrigin=eyJpIjoiZWY0MmRmYzU1NjVkNDNjM2FlN2YwYTZhNjA1MzdhOWEiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100149- 
sha1:7ccee73 )___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Version control for local Geoserver Repository

2020-10-13 Thread Jody Garnett 
Technically your extension is still GPL, you have to share the source code
with the person running the application, in this case yourself :)

When working in isolation on an extension for a customer ... I tend to make
a separate web-app (via war overlay, or by copying the geoserver web app).
This gives me an easy way to try out the change and debug.
--
Jody Garnett


On Mon, 12 Oct 2020 at 21:05, maven apache  wrote:

> I am building a local geoserver extension which does not have the plan to
> make it open source, and I only use that extension with geoserver myself. I
> think this does not breach the GPL License used by Geoserver. If yes,
> plesae let me know.
>
> The extension started from a tag v2.17.0:
>
> git pull https://github.com/geoserver/geoserver.git
> git checkout -b local_branch 2.17.0
> //coding for the extension
>
> Now once we want to sync with the current stable version of geoserver:
> 2.18.0, I tried this:
>
> git checkout master
> git pull --tags
> git checkout local_branch
> git merge 2.18.0
>
> Now there are so many files changed/confliction because of the version
> changed in the pom.xml:
>
> org.geoserver
> geoserver
> pom
> 2.18.0
> GeoServer
>
> I am afraid this may break the git history.
>
> Then I wonder how does geoserver handle this problem? Since every time a
> new stable version is released, the version number will be updated too. But
> I do not find the commits for the version update.
>
> Even though I read the development guide at
> https://docs.geoserver.org/stable/en/developer/source.html#source-code, I
> still can not find a solution.
>
> Any suggestions or the best practice for this customization workflow?
>
>
> Thanks.
>
> ___
> 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

Re: [Geoserver-devel] New community module: cog (Cloud Optimized GeoTIFF)

2020-10-13 Thread Jody Garnett 
Fair enough, you already have my +1, looking forward to the result :)
--
Jody Garnett


On Mon, 12 Oct 2020 at 01:32, Daniele Romagnoli <
daniele.romagn...@geo-solutions.it> wrote:

>
>
> On Sun, Oct 11, 2020 at 8:09 PM Jody Garnett 
> wrote:
>
>> +1
>>
>> Was going to ask what the module would be called, and checked the draft
>> ... `cog` :)
>> Should we follow the existing naming convention with `s3-geotiff`, and
>> end up with something like `cog-geotiff` ?
>>
>
> I agree with Andrea's joke :) The G in coG already means GeoTIFF so it
> will be redundant.
> Regards,
> Daniele
>
>
>>
>> Or is it a case that when these community modules are approved they will
>> be added to the existing geotiff support.
>>
>
>> --
>> Jody Garnett
>>
>>
>> On Fri, 9 Oct 2020 at 03:59, Daniele Romagnoli <
>> daniele.romagn...@geo-solutions.it> wrote:
>>
>>> Dear all,
>>> I'm proposing the addition of a new cog community module on GeoServer.
>>> Where cog-> COG means Cloud Optimized GeoTIFF, a regular GeoTIFF file,
>>> aimed at being hosted on a file server, whose internal organization is
>>> friendly for consumption by clients issuing GET Byte range requests.
>>>
>>> The module will be mainly based on new imageio-ext readers/streams
>>> supporting these Byte Range requests.
>>>
>>> It will contain new UI sections extending the GeoTIFF format panel to
>>> configure a (COG)eoTiff Dataset, as well as additional instructions and
>>> configuration parameters to setup an ImageMosaic on top of an index
>>> referring to COG granules.
>>>
>>> Finally it will add all the additional dependencies needed to support
>>> those new capabilities, not being part of the standard GeoServer war.
>>>
>>> The related GeoServer JIRA.
>>> https://osgeo-org.atlassian.net/browse/GEOS-9767
>>>
>>> Related GeoTools JIRA and PRs (still in draft state)
>>>
>>> GeoTIFF:
>>> https://osgeo-org.atlassian.net/browse/GEOT-6715
>>> https://github.com/geotools/geotools/pull/3169
>>>
>>> ImageMosaic:
>>> https://osgeo-org.atlassian.net/browse/GEOT-6716
>>> https://github.com/geotools/geotools/pull/3173
>>>
>>> --
>>> Regards,
>>> Daniele Romagnoli
>>> ==
>>> GeoServer Professional Services from the experts! Visit
>>> http://goo.gl/it488V for more information.
>>> ==
>>>
>>> Ing. Daniele Romagnoli
>>> Senior Software Engineer
>>>
>>> GeoSolutions S.A.S.
>>> Via di Montramito 3/A
>>> 55054  Massarosa (LU)
>>> Italy
>>> phone: +39 0584 962313
>>> fax:  +39 0584 1660272
>>>
>>> http://www.geo-solutions.it
>>> http://twitter.com/geosolutions_it
>>>
>>> ---
>>>
>>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>>> precisa che ogni circostanza inerente alla presente email (il suo
>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>>
>>> This email is intended only for the person or entity to which it is
>>> addressed and may contain information that is privileged, confidential or
>>> otherwise protected from disclosure. We remind that - as provided by
>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>>> e-mail or the information herein by anyone other than the intended
>>> recipient is prohibited. If you have received this email by mistake, please
>>> notify us immediately by telephone or e-mail.
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>
> --
> Regards,
> Daniele Romagnoli
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> ==
>
> Ing. Daniele Romagnoli
> Senior Software Engineer
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054  Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax:  +39 0584 1660272
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> ---
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure.

Re: [Geoserver-devel] Version control for local Geoserver Repository

2020-10-13 Thread maven apache 
If the extension is completely separated from geoserver and modules, I can
create a  new project, which makes geoserver and the other modules as
dependencies,

However when I built the extension, there were some other modifications
for the geoserver codebase.  That's why I have to put my extension under a
geoserver tree like `/src/extension/myext/...`



On Tue, Oct 13, 2020 at 2:53 PM  wrote:

> You could rebase your changes. Or just move your extension out of the tree.
>
> Its your code - if it isn't going to be part of GeoServer do it however
> you like.
>
> Brad.
>
> On 13 Oct 2020 3:03 pm, maven apache  wrote:
>
> I am building a local geoserver extension which does not have the plan to
> make it open source, and I only use that extension with geoserver myself. I
> think this does not breach the GPL License used by Geoserver. If yes,
> plesae let me know.
>
> The extension started from a tag v2.17.0:
>
> git pull https://github.com/geoserver/geoserver.git
> git checkout -b local_branch 2.17.0
> //coding for the extension
>
> Now once we want to sync with the current stable version of geoserver:
> 2.18.0, I tried this:
>
> git checkout master
> git pull --tags
> git checkout local_branch
> git merge 2.18.0
>
> Now there are so many files changed/confliction because of the version
> changed in the pom.xml:
>
> org.geoserver
> geoserver
> pom
> 2.18.0
> GeoServer
>
> I am afraid this may break the git history.
>
> Then I wonder how does geoserver handle this problem? Since every time a
> new stable version is released, the version number will be updated too. But
> I do not find the commits for the version update.
>
> Even though I read the development guide at
> https://docs.geoserver.org/stable/en/developer/source.html#source-code, I
> still can not find a solution.
>
> Any suggestions or the best practice for this customization workflow?
>
>
> Thanks.
>
>
>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Version control for local Geoserver Repository

2020-10-13 Thread bradh 
You could rebase your changes. Or just move your extension out of the tree.Its your code - if it isn't going to be part of GeoServer do it however you like.Brad.On 13 Oct 2020 3:03 pm, maven apache  wrote:I am building a local geoserver extension which does not have the plan to make it open source, and I only use that extension with geoserver myself. I think this does not breach the GPL License used by Geoserver. If yes, plesae let me know.
The extension started from a tag v2.17.0:
git pull https://github.com/geoserver/geoserver.git
git checkout -b local_branch 2.17.0
//coding for the extension
Now once we want to sync with the current stable version of geoserver: 2.18.0, I tried this:
git checkout master
git pull --tags
git checkout local_branch 
git merge 2.18.0
Now there are so many files changed/confliction because of the version changed in the pom.xml:
org.geoserver
geoserver
pom
2.18.0
GeoServer
I am afraid this may break the git history. 
Then I wonder how does geoserver handle this problem? Since every time a new stable version is released, the version number will be updated too. But I do not find the commits for the version update.Even though I read the development guide at https://docs.geoserver.org/stable/en/developer/source.html#source-code, I still can not find a solution.Any suggestions or the best practice for this customization workflow?Thanks.

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