Re: [cross-project-issues-dev] Helios repository updates

[David M Williams <david_williams@xxxxxxxxxx>]

I see you weren't really asking about
schedules. :) 

As you test the /releases/helios there's
a few tips that provide for a better test and could provide good input
to any bugs that you open. 

First, I recommend disabling all other
repos (when you are testing this repo) just to make sure you are getting
a view of only /releases/helios

Then, if you don't see what you expect,
be sure to try "uncategorized" view and/or "show all versions"
views. That might give some insight. 
For example, if an old version shows
up in categorized view, but the new version shows up if uncategorized,
then that implies something is wrong with the category ... and a cross-project
bug would be appropriate, not a p2 bug ... not a rap bug. 

In our current /releases/helios we actually
have M7 + M6 + M5.  That is one big difference between "staging"
and "releases" (staging always has only one version of everything).
We purposely keep the "old" milestones around ... during development
cycle ... specifically to test if "multiple, persistent versions"
is working as we need it to. When we release in June, we will have only
one version there .... but we want to test early, to make sure it is working
so when we do have and need multiple versions (after service releases,
SRn) that the multiple version mechanisms  work correctly. 

So, thanks for testing and reporting
good bugs. We can all collaborate in the bugzilla entry to get to the bottom
of it. 

Thanks,

From:	Ralf Sternberg <rsternberg@xxxxxxxxxxxxxxxxx>
To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:	05/08/2010 09:52 AM
Subject:	Re: [cross-project-issues-dev] Helios repository updates
Sent by:	cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Markus Knauer wrote:
> It should be there since yesterday... maybe p2 doesn't know yet about
the
> update and uses some cached copies of the content/artifacts.
> 
> releases/helios/201005070900/aggregate/features/org.eclipse.rap.tooling_1.3.0.20100504-1207.jar

Yes, that's the correct version. But I still get this old version even
with a fresh Eclipse installation and workspace:

  Rich Ajax Platform (RAP) Tooling        
        1.3.0.20100201-1240

Are there any p2 caches on my system outside the install area?
How can I verify that the correct version is in the repo? I tried a

  wget http://download.eclipse.org/releases/helios/content.xml
/ content.jar

but get a 404.

What good are those p2 caches if they shadow available software forever?

Ralf

> On 8 May 2010 10:59, Ralf Sternberg <rsternberg@xxxxxxxxxxxxxxxxx>
wrote:
> 
>> Hi,
>>
>> I wanted to ask on what schedule the Helios repository is updated?
>>
>> While the staging repository [1] now includes the M7 features
of RAP,
>> the official Helios repo [2] contains only RAP M5 tooling and
the M6
>> runtime. Unfortunately, the M5 tooling had a problem, that everyone
who
>> installs RAP tooling from this update site still runs into.
>>
>> Is it possible to get M7 features into the Helios repository?
>>
>> Thanks, Ralf
>>
>> [1] http://download.eclipse.org/releases/staging
>> [2] http://download.eclipse.org/releases/helios
>>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


-- 
Ralf Sternberg

EclipseSource
www.eclipsesource.com

Tel: +49 721 664 7330
Fax: +49 721 664 73329

Innoopract Informationssysteme GmbH
Stephanienstrasse 20, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883

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