Pedro,
I'm guessing from the information that you provided that there is a problem
with the format of your WKT "Point" geometry. Or at least OpenJUMP thinks
that there is.
Can you check to make sure the WKT geometry your storing is a valid format
and get back to us?
The Sunburned Surveyor
On
Larry,
It seems I can generate the Javadoc just find using the File>Export>Javadoc
command in Eclipse. So there is defnitely something wrong with how Eclipse
is handling the Ant Script.
It seems like my Javadoc task is only loading the source files and is not
completing the rest of the Javadoc T
Hi Sunburned,
I don't know why your Ant script isn't working. I always use the
Project->Generate Javadoc command. It is always a big deal to me
since every time I update the Javadoc on SourceForge, it seems to take
hours.
You might try adding failonerror="false" if you haven't already.
Lar
I'm trying to put the finishing touches on the OpenJUMP/OpenJUMP-Ex Ant
Build file that I've been working on. I've got everything but the Javadoc
task working. Here is the portion of my Ant build file that generates the
Javadoc for OpenJUMP:
Hi all,
I'm agree with Larry. I'm also paranoiac (Google is very hungry) .I think
that sourceforge is very well.
However if you want system more "user friendly" look at Trac Plateform
http://trac.edgewall.org/.
We use it now with projet-sigle and at my work (
http://geosysin.iict.ch/irstv-trac/)
Hi Jon,
The main attraction of Google Code to me is the clean and responsive
interface. However, when you compare the features, Google has a long
way to go to catch up with SourceForge, especially the web code
browser, which currently lacks syntax highlighting. That makes it
much more difficul
Thanks Jon. I realized when I downloaded the font that it was recognized by
my Windows XP OS.
SS
On 2/6/07, Jonathan Aquino <[EMAIL PROTECTED]> wrote:
Actually WinXP supports OTF (OpenType) fonts, so you can just drag it
into your Fonts folder.
But to answer your question, I don't know of a
I may be completely wrong here, but is seems that your geometry is encoded
as WKB (Well Known Binary), but the driver is trying to access it as WKT (Well
Known Text).
Inside PostgisValueConverterFactory there's this code:
...
public ValueConverter getConverter(ResultSetMetaData rsm, int c
Hi group,
Trying to execute a valid query for a valid geom. type (point) fires this
baby:
The query:
select friendly_name, curr_location from units where id=8135;
in the table definition:
CONSTRAINT enforce_point CHECK (geometrytype(curr_location) = 'POINT'::text)
The 'baby':
com.v
