+1 here too.
---
Ing. Alessio Fabiani
Founder / CTO GeoSolutions S.A.S.
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: (+39) 0584 96.23.13
fax: (+39) 0584 96.23.13
mobile:(+39) 349 82.27.000
HI Devs,
I am interested in the project to implement a RestConfig client for Geo
server using the existing A.Since i am new to Geoserve i started from
building the trunk and following the sample tutorials
to understand the project.I was able to test run with in the IDE and deploy
in tomcat
Allow log file location to be overridden by enviroment variable
---
Key: GEOS-4334
URL: http://jira.codehaus.org/browse/GEOS-4334
Project: GeoServer
Issue Type: Bug
Affects
Dear all,
thank you for proposing me Andrea, and thanks to Justin and Alessio
for giving green light for me :)
Justin, Ive read about commit policies and things are pretty clear.
There won't be any committing done before patches get reviewed from
the community.
I will create account at xircles
Hi,
i've just applied to xircles.codehaus.org , waiting for your confirmation now :)
Cheers,
Ivan
On Thu, Jan 27, 2011 at 1:11 PM, Ivan Grcic igr...@gmail.com wrote:
Dear all,
thank you for proposing me Andrea, and thanks to Justin and Alessio
for giving green light for me :)
Justin, Ive
Hi,
in a production system we're setting up we have a cluster of GeoServer all
sharing the same NFS mounted data directory.
Generally it works fine but the log file is shared among all the instances,
which is not exactly the best solution (as the writes will happen concurrently).
I think for this
On Thu, Jan 27, 2011 at 1:14 PM, Ivan Grcic igr...@gmail.com wrote:
Hi,
i've just applied to xircles.codehaus.org , waiting for your confirmation now
:)
Done, you can now commit using the same username and password
you use for jira or xircles
Cheers
Andrea
--
Ing. Andrea Aime
Technical
See http://hudson.opengeo.org/hudson/job/geoserver-trunk/3493/
--
[...truncated 25408 lines...]
[WARNING] the build.path property is already defined, its value will be
overwritten. Consider another value for the entry properties prefix.
[WARNING] the
There's actually already a Java client for RESTConfig in the community
modules section of the source repository - so a good first step would be to
read over that code and try to use it for a few tasks. If you don't find
any bugs while doing that, perhaps you could start working on a section of
Hi David
Thank You very much.I will have look and test the implementation.
On Thu, Jan 27, 2011 at 6:54 PM, David Winslow dwins...@opengeo.org wrote:
There's actually already a Java client for RESTConfig in the community
modules section of the source repository - so a good first step would be
On Thu, Jan 27, 2011 at 3:39 PM, Justin Deoliveira jdeol...@opengeo.org wrote:
Patch looks good. Added my +1.
Thanks for the review (Gabriel too).
I've committed the changes
Cheers
Andrea
--
Ing. Andrea Aime
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
See http://hudson.opengeo.org/hudson/job/geoserver-trunk/3494/changes
--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Oracle Documentation - additional note on schema setting
Key: GEOS-4335
URL: http://jira.codehaus.org/browse/GEOS-4335
Project: GeoServer
Issue Type: Improvement
Components:
So how are we feeling about 2.1.0? RC1 has been out 1.5 weeks. Can we put
together a schedule for 2.1.0? Do we need another RC? I haven't been
following the lists super closely, but I haven't seen any blockers yet. But
we've also had some smaller fixes I think. Do we put out another RC and
Sounds like we are on track Chris; any feedback or problems on the user list to
worry about?
Jody
On 28/01/2011, at 7:23 AM, Chris Holmes wrote:
So how are we feeling about 2.1.0? RC1 has been out 1.5 weeks. Can we put
together a schedule for 2.1.0? Do we need another RC? I haven't been
Hi GeoServer Developers,
I'm in both user and developer mailing list as most of the time check the
codes while developing GIS solution in limited time period. Some of the
features released in this GeoServer 2.1 series are key/important features
for GIS solution i worked/i consider such as
1.
Direct raster path does not support opacity
---
Key: GEOS-4336
URL: http://jira.codehaus.org/browse/GEOS-4336
Project: GeoServer
Issue Type: Bug
Affects Versions: 2.1-RC1
Reporter:
RGBA raster + direct raster path + JPEG output - inverted colors
-
Key: GEOS-4337
URL: http://jira.codehaus.org/browse/GEOS-4337
Project: GeoServer
Issue Type: Bug
Affects
18 matches
Mail list logo
