[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] Re: EPP and PDT @EclipseCon

Yes, invalid credentials will certainly prevent a cvs check in.

In this case, the credentials for updating the file were correct, but those used for tagging & releasing were still set to Alon. I've fixed that.

The error message, fwiw, is this bit of cryptic nonsense:

cvs rdiff: failed to read diff file header /tmp/cvsWv0oeE for java-cup-10k.jar,v: end of file

I've kicked a tag&release using the updated credentials. You should get an email when it's done.

Michael Spector wrote:
Hi Nick,

Can you update this script for CVS username & e-mail address (alon ->
michael, apeled -> mspector), since I don't have permissions?
IIUC, if this script runs automatically, can wrong CVS user be the
reason for the non-updated versions?


On Fri, Mar 20, 2009 at 4:52 PM, Nick Boldt <nickboldt@xxxxxxxxx> wrote:
=== Tags, mapfiles, and qualifiers ===

.HEAD happens when you put HEAD in your map file. If you build from a tag,
you get the tag id (eg., v20090320-0800).

You can also override all those tags with forceContextQualifier, but that
means ALL plugins and features will be built with that override value,
rather than their mixed (real) values from the map file.


And, if you want unchanging features to reflect the fact that their
*contained features* and *contained plugins* change by appending a hashed
suffix, you can add generateFeatureVersionSuffix=true to all
build.properties files where you want this to happen (eg., php.sdk and php

To automatically replace HEAD in the map with a generated tag value, wait
for the next crontab run (Thursdays at 9:30am Eastern time / GMT-4), or run
this script yourself on modeling.eclipse.org:

-debug 2

=== Galileo contribution file pdt.build ===

As to the automated creation of pdt.build (the contribution file for
Galileo), simply checking the box on the promote page will do that for
you... IF the user that's running the build is in the callisto-dev group on
dev.eclipse.org. Assuming the build runs with Michael's id, that step should
work automatically.

You can also perform that step on a previously-promoted build via the
commandline using the `-coordsiteonly galileo` flag, passed to
/home/www-data/build/modeling/scripts/promoteToEclipse.sh along with the
usual flags for -sub, -buildID, -branch, etc.


Michael Spector wrote:
No, this file should be committed automatically upon milestone build, as I

May be the checkbox must be checked as well. The problem is that PDT
2.1.0M6 has wrong versions in its package as well: 2.1.0.HEAD.

Best regards,


*From:* Roy Ganor *Sent:* Friday, March 20, 2009 11:51 AM *To:* Michael Spector *Cc:* Markus Knauer; Nick Boldt *Subject:* RE: EPP and PDT @EclipseCon

Hi Michael,

Should **we** update this file manually after we build each milestone of
Eclipse PDT? Or this can be done automatically as part of the new build

I noticed that in the promote process there is a checkbox mentioning that
we can notify the Galileo build system about this release…

(adding Nick to this conversation, maybe he can shed the light)

- Roy


*From:* Michael Spector
*Sent:* Friday, March 20, 2009 11:40 AM
*To:* Roy Ganor; 'Markus Knauer'
*Subject:* RE: EPP and PDT @EclipseCon


The version of PDT feature that appears in the pdt.build file is wrong:

<?xml version="1.0" encoding="ASCII"?>

<build:Contribution xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI";
xmlns:build="http://www.eclipse.org/amalgam/2008/build"; label="PDT">

 <contacts name="PDT Build Team" email="michael@xxxxxxxx"/>

 <contacts name="PDT Build Team" email="roy@xxxxxxxx"/>

 <features id="org.eclipse.php.sdk" version="2.1.0.HEAD"


label="PDT milestones"/>


I guess this is the reason why PDT is not gathered by the Galileo build magic?

Best regards,


*From:* Roy Ganor *Sent:* Friday, March 20, 2009 11:25 AM *To:* Michael Spector; Markus Knauer *Subject:* RE: EPP and PDT @EclipseCon

We released PDT 2.1.0M6 today, so there should be no problems providing it for Galileo M6 build.

Michael, can you please update about
http://build.eclipse.org/galileo/staging/ ?


- Roy


*From:* mknauer@xxxxxxxxxxxxxxxxx [mailto:mknauer@xxxxxxxxxxxxxxxxx] *On
Behalf Of *Markus Knauer
*Sent:* Friday, March 20, 2009 11:22 AM
*To:* Roy Ganor
*Subject:* Re: EPP and PDT @EclipseCon

Hi Roy,

just one question, but an important one: What is your Galileo Status? Will
PHP be included in the Galileo M6 build (i.e. the Galileo staging
repository: http://build.eclipse.org/galileo/staging/)? Haven't seen
anything new here but that might be due to the fact that the Galileo build
seems to be broken (Rich Gronback is working with other people on fixing

Depending on this I will be able to setup an initial version this weekend
and will *try* to make it available right in time with EclipseCon.

Regards, Markus

2009/3/20 Roy Ganor <roy@xxxxxxxx <mailto:roy@xxxxxxxx>>

Hi Markus,

Just wanted to know (verify) that you are all set for creating a PHP
package based on PDT.

Michael Spector (micahel@xxxxxxxx <mailto:micahel@xxxxxxxx>) will be
attending the conference. I will be happy if you can update him about the
status of the EPP project and what we need to do more (if any) to maintain
the PHP package.

Thank you very much for your time,


Markus Knauer
###   phone: +49 721 664 733 0  (GMT +1)
###     fax: +49 721 664 733 29
###     web: www.eclipsesource.com <http://www.eclipsesource.com>

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

Nick Boldt :: http://wiki.eclipse.org/User:Nickb
Release Engineer :: Eclipse Modeling & Dash Athena
pdt-dev mailing list

-- Nick Boldt :: http://wiki.eclipse.org/User:Nickb Release Engineer :: Eclipse Modeling & Dash Athena