line 208, column The build could not read 1 project -> ‘’ for :spring-boot-starter-thymeleaf:jar is missing. ‘’ for com.h2database:h2:jar is missing. ‘’ for :spring-boot-starter-jdbc:jar is missing. ‘’ for :spring-boot-devtools:jar is missing. ‘’ for :spring-boot-starter-data-jpa:jar is missing. ‘’ for org.springframework:spring-webflux:jar is missing. ‘’ for :spring-boot-starter-webflux:jar is missing. ‘’ for :spring-boot-starter-web:jar is missing. ‘’ for :spring-boot-starter-actuator:jar is missing. Non-resolvable import POM: Could not transfer artifact :camunda-bom:pom:7.9.0 from/to camunda-bpm-nexus ( ): Connect to :443 failed: Connection timed out: connect line 29, column 25 Non-resolvable import POM: Could not transfer artifact :spring-boot-dependencies:pom:2.0.6.RELEASE from/to camunda-bpm-nexus ( ): Connect to :443 failed: Connection timed out: connect line 21, column 25 Some problems were encountered while processing the POMs: "C:\Program Files\Java\jdk-10\bin\java.exe" -Dmaven.multiModuleProjectDirectory=C:\Camunda\bpm\cam-engine "=C:\Program Files\JetBrains\IntelliJ IDEA 2018.3\plugins\maven\lib\maven3" "nf=C:\Program Files\JetBrains\IntelliJ IDEA 2018.3\plugins\maven\lib\maven3\bin\m2.conf" "-javaagent:C:\Program Files\JetBrains\IntelliJ IDEA 2018.3\lib\idea_rt.jar=17467:C:\Program Files\JetBrains\IntelliJ IDEA 2018.3\bin" -Dfile.encoding=UTF-8 -classpath "C:\Program Files\JetBrains\IntelliJ IDEA 2018.3\plugins\maven\lib\maven3\boot\plexus-classworlds-2.5.2.jar" -Didea.version=2018.3 clean I understand that you may want to avoid renames in the general case when there are not clashes, in which case you can just attach a counter suffix to a file only when a clash is detected.I am not able to download Camunda dependencies in IntelliJ. The option of numbering files doesn't strike me as unreasonable: as far as I know, the Sync task is neither cacheable nor incremental, and the up-to-date check doesn't depend on whether the output is deterministic. A better option would be to rename the jar files to use a unique name at the time when they are copied to the sandbox – after all, jar file names are expected to be used within a repository structure where only the full directory path is meant to be unique. I think that the IntelliJ plugin should, at the very least, detect the issue and fail gracefully. This may not be a frequent issue, but it's not that unusual in a complex modular plugin. In a setup described above where the plugin depends on :library1:core and :library2:core the IntelliJ plugin creates a corrupt sandbox that causes the deployed plugin to crash with a nondescript error that's really hard to diagnose. I think that the question of whether project artifacts should use globally unique names is not quite relevant to this issue: the reality is that Gradle uses the project name as the default base name for an artifact, which is not guaranteed to be unique.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |