zip error: Zip file structure invalid (sensor-vernier__V1.0-20121109.222028-21.jar) ???

[Stephen Bannasch]

I'm getting this error using sensor-vernier__V1.0-20121109.222028-21.jar

zip error: Zip file structure invalid (sensor-vernier__V1.0-20121109.222028-21.jar)

Any ideas ???

************************************************************


Using java project: 'sensor-vernier'

from:
http://source.concord.org/nexus/content/repositories/cc-repo-internal-snapshot/org/concord/sensor/sensor-vernier/1.0-SNAPSHOT/sensor-vernier-1.0-20121109.222028-21.jar
version: 1.0-20121109.222028-21
located: /var/www/app/java/sensor-vernier

copy: /var/www/app/java/sensor-vernier/sensor-vernier-1.0-20121109.222028-21.jar
to: /var/www/app/server/public/jnlp/org/concord/sensor/sensor-vernier/sensor-vernier__V1.0-20121109.222028-21.jar

*** GENERATING SIGNED RESOURCE

Java Code Siging Certificate Keystore:

Alias: concord
Expires: Sat Apr 26 23:59:59 UTC 2014

processing 1 jars ...

working in dir: /var/www/app/server/public/jnlp/org/concord/sensor/sensor-vernier

removing content in meta-inf directory in:
/var/www/app/server/public/jnlp/org/concord/sensor/sensor-vernier/sensor-vernier__V1.0-20121109.222028-21.jar
zip warning: missing end signature--probably not a zip file (did you
zip warning: remember to use binary mode when you transferred it?)
zip warning: (if you are trying to read a damaged archive try -F)

zip error: Zip file structure invalid (sensor-vernier__V1.0-20121109.222028-21.jar)

adding META-INF/services directory to:
/var/www/app/server/public/jnlp/org/concord/sensor/sensor-vernier/sensor-vernier__V1.0-20121109.222028-21.jar

creating 'Trusted-Library: true' manifest in:
/var/www/app/server/public/jnlp/org/concord/sensor/sensor-vernier/sensor-vernier__V1.0-20121109.222028-21.jar

repacking:
/var/www/app/server/public/jnlp/org/concord/sensor/sensor-vernier/sensor-vernier__V1.0-20121109.222028-21.jar

signing:
/var/www/app/server/public/jnlp/org/concord/sensor/sensor-vernier/sensor-vernier__V1.0-20121109.222028-21.jar

verifying:
/var/www/app/server/public/jnlp/org/concord/sensor/sensor-vernier/sensor-vernier__V1.0-20121109.222028-21.jar
jar verified.

creating:
/var/www/app/server/public/jnlp/org/concord/sensor/sensor-vernier/sensor-vernier__V1.0-20121109.222028-21.jar.pack.gz

unpacking and verifying:
/var/www/app/server/public/jnlp/org/concord/sensor/sensor-vernier/sensor-vernier__V1.0-20121109.222028-21.jar.pack.gz
jar verified.

[Aaron Unger]

That's the same error you get if it doesn't download the jar correctly
(saves the redirect html instead, etc.). Can you download that jar
directly from your browser?

-- Aaron

[Scott Cytacki]

That doesn't seem like a valid jar file to request, your code is probably not handling the error and saving the error response page.

This shows the list of files:

http://source.concord.org/nexus/content/repositories/cc-repo-internal-snapshot/org/concord/sensor/sensor-vernier/1.0-SNAPSHOT/

I believe our nexus setup automatically cleans up old snapshots after some time.

The jnlp server doesn't do that, so if that jar was built as a jnlp you should be able to find it there.

Scott

--
You received this message because you are subscribed to the Google
Groups "org-concord-sensor" group.
To post to this group, send email to org-concord-sensor@googlegroups.com
To unsubscribe from this group, send email to
org-concord-sensor+unsub...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/org-concord-sensor?hl=en?hl=en
Google Code project for org-concord-sensor: http://code.google.com/p/org-concord-sensor/

--

Scott Cytacki

The Concord Consortium

http://concord.org

[Aaron Unger]

Ah, right. I'd forgotten that Nexus does that cleanup. Those should get switched over to the jnlp server, since those are more permanent.

-- Aaron

To post to this group, send email to org-conco...@googlegroups.com

To unsubscribe from this group, send email to

org-concord-sen...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/org-concord-sensor?hl=en?hl=en
Google Code project for org-concord-sensor: http://code.google.com/p/org-concord-sensor/

--

Scott Cytacki

The Concord Consortium

http://concord.org

--
You received this message because you are subscribed to the Google
Groups "org-concord-sensor" group.

To post to this group, send email to org-conco...@googlegroups.com

To unsubscribe from this group, send email to

org-concord-sen...@googlegroups.com

[stepheneb]

What's the url for the jnlp server?

[Scott Cytacki]

here is the url for a jar from the same time:

http://jnlp.concord.org/dev3/org/concord/sensor/sensor-vernier/sensor-vernier-1.0-20121109.222028-21.jar

Scott

On Thu, Dec 6, 2012 at 12:24 PM, stepheneb <stephen....@deanbrook.org> wrote:

What's the url for the jnlp server?

--
You received this message because you are subscribed to the Google
Groups "org-concord-sensor" group.
To post to this group, send email to org-conco...@googlegroups.com
To unsubscribe from this group, send email to
org-concord-sen...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/org-concord-sensor?hl=en?hl=en
Google Code project for org-concord-sensor: http://code.google.com/p/org-concord-sensor/

[Scott Cytacki]

I think it was my idea to use the nexus server directly, so now we know that is a bad idea. :)

It is probably safest to download the jar and put it into the repo that needs it. At least until we start using real versions and/or get them into maven-central.

[Stephen Bannasch]

At 12:32 PM -0500 12/6/12, Scott Cytacki wrote:
>I think it was my idea to use the nexus server directly, so now we know that is a bad idea. :)
>

>It is probably safest to download the jar and put it into the repo that needs it. At least until westart using real versions and/or get them into maven-central.

Here's the current fix I've pushed (and deployed all the way through production):

https://github.com/concord-consortium/lab/commit/d4f50aa5e471851

The actual version numbers on the jnlp server don't match the ones on source.concord.org. Mostly this was just differences in the datestring -- but there was no version 21 for the sensor jar:

sensor-1.0-<datestring>-21.jar is not present here:

http://jnlp.concord.org/dev3/org/concord/sensor/sensor/

So I specified sensor-1.0-20121114.175203-22.jar instead.

[Aaron Unger]

That works. Not all of the versions in Nexus end up on the jnlp server
-- only ones that are the most recent version when the jnlps get rebuilt.

-- Aaron