Ami fails to compile

[egonw]

When I run "mvn package" (per README), I get this compile error:

[ERROR] Failed to execute goal on project ami2: Could not resolve dependencies for project org.xml-cml:ami2:jar:0.3.0: Failed to collect dependencies for [org.xml-cml:norma:jar:0.3.0 (compile), org.xml-cml:diagramanalyzer:jar:0.1-SNAPSHOT (compile), org.apache.lucene:lucene-core:jar:4.10.3 (compile), org.apache.lucene:lucene-analyzers-common:jar:4.10.3 (compile), com.google.guava:guava:jar:18.0 (compile), junit:junit:jar:4.11 (test), blogspot.software-and-algorithms:stern-library:jar:0.1 (compile), org.vafer:jdeb:jar:1.3 (provided), com.jayway.jsonpath:json-path:jar:2.0.0 (compile), com.univocity:univocity-parsers:jar:1.5.6 (compile)]: Failed to read artifact descriptor for org.xml-cml:norma:jar:0.3.0: Could not transfer artifact org.xml-cml:norma:pom:0.3.0 from/to ebi-repo (http://www.ebi.ac.uk/intact/maven/nexus/content/repositories/ebi-repo/): Failed to transfer file: http://www.ebi.ac.uk/intact/maven/nexus/content/repositories/ebi-repo/org/xml-cml/norma/0.3.0/norma-0.3.0.pom. Return code is: 500 , ReasonPhrase:Internal Server Error. -> [Help 1]

I like to get a build environment as I want to write a plugin to use a controlled list of nanomaterial names ("NM-100") to be extracted the occurrence of articles...

[petermr]

Thanks - I will try to get a new AMI released which will have better dependencies.

…

On Tue, Nov 29, 2016 at 6:59 AM, Egon Willighagen ***@***.***> wrote: When I run "mvn package" (per README), I get this compile error: [ERROR] Failed to execute goal on project ami2: Could not resolve dependencies for project org.xml-cml:ami2:jar:0.3.0: Failed to collect dependencies for [org.xml-cml:norma:jar:0.3.0 (compile), org.xml-cml:diagramanalyzer:jar:0.1-SNAPSHOT (compile), org.apache.lucene:lucene-core:jar:4.10.3 (compile), org.apache.lucene:lucene-analyzers-common:jar:4.10.3 (compile), com.google.guava:guava:jar:18.0 (compile), junit:junit:jar:4.11 (test), blogspot.software-and-algorithms:stern-library:jar:0.1 (compile), org.vafer:jdeb:jar:1.3 (provided), com.jayway.jsonpath:json-path:jar:2.0.0 (compile), com.univocity:univocity-parsers:jar:1.5.6 (compile)]: Failed to read artifact descriptor for org.xml-cml:norma:jar:0.3.0: Could not transfer artifact org.xml-cml:norma:pom:0.3.0 from/to ebi-repo (http://www.ebi.ac.uk/intact/maven/nexus/content/repositories/ebi-repo/): Failed to transfer file: http://www.ebi.ac.uk/intact/maven/nexus/content/repositories/ebi-repo/org/xml-cml/norma/0.3.0/norma-0.3.0.pom. Return code is: 500 , ReasonPhrase:Internal Server Error. -> [Help 1] I like to get a build environment as I want to write a plugin to use a controlled list of nanomaterial names ("NM-100") to be extracted the occurrence of articles... — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#62>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAsxSz3TBNUTMrbMNVflksnt7cfTe2Gsks5rC81tgaJpZM4K-oeD> .

-- Peter Murray-Rust Reader Emeritus University of Cambridge +44-1223-763069 and ContentMine Ltd

[egonw]

OK, it seems to need patches in @petermr's dev/ branch of cmine... I will now give that a try...

[egonw]

ah, wrong... I now see the s/cmine/cproject/ patch... so this ami branch needs updating for that...

[egonw]

So, I need an ami/ branch which is updated for the cmine/cproject migration... I now have >170 compile fails... some of these are simple cmine/cproject changes, but I also see API changes...

Is there an ami/ branch that is updated to use cproject?

[egonw]

I sort of got this working now with this patch: #68