Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338481 - use :local: to rewrite maps during production build
Summary: use :local: to rewrite maps during production build
Status: RESOLVED FIXED
Alias: None
Product: WTP Releng
Classification: WebTools
Component: releng (show other bugs)
Version: 3.10   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.10.0   Edit
Assignee: David Williams CLA
QA Contact: David Williams CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-28 17:16 EST by David Williams CLA
Modified: 2018-06-29 15:30 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2011-02-28 17:16:19 EST
I tried this once before, but ran into trouble with source references. 
See bug 337621. 

I've discovered the solution is implied in a blog post by Kim: 

http://relengofthenerds.blogspot.com/2010/04/wheres-source.html

She's talking about ext to pserver, but idea is the same ... replace with desired values in the "postFetch" phase, in the sourceReferences.properties file that is created.
Comment 1 David Williams CLA 2011-03-01 02:29:18 EST
Besides re-writing back to original for sourceReferences.properties I also had to do the same for "directory.txt" (which is also produced automatically by PDE build). 

And, the sourceReferences.properties had values escaped, so in one spot had to replace :\local:\ with \:pserver\:etc but in another replace :local: with :pserver:etc. 

I also find it odd that "anonymous@" is not left in the source reference in manifest.mf, even though it is in the sourceReferences.properties I'm assuming that's by design.
Comment 2 David Williams CLA 2011-03-01 15:04:44 EST
> 
> I also find it odd that "anonymous@" is not left in the source reference in
> manifest.mf, even though it is in the sourceReferences.properties I'm assuming
> that's by design.

Correction. It _is_ left in when I put it there explicitly, as part of the "replace". But, then that causes lots of comparator differences ... so, I think I'll leave out, for now, until all the other "local" problems are fixed (as mentioned in bug 337621).