Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to reparse SNAPHOTS

See original GitHub issue

We have an sbt project using 0.13.9 and works fine. However upgrading to any version larger than that gives warnings and intermittently fails to compile as sbt didn’t download the jar file for snapshot dependencies.

Here is the output I get

[info] Compiling 41 Scala sources and 2 Java sources to /projects/project_ui/modules/common_views/target/scala-2.11/classes...
[info] Resolving company#akka-http-auth_2.11;3.0.0-SNAPSHOT ...
[warn] Unable to reparse company#akka-http-auth_2.11;3.0.0-SNAPSHOT from Artifactory Snapshots, using Thu Aug 03 06:04:55 BST 2017
[warn] Unable to reparse company#akka-http-auth_2.11;3.0.0-SNAPSHOT from Monitoring snapshots, using Wed Aug 02 16:25:09 BST 2017
[warn] Sorting results from company#akka-http-auth_2.11;3.0.0-SNAPSHOT, using Wed Aug 02 16:25:09 BST 2017 and null
[warn] Sorting results from company#akka-http-auth_2.11;3.0.0-SNAPSHOT, using Thu Aug 03 06:04:55 BST 2017 and null
[info] Resolving company#dalton-client_2.11;3.0.0-SNAPSHOT ...
[warn] Unable to reparse company#dalton-client_2.11;3.0.0-SNAPSHOT from Artifactory Snapshots, using Thu Aug 03 06:05:03 BST 2017
[warn] Unable to reparse company#dalton-client_2.11;3.0.0-SNAPSHOT from Monitoring snapshots, using Wed Aug 02 16:24:56 BST 2017
[warn] Sorting results from company#dalton-client_2.11;3.0.0-SNAPSHOT, using Wed Aug 02 16:24:56 BST 2017 and null
[warn] Sorting results from company#dalton-client_2.11;3.0.0-SNAPSHOT, using Thu Aug 03 06:05:03 BST 2017 and null
[info] Resolving com.company.clients#dalton-client;2.0.1-SNAPSHOT ...
[warn] Unable to reparse com.company.clients#dalton-client;2.0.1-SNAPSHOT from Artifactory Snapshots, using Thu Aug 03 06:05:09 BST 2017
[info] Resolving com.company.clients#euresource;2.0.1-SNAPSHOT ...
[warn] Unable to reparse com.company.clients#euresource;2.0.1-SNAPSHOT from Artifactory Snapshots, using Thu Aug 03 06:05:28 BST 2017
[info] Resolving com.company.clients#eureka-client;2.0.1-SNAPSHOT ...
[warn] Unable to reparse com.company.clients#eureka-client;2.0.1-SNAPSHOT from Artifactory Snapshots, using Thu Aug 03 06:05:38 BST 2017
[info] Resolving company#plinth-client_2.11;3.0.0-SNAPSHOT ...
[warn] Unable to reparse company#plinth-client_2.11;3.0.0-SNAPSHOT from Artifactory Snapshots, using Thu Aug 03 06:06:04 BST 2017
[warn] Unable to reparse company#plinth-client_2.11;3.0.0-SNAPSHOT from Monitoring snapshots, using Wed Aug 02 16:25:04 BST 2017
[warn] Sorting results from company#plinth-client_2.11;3.0.0-SNAPSHOT, using Wed Aug 02 16:25:04 BST 2017 and null
[warn] Sorting results from company#plinth-client_2.11;3.0.0-SNAPSHOT, using Thu Aug 03 06:06:04 BST 2017 and null
[info] Resolving com.company.clients#plinth-client;2.0.1-SNAPSHOT ...
[warn] Unable to reparse com.company.clients#plinth-client;2.0.1-SNAPSHOT from Artifactory Snapshots, using Thu Aug 03 06:23:57 BST 2017
[info] Resolving com.company.clients#reference-client;2.0.1-SNAPSHOT ...
[warn] Unable to reparse com.company.clients#reference-client;2.0.1-SNAPSHOT from Artifactory Snapshots, using Thu Aug 03 06:24:08 BST 2017
[info] Resolving company#issue-management-models_2.11;1.0.0-SNAPSHOT ...
[warn] Unable to reparse company#issue-management-models_2.11;1.0.0-SNAPSHOT from Artifactory Snapshots, using Thu Aug 03 06:24:30 BST 2017
[warn] Unable to reparse company#issue-management-models_2.11;1.0.0-SNAPSHOT from Monitoring snapshots, using Tue Aug 01 16:54:51 BST 2017
[warn] Sorting results from company#issue-management-models_2.11;1.0.0-SNAPSHOT, using Tue Aug 01 16:54:51 BST 2017 and null
[warn] Sorting results from company#issue-management-models_2.11;1.0.0-SNAPSHOT, using Thu Aug 03 06:24:30 BST 2017 and null
[info] Resolving jline#jline;2.12.1 ...
[info] downloading https://artifactory.server.com/artifactory/snapshot/company/akka-http-auth_2.11/3.0.0-SNAPSHOT/akka-http-auth_2.11-3.0.0-SNAPSHOT.jar ...
[info]  [SUCCESSFUL ] company#akka-http-auth_2.11;3.0.0-SNAPSHOT!akka-http-auth_2.11.jar (2013ms)
[info] downloading https://artifactory.server.com/artifactory/snapshot/company/plinth-client_2.11/3.0.0-SNAPSHOT/plinth-client_2.11-3.0.0-SNAPSHOT.jar ...
[info]  [SUCCESSFUL ] company#plinth-client_2.11;3.0.0-SNAPSHOT!plinth-client_2.11.jar (1945ms)
[info] downloading https://artifactory.server.com/artifactory/snapshot/company/dalton-client_2.11/3.0.0-SNAPSHOT/dalton-client_2.11-3.0.0-SNAPSHOT.jar ...
[info]  [SUCCESSFUL ] company#dalton-client_2.11;3.0.0-SNAPSHOT!dalton-client_2.11.jar (669ms)
[info] downloading https://artifactory.server.com/artifactory/snapshot/company/issue-management-models_2.11/1.0.0-SNAPSHOT/issue-management-models_2.11-1.0.0-SNAPSHOT.jar ...
[info]  [SUCCESSFUL ] company#issue-management-models_2.11;1.0.0-SNAPSHOT!issue-management-models_2.11.jar (2599ms)
[info] Done updating.
[info] Resolving com.typesafe.play#play_2.11;2.5.16 ...
[info] Sass compiling on 3 source(s)
[info] Resolving company#akka-http-auth_2.11;3.0.0-SNAPSHOT ...
[info] Sass compilation done in 427 ms. 6 resulting css/source map file(s)
[info] Compiling 12 Scala sources and 3 Java sources to /projects/project_ui/modules/actions/target/scala-2.11/classes...
[warn] Unable to reparse company#akka-http-auth_2.11;3.0.0-SNAPSHOT from Artifactory Snapshots, using Thu Aug 03 06:04:55 BST 2017
[warn] Unable to reparse company#akka-http-auth_2.11;3.0.0-SNAPSHOT from Monitoring snapshots, using Wed Aug 02 16:25:09 BST 2017
[warn] Sorting results from company#akka-http-auth_2.11;3.0.0-SNAPSHOT, using Wed Aug 02 16:25:09 BST 2017 and null

Issue Analytics

State:
Created 6 years ago
Reactions:2
Comments:7 (2 by maintainers)

Top GitHub Comments

8reactions

Ukocommented, Jan 30, 2018

So what? Half a year passed and no one cares about this issue?

2reactions

rojanucommented, Jun 27, 2018

SNAPSHOT is part of many many projects and how they handle code that’s not released and to push it to a side and say don’t use it beyond your local box is not really ideal.

Other build tools handle it well and sbt is expected to behave the same.

I am having difficulty to understand the logic behind closing the issue and not fixing it

Top Results From Across the Web

Idea, sbt, unable to reparse warning - Stack Overflow

There are 2 ways to fix this. Update your snapshot version number(recommended); Remove the SNAPSHOT from your artifactory and remove the .ivy2/cache/{dependency ...

IDEA doesn't resolve properly locally published snapshots

It seems IDEA fails to correctly maintain snapshots when you have the same snapshot version both remotely and locally. IDEA doesn't care about...

[SOLVED] - ZSF Snapshot: unable to parse value of 'runningcpu'

Hi, I tried everything but i can't get SnapShots of my VM 100 to work. It is on ZFS. The error is "unable...

Backups are completing with exceptions with error - Avamar

Backups are completing with exceptions by the error code 10020 and with the below error in the log file 2017-12-07 17:03:27 avtar Error...

Multi-Component Repository Publishing - Aptly

Snapshots, mirrors and local repositories are lists of packages (more precisely, ... snapshots and keep getting an "Unable to parse command" error.