Build failed on latest environment
See original GitHub issue👀 http://redpen.cc/docs/latest/#_for_developers
$ git rev-parse HEAD
ed621501a7ec1840ba5f97adeea064f2e5be7235
$ ./mvnw clean install
...(omitted)...
[INFO] ------------------------------------------------------------------------
[INFO] Building redpen-core 1.10.3-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for org.codelibs:lucene-analyzers-kuromoji-ipadic-neologd:jar:4.10.4-20150608 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
...(omitted)...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.597 s
[INFO] Finished at: 2019-05-15T14:34:48+09:00
[INFO] Final Memory: 8M/28M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project redpen-core: Could not resolve dependencies for project cc.redpen:redpen-core:jar:1.10.3-SNAPSHOT: Failure to find org.codelibs:lucene-analyzers-kuromoji-ipadic-neologd:jar:4.10.4-20150608 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
org.codelibs:lucene-analyzers-kuromoji-ipadic-neologd
is gone?
refs #860 I’m talking with @sfujiwara
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Gradle build failed on a new local environment - Stack Overflow
I'm suspecting this is related to gradle but my initial google search got me nowhere. There shouldn't be anything wrong with the project...
Read more >Build failure with latest Trusty environment #8078 - GitHub
I am experiencing build failures on all my repositories (with sudo-enabled environments) after the trusty environment has been updated as of ...
Read more >Error: Module build failed: Error: Node Sass does not yet ...
This error happened with me after upgrade of node.js. Cause: Node Sass version is not compatible with Node.js version. Solution: you should check...
Read more >Troubleshoot environment images - Azure Machine Learning
Learn how to troubleshoot issues with environment image builds and package installations.
Read more >My build failed. What's wrong with my change? | Saros
In case the build has failed it can be difficult to find the error in the ant log. The easiest is to search...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@vvakame Thank you very much for the valuable report 🙏 !
I confirmed
com.github.cstoku:elasticsearch-analysis-kuromoji-unidic-neologd
exists inMvan central.https://search.maven.org/artifact/com.github.cstoku/elasticsearch-analysis-kuromoji-unidic-neologd/2.3.2.0/jar
Maybe the version specified in pom.xml is no longer exist in the Maven central. I will look into this problem soon.
thanks! let’s go sfujiwara!