Skip to main content
diff options
authorEd Willink2014-12-05 11:40:53 +0000
committerEd Willink2014-12-05 11:40:53 +0000
commit2b02849b5e6d74f3e80b6d22b8118eb3ab270aff (patch)
tree73310259e8ea2889829853f6331af2781f1e30a9 /releng/org.eclipse.qvtd.releng.buckminster/README.txt
parent75d6b8dfbc5746fdf51e67b5e593ff3f2985798f (diff)
[ocl25] xtext, CS URI renames
Diffstat (limited to 'releng/org.eclipse.qvtd.releng.buckminster/README.txt')
1 files changed, 6 insertions, 6 deletions
diff --git a/releng/org.eclipse.qvtd.releng.buckminster/README.txt b/releng/org.eclipse.qvtd.releng.buckminster/README.txt
index 84f04f925..bd440d243 100644
--- a/releng/org.eclipse.qvtd.releng.buckminster/README.txt
+++ b/releng/org.eclipse.qvtd.releng.buckminster/README.txt
@@ -1,23 +1,23 @@
The Buckminster build automatically promotes downloads and updates, so no cron job help is necessary.
The updates can be checked by looking for the new entry on
-or installing new software from e.g.
+or installing new software from e.g.
However operations on composite repositories are not automated, partly because they are sufficiently important to deserve manual attention.
A new milestone build can be added to the composite repository by:
logon to
-cd downloads/mmt/qvtd/updates/milestones/0.12.0
-ant -f /shared/modeling/tools/promotion/manage-composite.xml add -Dchild.repository=S201408191819"QVTd 0.12.0 milestones"
+cd downloads/mmt/qvtd/updates/milestones/1.0.0
+ant -f /shared/modeling/tools/promotion/manage-composite.xml add -Dchild.repository=S201408191819"QVTd 1.0.0 milestones"
-(This can be checked by installing new software from e.g.
+(This can be checked by installing new software from e.g.
The Mars aggregator is configured by GIT\\qvtd.b3aggrcon to use an explicit milestone entry
So edit qvtd.b3aggrcon to update
push to upstream master and start a new build at
Once a relese has been promoted update qvtd.b3aggrcon to the final release

Back to the top