Mcreator 1.9.0 Error

Started by tntookcz on

Topic category: Troubleshooting, bugs, and solutions

Joined Sep 2019
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Mcreator 1.9.0 Error
Joined Sep 2019
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
############################…
Thu, 09/19/2019 - 06:19

#################################################
         ForgeGradle 2.3-SNAPSHOT-6084129e        
  https://github.com/MinecraftForge/ForgeGradle  
#################################################
                 Powered by MCP                  
             http://modcoderpack.com             
     by: Searge, ProfMobius, R4wk, ZeuX          
     Fesh0r, IngisKahn, bspkrs, LexManos         
#################################################
:deobfCompileDummyTask
:deobfProvidedDummyTask
:getVersionJson
:extractUserdev UP-TO-DATE
:extractDependencyATs SKIPPED
:extractMcpData SKIPPED
:extractMcpMappings SKIPPED
:genSrgs SKIPPED
:downloadClient SKIPPED
:downloadServer SKIPPED
:splitServerJar SKIPPED
:mergeJars SKIPPED
:deobfMcSRG SKIPPED
[Fatal Error] scala-continuations-library_2.11-1.0.2.pom:3:1: Content is not allowed in prolog.
[Fatal Error] scala-parser-combinators_2.11-1.0.1.pom:2:1: Content is not allowed in prolog.
[Fatal Error] scala-library-2.11.1.pom:2:1: Content is not allowed in prolog.
:decompileMc FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':decompileMc'.
> Could not resolve all files for configuration ':forgeGradleMcDeps'.
> Could not resolve org.scala-lang.modules:scala-parser-combinators_2.11:1.0.1.
     Required by:
         project :
project : > org.scala-lang:scala-compiler:2.11.1
> Could not resolve org.scala-lang.modules:scala-parser-combinators_2.11:1.0.1.
5 actionable tasks: 4 executed, 1 up-to-date
> Could not parse POM https://repo.maven.apache.org/maven2/org/scala-lang/modules/scala-parse…
> Content is not allowed in prolog.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 3m 35s