[EMAIL PROTECTED] a écrit :
>> As for Clover, last time I tried, I had to copy the
>> 'maven/build-configs/src/gt2/clover.license' file by hand in a 'gt2'
>> directory in order to get Clover running. I don't know if it is the
>> intented behavior or not.
>
> It is not. It should be picked up f
What about the following Jaloppy changes?
@@ -251,7 +251,7 @@
0
-*:0|gnu:2|java:2|javax:2
+
*:0|java:1|javax:1|gnu:1|com.vividsolutions:3|org.opengis:2|org.geotools:2
disabled
true
@@ -407,7 +407,7 @@
true
tru
Baseline is, IMHO, GeoServer should start following geotools releases
a bit closer (Geotools trunk is 2.4.x and GeoServer is built against
2.2.x, too bad) in order to avoid fixing the same errors X times in a
row.
Yes, I definitely agree. The main reason we haven't in the past is
geotools ha
Hello Jan
What about the following modification?
1) Replace CRSException by the following one (which in my understanding reflect
the kind of error involved):
http://geoapi.sourceforge.net/pending/javadoc/org/opengis/spatialschema/geometry/MismatchedReferenceSystemException.html
2) Rename "Abst
Hi all,
Our sys admin did a bunch of tests today and wasn't able to find any
major bottle necks committing to svn. He even tried using a remote
server in Amsterdam. So he was wondering if maybe it was a timing
issue. Could you email him the times when SVN is slow? His address
is [EMAIL
Indexed shapefile getReader() will return too few attributes to satisfy a filter
Key: GEOT-978
URL: http://jira.codehaus.org/browse/GEOT-978
Project: GeoTools
I
Doesn't take into account the layer's Query
---
Key: GEOT-977
URL: http://jira.codehaus.org/browse/GEOT-977
Project: GeoTools
Issue Type: Bug
Components: ext shapefilerender
Repor
Upgrated to maven-javadoc-plugin version 2.1, which fixes a number of bugs. The
Maven build do not fails anymore when running "mvn javadoc:javadoc" -
dependencies are found, and all taglets work.
Changes applied from revision 22110 to 22113 (inclusive) on trunk. Shall we
merge to the 2.3 branch
I commited as of revision 22110 a CommonFactoryFinder class that may be used as
a replacement of StyleFactoryFinder and FilterFactoryFinder (I have not yet
replaced the references to those factories finder however). Peoples asked for
constructor injection. Do we have a volunter for adding the ap
Martin Desruisseaux a écrit :
> Test set: org.geotools.validation.relate.MemoryLeakTest
> ---
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.797 sec <<<
> FAILURE!
Sorry, I didn't noticed that this te
Do I'm the only one to get this test failure?
Martin
---
Test set: org.geotools.validation.relate.MemoryLeakTest
---
Tests run: 2, Failur
Does I'm the only one to get this test failure?
Martin
---
Test set: org.geotools.validation.relate.MemoryLeakTest
---
Tests run: 2, Fail
Cory Horner ha scritto:
> I've corrected the poms on 2.2.x. Looking at the release instructions
> and commits, it seems Andrea did the release correctly and it is maven
> that is misbehaving (surprise!). I've amended the release instructions
> with a snippet to fix the branch after performing
Justin Deoliveira ha scritto:
> Its not really a failure, and the cite engine is probably the only thing
> that would complain about it. It places an additional restriction on fid
> format.
>
> We could have easily fixed it just by slightly changing our cite script
> as well. However I think that
Its not really a failure, and the cite engine is probably the only thing
that would complain about it. It places an additional restriction on fid
format.
We could have easily fixed it just by slightly changing our cite script
as well. However I think that a check for oids is probably a worth while
I've corrected the poms on 2.2.x. Looking at the release instructions
and commits, it seems Andrea did the release correctly and it is maven
that is misbehaving (surprise!). I've amended the release instructions
with a snippet to fix the branch after performing a release, as
maven-release cor
Hi Andrea, seems we are into day number 2.
> Sorry, I thought the procedure was first release then try CITE but yes,
> now I think about it, it does not make sense...
No worries, have the time I give it a day and cite tests are not run
anyways. Lets just be sure Justin provided a test case showing
Adrian Custer ha scritto:
> Hey all,
>
> I don´t know what the situtation is with 2.2.x. On 2.3.x, therefore
> using the mvn javadoc plugin, the javadocs are *not* generated during
> the release process and therefore are *always* generated with the
> wrong version information. I suspect this only
Hey all,
I don´t know what the situtation is with 2.2.x. On 2.3.x, therefore
using the mvn javadoc plugin, the javadocs are *not* generated during
the release process and therefore are *always* generated with the
wrong version information. I suspect this only influences information
in the root win
Hi,
In org.geotools.styling.StyleFactoryImpl.GetDefaultFont(), line 586
reads:
font.setFontFamily(filterFactory.createLiteralExpression("serif"));
Should the 's' of "serif" be capitalized?
For example, I find that the MapPane demo logs a lot of errors (one for
each label) because SLDStyleFactor
Hi guys,
yesterday bad news were not complete, one of the commercial apps I'm mantainer
of had problems and today I have to fix it, so I don't know if I can help
with the release of 2.2.1a, 2.2.2, whatever it is...
If I'm online you'll know, otherwise if you feel like going on without me, do
it.
Jody Garnett ha scritto:
> Justin Deoliveira wrote:
>> Confirmed, a patch I recently applied to postgis has broken cite tests.
>> It wont be show stopping for anything else besides geoserver cite tests,
>> so I am not sure how people want to proceed, halt the release or keep
>> going and throw out
22 matches
Mail list logo
