Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [udig-dev] GSoC 13 - Starting JGrassTools framework discovery
I love when I get to this point in GSoC: environment setup time.
It is perhaps the most enjoyable part of the whole game! ;-)

After issuing a:

   git clone https://code.google.com/p/jgrasstools/

I then tryied a:

   mvn eclipse:eclipse

and I got to an error.
It seems that

https://code.google.com/p/jgrasstools/source/browse/pom.xml

is referring to the NOT-EXISTING repository:

<repository>
      <id>JBOSS</id>
      <name>JBoss Repository</name>
      <url>http://repository.jboss.org/maven2/</url>
    </repository>
 
I suspect this is the cause of the subsequent error:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JGrasstools - uDig's geospatial toolbox (but not only)  SUCCESS [1.264s]
[INFO] Object Modeling System (JGrasstools package) ...... SUCCESS [0.372s]
[INFO] JGrass Gears ...................................... FAILURE [2.709s]
[INFO] The Horton Machine ................................ SKIPPED
[INFO] GRASS bindings module ............................. SKIPPED
[INFO] JGrasstools Simple Modules Wrapper ................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.797s
[INFO] Finished at: Fri Jul 19 16:26:19 CEST 2013
[INFO] Final Memory: 9M/22M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project jgt-jgrassgears: Could not resolve dependencies for project org.jgrasstools:jg
t-jgrassgears:jar:0.7.7-SNAPSHOT: Could not transfer artifact org.jgrasstools:jgt-oms3:jar:0.7.7-SNAPSHOT from/to JBOSS
.7-SNAPSHOT/jgt-oms3-0.7.7-SNAPSHOT.jar, ReasonPhrase:Forbidden. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :jgt-jgrassgears

Am I mad or just missing something silly?

More: Andrea can you please give me EditWiki permissions so I can eventually improve/fix documentation of JGrassTools ?

Thanks

Marco


2013/7/19 andrea antonello <andrea.antonello@xxxxxxxxx>
Hi Marco,
finally I get to work :)

> Today I could finally complete the review of the R script by Cristiano
> Lanni: it was a bit harder than expected and it took longer than due.. ..but
> I can now fully appreciate how useful is having this 'blueprint' for the
> logic I will implement in the model.

sure thing.

> In a private mail exchange between Andrea and me, he suggested me, as a
> first step, to implement the model as a java standalone to be moved into a
> JGrass module in a second phase.
>
> Andrea: can you expand a bit this idea?

Well, this was a proposal due to your requirements boudn to the
university, I would never do that right now :)
I used to do it in the past to bridge the difficulty to first
understand a framework and wanting first to make sure that the module
works properly.
Right now, the oms framework is so simple and non-invasive, that you
can go right away with it.

> I was expecting to rely on some JGrass/GeoTools feature to load input data
> in memory and start working the resulting objects to implement the logic.
> For sure I can rewrite the R code in Java and reproduce the smart matrix
> computation functions available in R.. ..but this would probably lead to
> some badly performing tool.
> In short I cannot see the advantage of this intermediate step: can you
> explain why are you suggesting it? I am surely missing something due to my
> ignorance about the involved libraries!

Well, I think the best thing is to get started on the jgrasstools
developers documentation:
https://code.google.com/p/jgrasstools/wiki/Contribute

I am sure there will be some outdated stuff, but this will also be a
good moment to upgrade it. Recently we had a quite invasive move in
the modules, so that it would be simple to use jgrasstools in the
scripting engine.

So check the docs and then feel free to ask/enhance whatever you need.

Remember, creating a jgrasstools module is as simple as writing your
module without the IO part and then adding some annotations to define
inputs/outputs and processing.

There are already several reader for rasters and vector data, check
https://code.google.com/p/jgrasstools/wiki/RasterReader
and surroundings.

Cheers,
Andrea



>
> Thanks!
>
> Marco
>
>
>
> _______________________________________________
> udig-dev mailing list
> udig-dev@xxxxxxxxxxxxxxxx
> https://locationtech.org/mailman/listinfo/udig-dev
>
_______________________________________________
udig-dev mailing list
udig-dev@xxxxxxxxxxxxxxxx
https://locationtech.org/mailman/listinfo/udig-dev

Back to the top