Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Corrupt jar for 2.8.2-1.6.8 #5

Open
rossabaker opened this issue Jan 14, 2012 · 3 comments
Open

Corrupt jar for 2.8.2-1.6.8 #5

rossabaker opened this issue Jan 14, 2012 · 3 comments

Comments

@rossabaker
Copy link

Tried to post to specs-users, but I don't think it got through.

I'm having problems with specs2_2.8.2-1.6.8. sbt update:

[info] downloading http://repo1.maven.org/maven2/org/scala-tools/testing/specs_2.8.2/1.6.8/specs_2.8.2-1.6.8.jar ...    
[warn]  [FAILED     ] org.scala-tools.testing#specs_2.8.2;1.6.8!specs_2.8.2.jar: invalid sha1: expected=4f29a5b629d7719d5a3faf6c5672d0e10b1d7c1b computed=08a4b5762e6696ec8df4e2e9769baec40b473a0e (4984ms)

I confirmed the same with wget and sha1sum. If I disable checksum verification and try to use the jar, I get this:

scala> class FooSpec extends Specification
error: error while loading Specification, invalid distance too far back
<console>:8: error: illegal inheritance;
 self-type FooSpec does not conform to org.specs.Specification's selftype org.specs.Specification
       class FooSpec extends Specification

scala> Class.forName("org.specs.Specification")
java.lang.ClassNotFoundException: org.specs.Specification

Yeah, I know, old Specs, old Scala version, but it'd sure tidy up the cross-builds if this worked. :-)

@etorreborre
Copy link
Owner

Hi Ross,

I re-published the jar and checked it by re-downloading it.

E.


Eric TORREBORRE
T +61 411 707 402
E [email protected]
P http://specs2.org

B http://etorreborre.blogspot.com


De: Ross A. Baker [email protected]
: etorreborre [email protected]
Envoy le : Samedi 14 Janvier 2012 14h27
Objet: [specs] Corrupt jar for 2.8.2-1.6.8 (#5)

Tried to post to specs-users, but I don't think it got through.

I'm having problems with specs2_2.8.2-1.6.8. sbt update:

[info] downloading http://repo1.maven.org/maven2/org/scala-tools/testing/specs_2.8.2/1.6.8/specs_2.8.2-1.6.8.jar ...
[warn] [FAILED ] org.scala-tools.testing#specs_2.8.2;1.6.8!specs_2.8.2.jar: invalid sha1: expected=4f29a5b629d7719d5a3faf6c5672d0e10b1d7c1b computed=08a4b5762e6696ec8df4e2e9769baec40b473a0e (4984ms)

I confirmed the same with wget and sha1sum. If I disable checksum verification and try to use the jar, I get this:

scala> class FooSpec extends Specification
error: error while loading Specification, invalid distance too far back
:8: error: illegal inheritance;
self-type FooSpec does not conform to org.specs.Specification's selftype org.specs.Specification
class FooSpec extends Specification

scala> Class.forName("org.specs.Specification")
java.lang.ClassNotFoundException: org.specs.Specification

Yeah, I know, old Specs, old Scala version, but it'd sure tidy up the cross-builds if this worked. :-)


Reply to this email directly or view it on GitHub:
etorreborre/specs#5

@rossabaker
Copy link
Author

It's also broken in Maven Central, which I don't think allows republishing, and Central is first by default. Workaround:

resolvers ~= { rs => ScalaToolsReleases +: rs }

Thanks for the republish. Works great as long as it comes from the corrected repo.

@etorreborre
Copy link
Owner

That's not the first time that I have corrupted jars, I don't know what to do about that.

Anyways, thanks for the resolvers trick, I'll try to remember that one :-).


Eric TORREBORRE
T +61 411 707 402
E [email protected]
P http://specs2.org

B http://etorreborre.blogspot.com


De: Ross A. Baker [email protected]
: etorreborre [email protected]
Envoy le : Samedi 14 Janvier 2012 15h39
Objet: Re: [specs] Corrupt jar for 2.8.2-1.6.8 (#5)

It's also broken in Maven Central, which I don't think allows republishing, and Central is first by default. Workaround:

resolvers ~= { rs => ScalaToolsReleases +: rs }

Thanks for the republish. Works great as long as it comes from the corrected repo.


Reply to this email directly or view it on GitHub:
etorreborre/specs#5 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants