Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317922 - Strange behaviour trying to override default about.mappings action in Bucky 3.6
Summary: Strange behaviour trying to override default about.mappings action in Bucky 3.6
Status: RESOLVED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-25 03:21 EDT by Philipp Nanz CLA
Modified: 2019-02-25 14:41 EST (History)
1 user (show)

See Also:


Attachments
3.5 vs 3.6 solution (4.10 KB, application/zip)
2010-06-25 03:23 EDT, Philipp Nanz CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Nanz CLA 2010-06-25 03:21:57 EDT
Build Identifier: 3.6 / org.eclipse.buckminster.core=1.2.360.r11456

I'm having trouble replacing a second token in about mappings with 3.6. The old way doesn't work because there is now a default action for this, and trying to override brings errors.

Please inspect the attached zip file for details.

Reproducible: Always

Steps to Reproduce:
Throw the buckminster.cspex from 3_6 into any eclipse plugin project with an about.mappings file, refresh and take a look on the buckminster console: you should read some error containing buildFileId
Comment 1 Philipp Nanz CLA 2010-06-25 03:23:53 EDT
Created attachment 172714 [details]
3.5 vs 3.6 solution

Please note I didn't have 3.6 available on the computer where I made this zip. I rewrote my changes from memory, hope all goes well. If not, I can provide a more accurate example tonight.
Comment 2 Philipp Nanz CLA 2010-06-28 20:56:29 EDT
A work-around is outlined here: http://www.eclipse.org/forums/index.php?t=msg&goto=543295&#msg_543295

Given that, I have no more urgent need for a bugfix... Still I think it should be investigated how (or if at all) this action is supposed to be overridden by clients
Comment 3 Thomas Hallgren CLA 2010-07-21 06:18:36 EDT
An attribute (action, group, or artifact) can be overridden in one of two ways.


You want to reuse the old action but do something more after it has executed:
1. Rename the old action
2. Create a new action with the original name that uses the renamed action as a prerequisite

You want to reuse the old action but execute something before it executes.
1. Create a new action that does what you want.
2. Add a prerequisite for your new action to the old action. Possibly remove other prerequisites.

You want to completely override the old action.
1. Remove the old action.
2. Add a new action with the same name.