Hi, David
We have found one issue in BIRT RC3 build that
needs to be fixed for TPTP. Current
plan is to upload BIRT RC3 build to the Callisto update
site later tonight and make another build RC3a with only one fix for TPTP before
the end of Monday PST time.
Thanks
Wenfeng
-----Original Message-----
From:
cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent: Friday, May 19, 2006 3:20 PM
To: Cross project issues
Subject: [cross-project-issues-dev]
Status of Callisto RC3
I have not ran my copy and optimization commands, on
the recent GMF updates yet, but otherwise, the staging site is "up and
running".
I
have yet to hear from TPTP and BIRT .. or did I miss something?
Accoring
to the plan summary,
http://wiki.eclipse.org/index.php/Callisto_Plan_Summary
TPTP
is not planning on updating anything this cycle? But .. I know for a fact some
"commmon" features/plugins have been created for them, so, not sure
that what is there
for
their RC2 will still work as expected? (But, admit, have not tried).
If
TPTP or BIRT submits anything, I'll "run my tools" again on Saturday,
but, normally, Saturday or Sunday is a good time to starting the mirroring
process, so if anyone intends to still contribute (or not),
please
keep us all up to date with plans and status.
Thanks,
all.
|
David M
Williams/Raleigh/IBM@IBMUS
Sent
by: cross-project-issues-dev-bounces@xxxxxxxxxxx
05/19/2006 05:42 PM
|
Please
respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
|
|
|
To
|
Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
|
Re: [cross-project-issues-dev] GMF 1.0 RC3
ready for Callisto RC3
|
|
For batik you should add a property set with the featureId
and version number. If its really coming from a different download site
(different from GMF) then I guess a whole seperate feature-batik.xml file would
be approperiate ... which, I'd assme, you would still be responsible for.
<ant
antfile="updateMirrorProject.xml">
<property name="featureId"
value="org.eclipse.gmf.callisto" />
<property name="version"
value="1.0.0.v20060519-1300" />
</ant>
Once that's there, I can update the master site.xml file so it shows up under
"Enabling Features".
Thanks,
|
Max Feldman
<max.feldman@xxxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
05/19/2006 04:54 PM
|
Please
respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
|
|
|
To
|
cross-project-issues-dev@xxxxxxxxxxx
|
|
cc
|
|
|
Subject
|
[cross-project-issues-dev] GMF 1.0 RC3 ready
for Callisto RC3
|
|
Callisto tools feature-gmf.xml updated
Download link: http://download.eclipse.org/technology/gmf/downloads/drops/S-1.0RC3-200605191300/index.php
Update site link: http://download.eclipse.org/technology/gmf/update-site/milestone/site.xml
Note that GMF update site doesn't have Batik feature anymore (see Bug 142058).
The org.apache.batik feature for inclusion to Callisto's "Enabling
Features" category can be downloaded from the Batik update site http://download.eclipse.org/technology/gmf/update-site/batik/site.xml,
although, not sure how to add it to the Callisto.. (David?)
Regards,
Max
_______________________________________________
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
