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.
Le 12/03/2012 11:36, Stéphane Bouchet a écrit :
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,
Le 11/03/2012 20:01, Vincent Zurczak a écrit :
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
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
