[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] Staging repo for Juno RC2 is complete
|
Hi David,
This could be a valid reason - our product is only published with the default ANY filter as the platform we are running on doesn't make any difference for us.
What are the filter requirements for a contributing project?
Also were these checks enabled in RC1, because I don't recall facing this issue back then? Both rc1 and rc2 repos were published with the same 'any' filters.
Best regards,
Bobby
On May 31, 2012 5:23 AM, "David M Williams" <
david_williams@xxxxxxxxxx> wrote:
While EPP packages are being created and
tested on Thursday, it would be a good time to sanity check the staging
repo:
http://download.eclipse.org/releases/staging/
(and yes, egit's latest is in there).
Virgo it the only project disabled.
It was failing for some mysterious reasons
and then, of all things, Bobby Kapukaranov took a vacation! :)
So, some last minute work to figure
out there (Bobby, I didn't think of it before when we exchanged mail, but
it might be related to platform filters ... I'm not sure if you intentionally
limit the platforms you run on, or if something you depend on does, but
I have seen, in the past, that a bundle that appears to be available is
not "available" for the for platform filters that are in effect
... and they all need to "line up" ... and, I believe that's
one of the things the aggregator catches that p2 installing by itself would
not ... after all, you are installing it, presumably, on a supported platform.
We can discuss more when you are back, but I know there are experts that
read this list that can explain it better than I can.
I have disabled the Juno aggregation
build to avoid confusion about what's current. I'll re-enable it on Friday
or so.
Thanks,
From:
Matthias Sohn <matthias.sohn@xxxxxxxxxxxxxx>
To:
Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>,
Date:
05/30/2012 07:32 PM
Subject:
Re: [cross-project-issues-dev]
JGit/EGit RC2 contribution will be late
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
I submitted our RC2 contribution for JGit and EGit, will
you start another aggregator build ?
I'll stay on standby until this build is green.
--
Matthias
2012/5/31 David M Williams <david_williams@xxxxxxxxxx>
- Use the 0.2.x version of the b3 aggregator, running on
Eclipse 3.7, installed from b3's "3.7 repo", at following URL:
http://download.eclipse.org/modeling/emft/b3/updates-3.7/
See http://wiki.eclipse.org/Juno/Contributing_to_Juno_Build
for more infor
From: Matthias
Sohn <matthias.sohn@xxxxxxxxxxxxxx>
To: Cross
project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:
05/30/2012 05:26 PM
Subject: Re:
[cross-project-issues-dev] JGit/EGit RC2 contribution will be
late
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
ok, I'll let you know
Can you point me to the p2 repo for installing the current b3 model editor
to update
the contribution files ? Hope this helps to not kill the aggregator build.
--
Matthias
2012/5/30 David M Williams <david_williams@xxxxxxxxxx>
sounds like 7 or 8 then? I'm find with that ... let us know if/when done.
If it starts to get "past 9" (Eastern) I think we should should
say "no more" ... as with last week, we seem to be having trouble
getting a green build today, on +3 day.
Thanks,
From: Matthias
Sohn <matthias.sohn@xxxxxxxxxxxxxx>
To: Cross
project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date: 05/30/2012
03:50 PM
Subject: [cross-project-issues-dev]
JGit/EGit RC2 contribution will be late
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
Looks like JGit/EGit will contribute late to RC2, after struggling with
builds and tests for weeks I have reached a green build and I hope I can
tag rc2 in another 2-3 hours. Let me know if I am getting too late
then we'll have to skip RC2 and contribute early to RC3. Though
I would prefer to reach RC2 as this is the first JGit/EGit 2.0 contribution
for Juno (this late contribution is due to the mentioned build and test
problems we are struggling with).
--
Matthias_______________________________________________
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
_______________________________________________
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
_______________________________________________
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