Importing log4j-s3-search in gradle is broken
hasenbanck opened this issue · 5 comments
It seems that the POM of the maven repository is broken.
Importing the libraries in gradle using following dependencies:
compile group: 'com.therealvan', name: 'appender-core', version: '2.1.0'
compile group: 'com.therealvan', name: 'appender-log4j2', version: '2.1.0'Results in following error message from gradle when building the project:
> Task :compileJava FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Could not resolve all files for configuration ':compileClasspath'.
> Could not resolve com.therealvan:appender-core:2.1.0.
Required by:
project :
> Could not resolve com.therealvan:appender-core:2.1.0.
> Could not parse POM https://repo.maven.apache.org/maven2/com/therealvan/appender-core/2.1.0/appender-core-2.1.0.pom
> Could not find com.therealvan:log4j-s3-search:2.1.0.
> Could not resolve com.therealvan:appender-log4j2:2.1.0.
Required by:
project :
> Could not resolve com.therealvan:appender-log4j2:2.1.0.
> Could not parse POM https://repo.maven.apache.org/maven2/com/therealvan/appender-log4j2/2.1.0/appender-log4j2-2.1.0.pom
> Could not find com.therealvan:log4j-s3-search:2.1.0.Looking at the POMs, it seems that the parent configuration key is not right (there is no package "log4j-s3-search"):
<parent>
<groupId>com.therealvan</groupId>
<artifactId>log4j-s3-search</artifactId>
<version>2.1.0</version>
</parent>Hm. Sorry about that. Let me look into this.
OK. This has always been broken, it seems. Even w/ Maven (as opposed to Gradle), if I delete .m2/repository and rebuild a test program having only appender-core and appender-log4j, it will complain about the parent project missing.
I am in the process of releasing the parent pom into mvn repository. Thanks for your patience.
2.1.1 has been released to oss.sonatype.org. It will take some time for things to propagate to mvnrepository.org.
We can now import the library in our gradle project. Thank you for the fix.