RE: [pde-build-dev] Timestamp in build.properties

[Kim Moir <Kim_Moir@xxxxxxxxxx>]

I think the property is

forceContextQualifier


Kim :-)

Andrew Niefer/Ottawa/IBM@IBMCA
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

01/11/2008 02:24 PM

Please respond to
"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>

To	"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>
cc
Subject	RE: [pde-build-dev] Timestamp in build.properties

That timestamp property is not used when generating qualifiers.

You probably want to set 
forceQualifier=${timestamp} 
Which will use that timestamp instead of the cvs tag.

-Andrew

"Vladimir Grishchenko" <vladgri@xxxxxxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

01/11/2008 02:09 PM

Please respond to
"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>

To	"'Eclipse PDE Build developers list.'" <pde-build-dev@xxxxxxxxxxx>
cc
Subject	RE: [pde-build-dev] Timestamp in build.properties

Kim, 
  
I cannot get the timestamp value passed via -Dtimestamp to be used to replace
plugin and feature qualifiers, it appears that the task that generates
build.xml files obtains another timestamp and uses it to replace qualifiers.
I can tell since it is 1 minute past the timestamp passed from the bootstrap
script. Not a big issue but I'm wondering if this is this proper behavior
or I'm missing something. This is in  case when fetch tag is unspecified,
i.e. equivalent to fetching from HEAD in CVS. 
  
-Vladimir

---

From: pde-build-dev-bounces@xxxxxxxxxxx
[mailto:pde-build-dev-bounces@xxxxxxxxxxx] On Behalf Of Kim Moir
Sent: Thursday, January 10, 2008 1:53 PM
To: Eclipse PDE Build developers list.
Subject: Re: [pde-build-dev] Timestamp in build.properties


Hi Vladimir 

We use the timestamp as the buildId and to replace the qualifier in the
nightly build bundles.  We set a value for the  timestamp in
our  build's bootstrap shell script. The timestamp is then passed
as an Ant property when we  invoke pde build.

See 
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.releng.eclipsebuilder/bootstrap.sh?view=markup&pathrev=HEAD

# value used in buildLabel and for text replacement in index.php template
file
builddate=`date +%Y%m%d`
buildtime=`date +%H%M`
timestamp=$builddate$buildtime 

buildCommand="$antRunner ... -Dtimestamp=$timestamp ....."

Kim

"Vladimir Grishchenko" <vladgri@xxxxxxxxxxx>
Sent by: pde-build-dev-bounces@xxxxxxxxxxx

01/10/2008 04:08 PM

Please respond to
"Eclipse PDE Build developers list." <pde-build-dev@xxxxxxxxxxx>

To	<pde-build-dev@xxxxxxxxxxx>
cc
Subject	[pde-build-dev] Timestamp in build.properties

Hi,

Would someone kindly explain what is the purpose of the timestamp property
in the build.properties file? It is set to 007 by default. I'm working
on
build automation for our product and would like to include timestamp as
a
build id in about.mappings but it is not working out of the box for some
reason. I also tried to do it in the postFetch target in the
customTargets.xml as

<target name="postFetch">
               <replace dir="${buildDirectory}/plugins"
value="${timestamp}"
token="@build@">
                    
           <include name="**/about.mappings"
/>
               </replace>
</target>

but ended up with the value 007 as build id, which is how timestamp is
defined in build.properties. Qualifiers of my plugins get substituted with
a
timestamp but this timestamp value seem to be inaccessible outside of the
eclipse.buildScript task. I'm using 3.3.1.1 as builder. I searched here
and
there but could not find an answer so please accept my apologies for asking
this on the dev list. 

Thanks,
Vladimir

_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev
_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev
_______________________________________________
pde-build-dev mailing list
pde-build-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-build-dev