Kotlin settings -> unresolved references in IDE

Hi Maria,

Can you check whether the solutions mentioned here (either in the post itself or in the referenced links) help? https://teamcity-support.jetbrains.com/hc/en-us/community/posts/115000201004-Kotlin-DSL-dsl-plugins-repository-not-available-HTTP-404-

Unfortunately I've checked those out without success.  I don't have mirrorOf in any of my xml.  The root of the configured URL - http://<MY_TEAM_CITY_DOMAIN> - is up and loading fine.  teamcity.kotlinConfigsDsl.pluginsCompilationXmx=2048m wasn't originally set, but tried setting it and restarting the server with no luck.

Please provide teamcity-server.log* and teamcity-versioned-settings.log* from TeamCity server machine.

What's the best way to share those files?  They are too big to reasonably paste in a comment.

You can upload them to our ftp and provide file names (https://confluence.jetbrains.com/display/TCD10/Reporting+Issues#ReportingIssues-SendingInformationtotheDevelopers). Please also check if TeamCity server the following url: http://<teamcity server>/app/dsl-plugins-repository/org/jetbrains/teamcity/configs-dsl-kotlin-plugins/SNAPSHOT/maven-metadata.xml. 

That URL *does* work.  It gives me the below.  Uploaded those files as maria-teamcity-server.log and maria-teamcity-versioned-settings.log.

<metadata modelVersion="1.1.0">
<groupId>org/jetbrains/teamcity</groupId>
<artifactId>configs-dsl-kotlin-plugins</artifactId>
<version>20170725.141155-1</version>
<versioning>
  <snapshot>
    <timestamp>20170725.141155</timestamp>
    <buildNumber>1</buildNumber>
  </snapshot>
  <lastUpdated>20170725141155</lastUpdated>
  <snapshotVersions>
    <snapshotVersion>
      <extension>pom</extension>
      <value>20170725.141155-1</value>
      <updated>20170725141155</updated>
    </snapshotVersion>
  </snapshotVersions>
</versioning>
</metadata>

Logs don't contain any error regarding dsl artifacts.. Logs show that TeamCity is listening on the port 8111. Does the url in the pom.xml contain the port as well?

No the URL in the pom.xml doesn't contain the port.  When I try hitting the domain in my browser, I don't use the port and it won't load if I do.

Could you please enable 'debug-all' logging preset at Administration > Diagnostics, run the 'mvn -U package' command, toggle logging template back to default and attach all teamcity-server.log* and teamcity-versioned-settings.log* from TeamCity server?

Sure.  I uploaded the logs in maria-teamcitylogs.zip

Thanks. I've checked the logs: they don't contain any entries from the component which serves maven artifacts. This means that maven wasn't able to reach it. Please check the url in the pom.xml again. Maybe it is due to protocol. Judging by the logs, server uses https, please ensure that the pom contains it as well. If this doesn't help please run the 'mvn -X -U package' command and provide its output.

Looking at the output from that, I see a lot of messages like this one...

[[1;33mWARNING[m] Failure to transfer org.jetbrains.teamcity:configs-dsl-kotlin-visualstudiotest:1.0-SNAPSHOT/maven-metadata.xml from https://online-teamcity.carmax.com/app/dsl-plugins-repository was cached in the local repository, resolution will not be reattempted until the update interval of teamcity-server has elapsed or updates are forced. Original error: Could not transfer metadata org.jetbrains.teamcity:configs-dsl-kotlin-visualstudiotest:1.0-SNAPSHOT/maven-metadata.xml from/to teamcity-server (https://online-teamcity.carmax.com/app/dsl-plugins-repository): Connect to online-teamcity.carmax.com:443 [online-teamcity.carmax.com/52.186.123.61] failed: Connection timed out: connect

This sounds like it's an issue related to being behind a corporate proxy - timeout is often the error that seems to cause me.  But I've got all my proxy settings set up in IDEA and it's working when I test connections from there, so not sure what's up with that.

I uploaded the full output as mvcXUpackage.txt.

I think that the error is indeed caused by the proxy server. Please check if specifying proxy settings  in <User home directory>/.m2/settings.xml helps.

Ah, ended up getting this working.  It was a combination of both the corporate proxy and the fact that we were using a self-signed cert for teamcity that maven didn't like.

Thanks for the help!