[dash-dev] [cross-project-issues-dev] Corrupted Maven repository at Eclipse.org

Discussion:

David Carver

2012-03-13 20:28:55 UTC

Adding the dash-dev mailing list to this as well. Alex had discovered
some errors with the maven.eclipse.org repository and was looking into
it. He follows that list.

Dave

Hi,
In fact, we already use a private Maven repository.
The problem is that we can not refresh it because the original
artifacts are corrupted on the central Eclipse Maven repository
(http://maven.eclipse.org/nexus/content/groups/public) and it results
in an error with Tycho.
It seems the corrupted archives have been repaired since then.
Thanks anyway,
Vincent.

Hi,
You should use a private local maven repository to avoid such
problems, and if the repo is corrupted, you can wipe out it yourself.
Go to the configuration page of your job, and tick 'use private local
maven repository' under "advanced" tab of the maven category
cheers,

Hi,
In order to have a non-greedy build, I updated the BPEL Designer to use
Tycho 0.13.0.
The build works fine locally (I already have a valid Maven repository).
However, when building on Eclipse, it fails.
The reason is that the JAR file for tycho-p2-publisher-plugin is empty
on this repository (0 byte).

[ERROR] Failed to parse plugin descriptor for
org.eclipse.tycho:tycho-p2-publisher-plugin:0.13.0 ...: error in
opening zip file -> [Help 1]

I found a workaround for this JAR by forcing the use of the central
Maven repository.
But the same thing happens with eclipse-signing-maven-plugin
<http://maven.eclipse.org/nexus/content/groups/public/org/eclipse/dash/maven/eclipse-signing-maven-plugin/1.0.5/eclipse-signing-maven-plugin-1.0.5.jar>.
And this one is not on the central Maven repository.
I tried on Friday evening and I checked tonight too.
How often are updated the Eclipse repositories?
And could we force a reset on these invalid JAR files?
Thanks,
Vincent.
--
Vincent Zurczak
RCP Developer & ESB Consultant
Petals Link: http://www.petalslink.com
My Blog: http://vzurczak.wordpress.com
+33 (0) 4 76 96 15 16
_______________________________________________
cross-project-issues-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Vincent Zurczak
RCP Developer & ESB Consultant
Petals Link: http://www.petalslink.com
My Blog: http://vzurczak.wordpress.com
+33 (0) 4 76 96 15 16
_______________________________________________
cross-project-issues-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Jesse McConnell

2012-03-13 20:31:00 UTC

Permalink

we have seen this off and on for a while now :/

jesse

--
jesse mcconnell

Adding the dash-dev mailing list to this as well. Alex had discovered some
errors with the maven.eclipse.org repository and was looking into it. He
follows that list.
Dave
Hi,
In fact, we already use a private Maven repository.
The problem is that we can not refresh it because the original artifacts are
corrupted on the central Eclipse Maven repository
(http://maven.eclipse.org/nexus/content/groups/public) and it results in an
error with Tycho.
It seems the corrupted archives have been repaired since then.
Thanks anyway,
Vincent.
Hi,
You should use a private local maven repository to avoid such problems, and
if the repo is corrupted, you can wipe out it yourself.
Go to the configuration page of your job, and tick 'use private local maven
repository' under "advanced" tab of the maven category
cheers,
Hi,
In order to have a non-greedy build, I updated the BPEL Designer to use
Tycho 0.13.0.
The build works fine locally (I already have a valid Maven repository).
However, when building on Eclipse, it fails.
The reason is that the JAR file for tycho-p2-publisher-plugin is empty
on this repository (0 byte).
[ERROR] Failed to parse plugin descriptor for
org.eclipse.tycho:tycho-p2-publisher-plugin:0.13.0 ...: error in opening zip
file -> [Help 1]
I found a workaround for this JAR by forcing the use of the central
Maven repository.
But the same thing happens with eclipse-signing-maven-plugin
<http://maven.eclipse.org/nexus/content/groups/public/org/eclipse/dash/maven/eclipse-signing-maven-plugin/1.0.5/eclipse-signing-maven-plugin-1.0.5.jar>.
And this one is not on the central Maven repository.
I tried on Friday evening and I checked tonight too.
How often are updated the Eclipse repositories?
And could we force a reset on these invalid JAR files?
Thanks,
Vincent.
--
Vincent Zurczak
RCP Developer & ESB Consultant
Petals Link: http://www.petalslink.com
My Blog: http://vzurczak.wordpress.com
+33 (0) 4 76 96 15 16
_______________________________________________
cross-project-issues-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Vincent Zurczak
RCP Developer & ESB Consultant
Petals Link: http://www.petalslink.com
My Blog: http://vzurczak.wordpress.com
+33 (0) 4 76 96 15 16
_______________________________________________
cross-project-issues-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
dash-dev mailing list
https://dev.eclipse.org/mailman/listinfo/dash-dev

Alex Blewitt

2012-03-13 21:21:55 UTC

Permalink

I mentioned the server had run out of disk space because there was a lot of unnecessary cruft on the machine. It also doesn't help that the maven config was recently changed which introduced unnecessary issues.

I'm hoping that we can revert the configuration to a more stable state and address the settings issues as well to eliminate these kind of problems in the future.

Alex

Sent from my iPhone 4S

Post by Jesse McConnell
we have seen this off and on for a while now :/
jesse
--
jesse mcconnell

_______________________________________________
dash-dev mailing list
https://dev.eclipse.org/mailman/listinfo/dash-dev

David Carver

2012-03-14 14:46:57 UTC

Permalink

Alex,

We may want to consider an upgrade to Nexus 1.9 or 2.0 as well. I
think we are using 1.8.x which I know had some bugs.

Dave

Post by Alex Blewitt
I mentioned the server had run out of disk space because there was a lot of unnecessary cruft on the machine. It also doesn't help that the maven config was recently changed which introduced unnecessary issues.
I'm hoping that we can revert the configuration to a more stable state and address the settings issues as well to eliminate these kind of problems in the future.
Alex
Sent from my iPhone 4S

Post by Jesse McConnell
we have seen this off and on for a while now :/
jesse
--
jesse mcconnell

Adding the dash-dev mailing list to this as well. Alex had discovered some
errors with the maven.eclipse.org repository and was looking into it. He
follows that list.
Dave
Hi,
In fact, we already use a private Maven repository.
The problem is that we can not refresh it because the original artifacts are
corrupted on the central Eclipse Maven repository
(http://maven.eclipse.org/nexus/content/groups/public) and it results in an
error with Tycho.
It seems the corrupted archives have been repaired since then.
Thanks anyway,
Vincent.
Hi,
You should use a private local maven repository to avoid such problems, and
if the repo is corrupted, you can wipe out it yourself.
Go to the configuration page of your job, and tick 'use private local maven
repository' under "advanced" tab of the maven category
cheers,
Hi,
In order to have a non-greedy build, I updated the BPEL Designer to use
Tycho 0.13.0.
The build works fine locally (I already have a valid Maven repository).
However, when building on Eclipse, it fails.
The reason is that the JAR file for tycho-p2-publisher-plugin is empty
on this repository (0 byte).
[ERROR] Failed to parse plugin descriptor for
org.eclipse.tycho:tycho-p2-publisher-plugin:0.13.0 ...: error in opening zip
file -> [Help 1]
I found a workaround for this JAR by forcing the use of the central
Maven repository.
But the same thing happens with eclipse-signing-maven-plugin
<http://maven.eclipse.org/nexus/content/groups/public/org/eclipse/dash/maven/eclipse-signing-maven-plugin/1.0.5/eclipse-signing-maven-plugin-1.0.5.jar>.
And this one is not on the central Maven repository.
I tried on Friday evening and I checked tonight too.
How often are updated the Eclipse repositories?
And could we force a reset on these invalid JAR files?
Thanks,
Vincent.
--
Vincent Zurczak
RCP Developer& ESB Consultant
Petals Link: http://www.petalslink.com
My Blog: http://vzurczak.wordpress.com
+33 (0) 4 76 96 15 16
_______________________________________________
cross-project-issues-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Vincent Zurczak
RCP Developer& ESB Consultant
Petals Link: http://www.petalslink.com
My Blog: http://vzurczak.wordpress.com
+33 (0) 4 76 96 15 16
_______________________________________________
cross-project-issues-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
dash-dev mailing list
https://dev.eclipse.org/mailman/listinfo/dash-dev

_______________________________________________
dash-dev mailing list
https://dev.eclipse.org/mailman/listinfo/dash-dev

Alex Blewitt

2012-03-14 15:33:57 UTC

Permalink

I'd say we should upgrade to 2 but let's hold off for a while - 2.0.2 was released recently and it would be good to see how it works in the field before upgrading.

Alex

Sent from my iPhone 4S

Alex,
We may want to consider an upgrade to Nexus 1.9 or 2.0 as well. I think we are using 1.8.x which I know had some bugs.
Dave

Post by Jesse McConnell
we have seen this off and on for a while now :/
jesse
--
jesse mcconnell

Adding the dash-dev mailing list to this as well. Alex had discovered some
errors with the maven.eclipse.org repository and was looking into it. He
follows that list.
Dave
Hi,
In fact, we already use a private Maven repository.
The problem is that we can not refresh it because the original artifacts are
corrupted on the central Eclipse Maven repository
(http://maven.eclipse.org/nexus/content/groups/public) and it results in an
error with Tycho.
It seems the corrupted archives have been repaired since then.
Thanks anyway,
Vincent.
Hi,
You should use a private local maven repository to avoid such problems, and
if the repo is corrupted, you can wipe out it yourself.
Go to the configuration page of your job, and tick 'use private local maven
repository' under "advanced" tab of the maven category
cheers,
Hi,
In order to have a non-greedy build, I updated the BPEL Designer to use
Tycho 0.13.0.
The build works fine locally (I already have a valid Maven repository).
However, when building on Eclipse, it fails.
The reason is that the JAR file for tycho-p2-publisher-plugin is empty
on this repository (0 byte).
[ERROR] Failed to parse plugin descriptor for
org.eclipse.tycho:tycho-p2-publisher-plugin:0.13.0 ...: error in opening zip
file -> [Help 1]
I found a workaround for this JAR by forcing the use of the central
Maven repository.
But the same thing happens with eclipse-signing-maven-plugin
<http://maven.eclipse.org/nexus/content/groups/public/org/eclipse/dash/maven/eclipse-signing-maven-plugin/1.0.5/eclipse-signing-maven-plugin-1.0.5.jar>.
And this one is not on the central Maven repository.
I tried on Friday evening and I checked tonight too.
How often are updated the Eclipse repositories?
And could we force a reset on these invalid JAR files?
Thanks,
Vincent.
--
Vincent Zurczak
RCP Developer& ESB Consultant
Petals Link: http://www.petalslink.com
My Blog: http://vzurczak.wordpress.com
+33 (0) 4 76 96 15 16
_______________________________________________
cross-project-issues-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Vincent Zurczak
RCP Developer& ESB Consultant
Petals Link: http://www.petalslink.com
My Blog: http://vzurczak.wordpress.com
+33 (0) 4 76 96 15 16
_______________________________________________
cross-project-issues-dev mailing list
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
dash-dev mailing list
https://dev.eclipse.org/mailman/listinfo/dash-dev

_______________________________________________
dash-dev mailing list
https://dev.eclipse.org/mailman/listinfo/dash-dev

Aaron Digulla

2012-03-14 16:32:12 UTC

Permalink

Post by David Carver
Alex,
We may want to consider an upgrade to Nexus 1.9 or 2.0 as well. I
think we are using 1.8.x which I know had some bugs.

We didn't upgrade to 1.9 because of other bugs ;-)

Regards,

--
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
http://www.pdark.de/ http://blog.pdark.de/