Hi,
I'm wondering what's going on with the web-app packaging when we do the
releases.
The normal snapshot jars are fine, jars will classes that one can depend on
while building a GS web application including or building upon GeoServer,
e.g.
http://repo.opengeo.org/org/geoserver/web/web-app/2.1-SNAPSHOT/
However the release versions are all 40-50MB monsters which are really
the war under a different name:
http://repo.opengeo.org/org/geoserver/web/web-app/2.1-RC2/
Which means it's not really possible to build a derivative web app from them
(unless one uses web overlays, a mechanism that I really don't like, it's slow
and apparently makes it impossible to start the resulting project with
the embedded Jetty, so it's also an utterly unproductive setup)
Anyone knows what's going on here?
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 333 8128928
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
Hmmm… odd indeed. I can’t think of any explicit configuration that causes this to happen. I know the web-app pom attaches a war install to the regular install phase. I wonder if maybe if the version is a non snapshot it also deploys it as well. A useful test would be to comment out the war configuration in web/app/pom.xml and do a deploy to see if the war gets uploaded.
On Tue, Mar 15, 2011 at 12:06 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:
Hi,
I’m wondering what’s going on with the web-app packaging when we do the
releases.
The normal snapshot jars are fine, jars will classes that one can depend on
while building a GS web application including or building upon GeoServer,
e.g.
http://repo.opengeo.org/org/geoserver/web/web-app/2.1-SNAPSHOT/
However the release versions are all 40-50MB monsters which are really
the war under a different name:
http://repo.opengeo.org/org/geoserver/web/web-app/2.1-RC2/
Which means it’s not really possible to build a derivative web app from them
(unless one uses web overlays, a mechanism that I really don’t like, it’s slow
and apparently makes it impossible to start the resulting project with
the embedded Jetty, so it’s also an utterly unproductive setup)
Anyone knows what’s going on here?
Cheers
Andrea
–
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 333 8128928
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.