Looking at the latest (? Oxygen) version of eclipse - it seems to have
moved to be on the windows->preferences->errors/warnings page -> plugin
execution not covered set to Ignore.
Ian
On Fri, 25 Oct 2019 at 13:31, Luís Moreira de Sousa <
luis.de.so...@protonmail.ch> wrote:
> Hi Ian,
>
> I did
Hi Luis,
I'm afraid there is a underlying assumption, that to use those instructions
one has to be proficient with Maven and Java.
I literally followed them verbatim, just generated the classpath and
replaced the _CLASS_PATH_ variable in the
second script with that value.
If you can make a PR to
Hi Ian,
I did not manage to do as you say, I could not find the option to ignore these
error messages. Which Perspective are you using?
Thank you.
--
Luís
Sent with [ProtonMail](https://protonmail.com) Secure Email.
‐‐‐ Original Message ‐‐‐
On Thursday, October 24, 2019 6:13 PM, Ian
Hi Andrea,
thank you for taking the time to address this. The good news is that I manage
to run the tests following your exact instructions. However, neither from the
guide, nor from the instructions in the test file, would I gather the
parameters passed to maven, or the correct folder from
On Thu, Oct 24, 2019 at 6:08 PM Luís Moreira de Sousa <
luis.de.so...@protonmail.ch> wrote:
> Hi Andrea,
>
> I started by trying Eclipse, but all projects trigger errors related to
> the pom.xml file. So far, the only section in the documentation that
> provides information on how to set up a
All the eclipse "errors" are actually warnings about maven lifestyle issues
and if you right click them and set ignore in preferences they go away -
there should be a note in the docs (or may be I only put that into the
GeoServer ones).
Ian
On Thu, 24 Oct 2019 at 17:09, Luís Moreira de Sousa
Hi Andrea,
I started by trying Eclipse, but all projects trigger errors related to the
pom.xml file. So far, the only section in the documentation that provides
information on how to set up a development environment with Eclipse is the
build FAQ [0], which is possibly incomplete. If there is
Hi Luis,
we normally run those tests from a full blown Java IDE, don't think anyone
has tried to
do that from the command line in ages, and it requires quite some
familiarity with how both
Java and Maven work (e.g., stuff like the test classes ending up in
target/test/classes is
something
Hello again,
I located a .class file for ScriptRunner in
modules/library/referencing/target/test-classes and added it to the class path.
Like this the test can be run, but it is seeking the test scripts in the wrong
folder:
$ java -cp
Hi Mark,
thank you for your reply. mvn test-compile runs without errors, but it does
not create the test-classes folder inside ./target.
Thanks.
--
Luís
Sent with [ProtonMail](https://protonmail.com) Secure Email.
‐‐‐ Original Message ‐‐‐
On Monday, October 21, 2019 7:23 PM, mark
On 10/21/19 11:59 AM, Luís Moreira de Sousa via GeoTools-Devel wrote:
Hi all,
I am trying to run the projections tests. They all complain of the
absence of ScriptRunner, e.g.:
$ java -cp target/classes:target/test-classes:$CLASSPATH -ea
org.geotools.referencing.ScriptRunner
Hi all,
I am trying to run the projections tests. They all complain of the absence of
ScriptRunner, e.g.:
$ java -cp target/classes:target/test-classes:$CLASSPATH -ea
org.geotools.referencing.ScriptRunner
src/test/resources/org/geotools/referencing/test-data/scripts/Sinusoidal.txt
Error:
12 matches
Mail list logo
