[Geoserver-devel] Maven repositories and plugins

Hi,

I’m working on an application at the moment, where we use jetty as the container for geoserver and assemble this with the war and necessary plugins into an installable container which we use in a microservice architecture. For this we need access to the wars and the plugins (*.zip files) available, but I don’t see that they are published to the repository at repo.boundlessgeo.com

Would it be possible to publish the war files and the zipped plugins to the repository? At the moment we’re having to upload these manually to our own repository, which is a pain with every version upgrade.

Also, the extra zip files created for the plugins might they be added to the deployment by using the maven assembly plugin? This would reduce the dependency on the shell scripts for a complete build and deployment. I’d be happy to supply a pull request.

Kind Regards,

Frode Carlsen

On Tue, Mar 24, 2015 at 5:12 PM, Frode Odde CARLSEN <fc@anonymised.com>
wrote:

Hi,

I’m working on an application at the moment, where we use jetty as the
container for geoserver and assemble this with the war and necessary
plugins into an installable container which we use in a microservice
architecture. For this we need access to the wars and the plugins (*.zip
files) available, but I don’t see that they are published to the repository
at repo.boundlessgeo.com

Would it be possible to publish the war files and the zipped plugins to
the repository? At the moment we’re having to upload these manually to our
own repository, which is a pain with every version upgrade.

Also, the extra zip files created for the plugins might they be added to
the deployment by using the maven assembly plugin? This would reduce the
dependency on the shell scripts for a complete build and deployment. I’d be
happy to supply a pull request.

I cannot talk in terms of extra space consumption on the repository
(Boundless will have to speak up), but in terms of getting things done, an
open source project is a do-ocracy,
if you are the one doing the work of changing the release scripts to get
the deploys done (they are in git too), personally I won't complain :wink:

However, I would like to point out assembling zip and wars is not the
recommended way to create a customized GeoServer,
you should take web/app, copy it, change its dependencies to fit your
needs, and build it to get the exact war you need.
When you need to create a new version, just update the version number,
rebuild, done.

Cheers
Andrea

--

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

Ing. Andrea Aime
@geowolf
Technical Lead

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

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

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

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

Thanks,

​I managed to get it done through the maven dependency mechanism. For some reason I thought there’d be extra stuff in the plugin zips.

Cheers,

Frode

···

Fra: andrea.aime@…403… <andrea.aime@…403…> på vegne av Andrea Aime <andrea.aime@…1268…>
Sendt: 24. mars 2015 17:38
Til: Frode Odde CARLSEN
Kopi: geoserver-devel@lists.sourceforge.net
Emne: Re: [Geoserver-devel] Maven repositories and plugins

On Tue, Mar 24, 2015 at 5:12 PM, Frode Odde CARLSEN <fc@…4238…> wrote:

Hi,

I’m working on an application at the moment, where we use jetty as the container for geoserver and assemble this with the war and necessary plugins into an installable container which we use in a microservice architecture. For this we need access to the wars and the plugins (*.zip files) available, but I don’t see that they are published to the repository at repo.boundlessgeo.com

Would it be possible to publish the war files and the zipped plugins to the repository? At the moment we’re having to upload these manually to our own repository, which is a pain with every version upgrade.

Also, the extra zip files created for the plugins might they be added to the deployment by using the maven assembly plugin? This would reduce the dependency on the shell scripts for a complete build and deployment. I’d be happy to supply a pull request.

I cannot talk in terms of extra space consumption on the repository (Boundless will have to speak up), but in terms of getting things done, an open source project is a do-ocracy,
if you are the one doing the work of changing the release scripts to get the deploys done (they are in git too), personally I won’t complain :wink:

However, I would like to point out assembling zip and wars is not the recommended way to create a customized GeoServer,
you should take web/app, copy it, change its dependencies to fit your needs, and build it to get the exact war you need.
When you need to create a new version, just update the version number, rebuild, done.

Cheers
Andrea

==

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

==

Ing. Andrea Aime

@geowolf
Technical Lead

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

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

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.