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

2012-03-14 Thread Aaron Digulla 

Zitat von 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/
___
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev

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

2012-03-14 Thread Alex Blewitt 
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

On 14 Mar 2012, at 14:46, David Carver  wrote:

> 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
> 
> On 03/13/2012 05:21 PM, Alex Blewitt wrote:
>> 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
>> 
>> On 13 Mar 2012, at 20:31, Jesse McConnell  wrote:
>> 
>>> we have seen this off and on for a while now :/
>>> 
>>> jesse
>>> 
>>> --
>>> jesse mcconnell
>>> jesse.mcconn...@gmail.com
>>> 
>>> 
>>> 
>>> On Tue, Mar 13, 2012 at 15:28, David Carver  wrote:
 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
 
 
 On 03/13/2012 06:54 AM, Vincent Zurczak wrote:
 
 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
 .
 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-...@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
 
 
 
 
 ___
 cross-project-issues-dev mailing list
 cross-project-issues-...@eclipse.org
 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
 cross-project-issues-...@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
 
 
 
 ___
 dash-dev mailing list
 dash-dev@eclipse.org
 https://dev.eclipse.org/mailman/listinfo/dash-dev
 
>>> ___
>>> dash-dev mailing list
>>> dash-dev@eclipse.org
>>> https://dev.eclipse.org/mailman/listinfo/dash-dev
>> ___
>> dash-dev mailing list
>> dash-dev@eclipse.org
>> ht

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

2012-03-14 Thread 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.


Dave

On 03/13/2012 05:21 PM, Alex Blewitt wrote:

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

On 13 Mar 2012, at 20:31, Jesse McConnell  wrote:


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

jesse

--
jesse mcconnell
jesse.mcconn...@gmail.com



On Tue, Mar 13, 2012 at 15:28, David Carver  wrote:

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


On 03/13/2012 06:54 AM, Vincent Zurczak wrote:

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
.
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-...@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




___
cross-project-issues-dev mailing list
cross-project-issues-...@eclipse.org
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
cross-project-issues-...@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



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


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

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


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

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

2012-03-13 Thread 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

On 13 Mar 2012, at 20:31, Jesse McConnell  wrote:

> we have seen this off and on for a while now :/
> 
> jesse
> 
> --
> jesse mcconnell
> jesse.mcconn...@gmail.com
> 
> 
> 
> On Tue, Mar 13, 2012 at 15:28, David Carver  wrote:
>> 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
>> 
>> 
>> On 03/13/2012 06:54 AM, Vincent Zurczak wrote:
>> 
>> 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
>> .
>> 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-...@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>> 
>> 
>> 
>> 
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-...@eclipse.org
>> 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
>> cross-project-issues-...@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>> 
>> 
>> 
>> ___
>> dash-dev mailing list
>> dash-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/dash-dev
>> 
> ___
> dash-dev mailing list
> dash-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/dash-dev
___
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev

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

2012-03-13 Thread Jesse McConnell 
we have seen this off and on for a while now :/

jesse

--
jesse mcconnell
jesse.mcconn...@gmail.com



On Tue, Mar 13, 2012 at 15:28, David Carver  wrote:
> 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
>
>
> On 03/13/2012 06:54 AM, Vincent Zurczak wrote:
>
> 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
> .
> 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-...@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-...@eclipse.org
> 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
> cross-project-issues-...@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
> ___
> dash-dev mailing list
> dash-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/dash-dev
>
___
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev

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

2012-03-13 Thread David Carver 
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

On 03/13/2012 06:54 AM, Vincent Zurczak wrote:

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
. 


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-...@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




___
cross-project-issues-dev mailing list
cross-project-issues-...@eclipse.org
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
cross-project-issues-...@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


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