[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.tools.buckminster] Re: How to include component version with an action path 
Hi Tas,

On 08/19/2009 09:31 AM, Tas Frangoullides wrote: 
Hi Thomas,

I did notice the extractFeatureVersion task but couldn't think of a way
to use as part of an action's products. My current understanding of
actions is that you need to pre-declare output paths and artifacts in
the cspec/cspex, which means I need to know it before the action runs.
It looks like a chicken and egg situation to me?

The way we solve that is to use a folder as the output path and then let the ant-script create the part of the name that includes the version.

My end goal is to generate and publish multiple product zips during the
build. Is this the sort of thing you'd place in a high-level build
script, for example in a top-level releng component. If I had this
component use the buckminster task to invoke the product archive task
for each target platform would I be able to extract the version number
(with qualifier) there as it is after the build of the site?

We have some work in progress to make this kind of thing declarable (and of course runnable) in a cspec. I know it doesn't help you much right now but it might be good to know that it's coming.

You can subscribe yourself to bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=286637 "Add ability to repeat actions with different input".

Regards,
Thomas Hallgren