|
|
| Re: Finding the location of another component [message #688060 is a reply to message #687995] |
Thu, 23 June 2011 19:39  |
 Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
IIRC it is possible to contribute ant actions to the environment via
extension points. I think this is briefly discussed in the documentation
- esp. how to access such actions. From there it should be possible to
figure out how buckminster does this and do something similar.
Regards
- henrik
On 6/23/11 6:24 PM, Matthew Webber wrote:
> We have around 20 separate (but similar) products that we build. We use
> a "create.product" script (from
> http://www.ralfebert.de/blog/eclipsercp/rcp_builds/).
>
> Rather than put the same product.ant script in 20 different site
> projects, I just put it in one separate "builder" project. Then all 20
> CSPEX point to it: the actors all say
>
> <property key="buildFile"
> value="${workspace.root}/builder/buckminster_actions/product.ant" />
>
> Unfortunately, this assumes a certain workspace layout, and is too
> rigid. I attempted to replace ${workspace.root}/builder with
> ${project_loc:/builder}, but it simply does not get resolved.
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=329628 suggests that it
> should work, but it doesn't.
>
> Is there a way I can get the path to the other project (knowing just the
> project name)? The project is a component of type "buckminster".
> Something using buckminster.component?
> Or am I trying to be too clever, and should I just put a copy of
> product.ant in each cspex?
>
> Incidentally, is there any plan to have create.product a standard
> Buckminster action that works "out of the box"? This seems to be a
> common requirement, but everyone needs to add it themselves.
>
> Thanks
> Matthew
>
|
|
|
Powered by
FUDForum. Page generated in 0.03700 seconds
] 
Search
Help
Register
Login
Home
