The user guide link points to geotools-2.7.3-userguide.zip.
I think you can confidently say that this is the last release made from SVN (and thank OSGeo System Admin Committee for hosting the svn repository).-- Jody Garnett
That looks good. Thanks, Victor.
On 04/07/12 11:54, victor@csiro.au wrote:
> Hi, I have announced the release on
>
> Hi,
>
> I have made the release announcement on
>
> http://geotoolsnews.blogspot.com.au/2012/07/geotools-80-rc2-released.html
>
> please take the time to go through it if you ca
Hi, I have announced the release on
Hi,
I have made the release announcement on
http://geotoolsnews.blogspot.com.au/2012/07/geotools-80-rc2-released.html
please take the time to go through it if you can and let me know if any changes
are required before I announce it on the user mailing list :
On 03/07/12 21:26, David Winslow wrote:
> You could also put a .gitignore in the gt-jdbc-h2 folder.
Good thingking. Adding modules/plugin/jdbc/jdbc-h2/.gitignore works
perfectly, as long as it includes itself:
.gitignore
null.2.log.db
null.data.db
null.index.db
null.trace.db
The problem is, wha
The old wiki's are still in place (you just need to sign in to confluence to
see them):
1) http://docs.codehaus.org/display/GEOTOOLS/Home\
- did a search and did not come up with anything (a few reviews of EMF when it
was being compared to GML General Feature model)
2) http://docs.codehaus.org
Sigh... this is definitely not it. Do we have an old dump of the developer
guide somewhere around? I guess from an old release, maybe i will look
there.
On Tue, Jul 3, 2012 at 6:46 PM, Jody Garnett wrote:
> I have email saved from you helping Gabriel with emf but no docs.
>
> But most times you
I have email saved from you helping Gabriel with emf but no docs.
But most times you volunteer and do the work :)
All the good bits are here:
http://docs.geotools.org/latest/userguide/library/xml/internal/index.html
--
Jody Garnett
On 04/07/2012, at 12:55 AM, Justin Deoliveira wrote:
Hey Jod
Justin, it's good to have these different workflows explained (canonical VS
personal feature branch). Perhaps worth adding the feature branch workflow
to the Git doc, under the Git Primer section?
On Sat, Jun 30, 2012 at 12:55 PM, Justin Deoliveira wrote:
>
> That is, how is one's fork kept in s
Hey Jody,
A while back I wrote up a document describing how to work with and
instrument the emf models that live in geotools. I can't for the life of me
find it in confluence and it doesn't seem to have been ported over to the
sphinx docs. Any ideas? I might be way off but if memory serves me writ
Good to know. With the way our commit policies are structured today (and
these are naturally heavily influenced by the old svn model) github pull
requests are really only going to be useful for people who don't have
commit access / push rights to the canonical repository. Its a much handier
workflo
If (part of) the motivation for encouraging developer forks is to allow the
use of Github pull requests then I think I should point out that Github
allows pull requests within the same repository now (no forks necessary.)
They didn't when they first introduced pull requests. See
https://help.github
You could also put a .gitignore in the gt-jdbc-h2 folder. But I suppose if
you are really the only one working on it then it doesn't make too much
difference one way or the other.
--
David Winslow
OpenGeo - http://opengeo.org/
On Tue, Jul 3, 2012 at 1:44 AM, Ben Caradoc-Davies <
ben.caradoc-dav.
> > This would finally let us recover for the darn for-each loop. FeatureReader
> > and FeatureWriter should also implement closable.
> >
> > Java 6: close() would throw IOException
>
> Looks good to me. As said in the past, imho it has been a mistake not to
> throw IOException from
> the oth
Jody Garn
I updated the wiki so we have a landing page for the 9.x stream, and shuffled
the recently completed proposals into the correct location:
- http://docs.codehaus.org/display/GEOTOOLS/Home
- http://docs.codehaus.org/display/GEOTOOLS/Proposals
> The 8.x branch has been cut.
>
> https://github.co
Moved this under 8.x:
- http://docs.codehaus.org/display/GEOTOOLS/Transition+to+GitHub
Also went over the docs:
JD: Update the documentation for checkout and build (can use the uDig docs as a
good starting point for this)
Source Code
(http://docs.geotools.org/latest/userguide/advanced/build/so
On Mon, Jul 2, 2012 at 4:23 AM, Jody Garnett wrote:
> I mentioned this a couple weeks ago; but after reading into the Java 7
> pipeline and Juno support for try-with-resource I am even more convinced
> that this is a necissary change for GeoTools 9.x.
>
> Reading:
> -
> http://docs.oracle.com/ja
On Tue, Jul 3, 2012 at 9:00 AM, Jody Garnett wrote:
> Aside: I don't think I yet fully comprehend the purpose of our
> developer forks. I'm using "Pro Git" as my reference book and its
> discussion of alternative work-flows for projects, developer forks are
> only mentioned in the context of very
On Mon, Jul 2, 2012 at 5:10 PM, Justin Deoliveira wrote:
> I actually did add one when i setup the initial repo.
>
> https://github.com/geotools/geotools/blob/master/.gitignore
>
> Not 100% sure i get why we should not have one in the repo Ben?
>
Me neither honestly. Yes, it exposes some Eclipse
On 03/07/12 15:00, Jody Garnett wrote:
>> Apologies for so many entry-level questions.
> bah - no apologies - we need entry level questions so we can continue to
> beat answers out of justin.
+1.
My inbox is currently full of emails that constitute A Compilation of
the Git Wisdom of Justin.
(My
> Aside: I don't think I yet fully comprehend the purpose of our
> developer forks. I'm using "Pro Git" as my reference book and its
> discussion of alternative work-flows for projects, developer forks are
> only mentioned in the context of very restricted access to the
> canonical repo, ie. I woul
21 matches
Mail list logo
