Re: [Geotools-devel] build troubles with org.geotools.maven:javadoc on a "fresh" box

Hi Jody, The GeoTools javadoc plugin isn't really a plugin at all, in the maven sense. It is just providing the "@source" taglet which we use to get the module info onto each classes page. I looked at the maven javadoc plugin docs a while ago to see if there was an easier way of doing this. It pro

Re: [Geotools-devel] Updating gt-ImageMosaic to leverage on last jai-tools (1.1.1) instead of 1.1-M3 milestone

On Mon, Apr 11, 2011 at 10:57 PM, Andrea Aime wrote: > On Mon, Apr 11, 2011 at 4:04 PM, Daniele Romagnoli > wrote: > > Hi all, > > the gt-imageMosaic actually leverages on jai-tools 1.1-M3. > > Since Michael has released 1.1.1, any objection if I upload the > imageMosaic > > plugin to leverage on

[Geotools-devel] jai and imageio missing

These projects are still missing there downloads after the oracle fun and games moving stuff around. I have updated the developers guide with links to where stuff is supposed to be; currently the only way to proceed is with the imageio-ext one click installer (and copying stuff by hand into your

[Geotools-devel] build troubles with org.geotools.maven:javadoc on a "fresh" box

I am going through the build instructions with a co-worker and running into troubles on a new machine > 1 required artifact is missing. > > for artifact: > org.geotools.maven:javadoc:jar:8-SNAPSHOT > > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > osgeo

Re: [Geotools-devel] GeoTools 8-SNAPSHOT available on trunk

Hmm... Look forward to it On 12 April 2011 14:48, Jody Garnett wrote: > Thanks for answering the questions on the user list; when we first put out a > milestone release :-P > > -- > Jody Garnett > > On Tuesday, 12 April 2011 at 2:33 PM, Michael Bedward wrote: > > Hi Jody > > It all looks good - t

Re: [Geotools-devel] GeoTools 8-SNAPSHOT available on trunk

Thanks for answering the questions on the user list; when we first put out a milestone release :-P -- Jody Garnett On Tuesday, 12 April 2011 at 2:33 PM, Michael Bedward wrote: > Hi Jody > > It all looks good - thanks very much for the work ! > > Michael > > On 11 April 2011 10:06, Jody Garn

Re: [Geotools-devel] GeoTools 8-SNAPSHOT available on trunk

Hi Jody It all looks good - thanks very much for the work ! Michael On 11 April 2011 10:06, Jody Garnett wrote: > Okay I have completed the rest of the paper work: > Blog post: > - http://geotoolsnews.blogspot.com/2011/04/geotools-8.html > Jira: > - https://jira.codehaus.org/browse/GEOT > Wiki

Re: [Geotools-devel] Build failed in Hudson: geotools-trunk #3430

Welcome to the team :-P > Reason: Could not find the model file '< > http://hudson.opengeo.org/hudson/job/geotools-trunk/ws/gt_trunk/modules/unsupported/mark-wkt'.> > for project unknown > > I guess I should have committed the module first, and only then added it to > the > unsupported/pom.xml (I

Re: [Geotools-devel] Updating gt-ImageMosaic to leverage on last jai-tools (1.1.1) instead of 1.1-M3 milestone

On Mon, Apr 11, 2011 at 4:04 PM, Daniele Romagnoli wrote: > Hi all, > the gt-imageMosaic actually leverages on jai-tools 1.1-M3. > Since Michael has released 1.1.1, any objection if I upload the imageMosaic > plugin to leverage on that Stable version? > If nobody is against that, I will update it.

[Geotools-devel] Hudson build is back to normal : geotools-trunk #3432

See -- Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report

Re: [Geotools-devel] Build failed in Hudson: geotools-trunk #3431

On 04/11/2011 09:25 PM, Andrea Aime wrote: > Maybe a Java 6 dependency crept in? That I was thinking too... > GeoTools is a java 5 project Ok, I'll investigate right away. Regards, Luca Morandini http://www.lucamorandini.it

Re: [Geotools-devel] Build failed in Hudson: geotools-trunk #3431

Maybe a Java 6 dependency crept in? GeoTools is a java 5 project Cheers Andrea > [INFO] Compiling 2 source files to > > [INFO] > ---

[Geotools-devel] Build failed in Hudson: geotools-trunk #3431

See Changes: [lmoran] Initial import of Mark WKT module [lmoran] Initial import of Mark WKT module -- [...truncated 14750 lines...] [INFO] -

Re: [Geotools-devel] Build failed in Hudson: geotools-trunk #3430

On 04/11/2011 08:06 PM, Hudson wrote: > See > > Changes: > > [lmoran] Added mark-wkt module to the list > > -- > Started by an SCM change > Updating http://svn.osgeo.org/geotools/trunk > U

[Geotools-devel] Build failed in Hudson: geotools-trunk #3430

See Changes: [lmoran] Added mark-wkt module to the list -- Started by an SCM change Updating http://svn.osgeo.org/geotools/trunk U modules/unsupported/pom.xml At revision 36898 [gt_

Re: [Geotools-devel] Account activation

On 04/11/2011 12:45 PM, Jody Garnett wrote: > Thanks! I have added you into the mix; please let me know if you have an > questions :-) > > If I can ask you as your first commit to update the pom.xml with your details > for > the developers section. Done, apparently with some success. I'll commi

Re: [Geotools-devel] ava.lang.ClassCastException: org.geoserver.security.decorators.SecuredIterator

On Mon, Apr 11, 2011 at 4:39 PM, Justin Deoliveira wrote: > Hi Victor, > > I believe this is a more specifically a geoserver issue... you should > probably move the conversation there. As for the fix I still think modifying > the SecuredObject* interfaces in geoserver to explicitly pass down the >

Re: [Geotools-devel] ava.lang.ClassCastException: org.geoserver.security.decorators.SecuredIterator

Hi Victor, I believe this is a more specifically a geoserver issue... you should probably move the conversation there. As for the fix I still think modifying the SecuredObject* interfaces in geoserver to explicitly pass down the interface is the most robust option. But that is something for discus

Re: [Geotools-devel] broken links on docs page

Awesome, thanks Michael! On Sun, Apr 10, 2011 at 10:16 PM, Michael Bedward wrote: > Thanks Justin, I've just made those changes. Also now have the zip > files being moved to xxx.old.zip after unpacking. Fingers crossed that > it all still works :) > > Michael > > > On 11 April 2011 05:49, Justin

Re: [Geotools-devel] xml docs updated; and stalling out on binding examples

On Sun, Apr 10, 2011 at 4:58 PM, Jody Garnett wrote: > I updated it; it works now. > > Cool. > Do we have an example with EMF? > Nope. Not at this time. > > -- > Jody Garnett > > On Monday, 11 April 2011 at 5:19 AM, Justin Deoliveira wrote: > > Yeah I am wondering if this documentation is eve

[Geotools-devel] Updating gt-ImageMosaic to leverage on last jai-tools (1.1.1) instead of 1.1-M3 milestone

Hi all, the gt-imageMosaic actually leverages on jai-tools 1.1-M3. Since Michael has released 1.1.1, any objection if I upload the imageMosaic plugin to leverage on that Stable version? If nobody is against that, I will update it. I have opened a JIRA for this: http://jira.codehaus.org/browse/GEOT

[Geotools-devel] [jira] Created: (GEOT-3505) Update ImageMosaic to leverage on last jai-tools version (1.1.1)

Update ImageMosaic to leverage on last jai-tools version (1.1.1) Key: GEOT-3505 URL: http://jira.codehaus.org/browse/GEOT-3505 Project: GeoTools Issue Type: Task Re

Re: [Geotools-devel] Account activation

Thanks! I have added you into the mix; please let me know if you have an questions :-) If I can ask you as your first commit to update the pom.xml with your details for the developers section. -- Jody Garnett On Monday, 11 April 2011 at 8:29 PM, Luca Morandini wrote: > Folks, > > to become

[Geotools-devel] Account activation

Folks, to become a maintainer of an (unsupported) module, I had to: sign and send the agreement (which I did), register an account at OSGeo (which I did, "lmoran" is the account), declare these actions to the dev list (which I've done with this message)... now I should be eligible for access to

[Geotools-devel] ava.lang.ClassCastException: org.geoserver.security.decorators.SecuredIterator

Hi Andrea, I am at a lost on how to resolve this issue as it only occurs on specific environment. In our case its a debian server. I believe it's some policy setting to created this issue but I do not know how the policy works and I could not find any documentation on it as well. Would you be