I just tried working on fixing this one at home and find myself rather stuck,
GeoServer currently won't build JAIMapResponse is commited in terms of
DefaultMapContext - and this class is not in any of the jars commited to the
GeoServer libs directory.
So either I have caught someone in the middle of fixing everything I am out of luck.
Jody
On Thursday 08 April 2004 05:39, jgarnett@anonymised.com wrote:
I just tried working on fixing this one at home and find myself rather
stuck, GeoServer currently won't build JAIMapResponse is commited in terms
of DefaultMapContext - and this class is not in any of the jars commited to
the GeoServer libs directory.So either I have caught someone in the middle of fixing everything I am out
of luck.
That class is in the map module. You do need to add it to the libs.
Best regards
Andrea Aime
Quoting Andrea Aime <andrea.aime@anonymised.com>:
On Thursday 08 April 2004 05:39, jgarnett@anonymised.com wrote:
> I just tried working on fixing this one at home and find myself rather
> stuck, GeoServer currently won't build JAIMapResponse is commited in terms
> of DefaultMapContext - and this class is not in any of the jars commited to
> the GeoServer libs directory.
>
> So either I have caught someone in the middle of fixing everything I am out
> of luck.That class is in the map module. You do need to add it to the libs.
Thanks Andrea: I am not sure that David our I were very clear in describing our
problem. We did not know how to generate the new jars to add to the libs.
But I now, after a couple hours, have the answer.
The wiki (not the developers guide) has the important maven goal we were looking
for (http://docs.codehaus.org/display/GEOTOOLS/How+to+cut+a+release).
And that goal is:
maven -Drelease.version=2.0-B3 createRelease
GeoServer has been using its own ant script assemble jars, recently it has
switched over to tracking the 2.0-B? releases. This set back is all about
lacking a clear jar update procedure in between 2.0-B? releases.
Cheers,
Jody
The libs have now been updated, the ant build files has as well.
Both scrips are not perfect:
- maven builds a gt2-opengis jar that ant simply squishes into gt2-main.jar
- ant builds a gt2-property jar that maven does not
If someone who understands the maven script can tell me what goes into the
opengis-2.0-B3.jar we can teach the ant script to follow suite.
But the long and short of it is that GeoServer development can proceed again.
Jody
> That class is in the map module. You do need to add it to the libs.
Thanks Andrea: I am not sure that David our I were very clear in describing
our
problem. We did not know how to generate the new jars to add to the libs.But I now, after a couple hours, have the answer.
The wiki (not the developers guide) has the important maven goal we were
looking
for (http://docs.codehaus.org/display/GEOTOOLS/How+to+cut+a+release).And that goal is:
maven -Drelease.version=2.0-B3 createReleaseGeoServer has been using its own ant script assemble jars, recently it has
switched over to tracking the 2.0-B? releases. This set back is all about
lacking a clear jar update procedure in between 2.0-B? releases.Cheers,
Jody
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.Compare, Download & Develop Open Source & Business Software - SourceForge
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel