On Thu, Jun 9, 2011 at 9:35 AM, David M Williams
<david_williams@xxxxxxxxxx> wrote:
> When should I update the WindowBuilder aggregator file?
Only when the "release" version is completely
ready to use. That may be shortly after you do the move, but if you "leave
it invisible" until release (like you are supposed to do) then p2
(and the aggregator) can't really use it yet. So, pretty much have to use
"copy" (not move), leave the old one in place, and reference
old one in b3aggrcon file, until the final resting spot is usable (visible
to p2). Then you can update b3aggrcon file anytime after that. And, then,
you can remove old RC4 directory. Perhaps even all on "release
day". There are some slightly different ways to do all this, if projects
use composite repositories, but don't think that applies to you. Hopefully
those that use composites, know what I'm talking about :) and know what
to do.
Thanks,
From:
Mark Russell <mrrussell@xxxxxxxxxx>
To:
Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>
Date:
06/08/2011 05:34 PM
Subject:
[cross-project-issues-dev]
aggrigator files
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
If I plan on moving my code to a new new location for
release will I have to update the aggrigator file for WindowBuilder?
I currently have the code here:
/home/data/httpd/download.eclipse.org/windowbuilder/WB/RC4-201106081257/3.7
the final resting place is:
/home/data/httpd/download.eclipse.org/windowbuilder/WB/release/R201106211200/3.7
When should I update the WindowBuilder aggrogator file?
--
Mark R Russell
(724) 473-3140
Release Engineer
Google Pittsburgh
_______________________________________________
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
