Update of BndEditModel

[pkriens]

Now properly reflects the inheritance structure of Processor chains

@chrisrueger I made a few changes to your code, please verify

Signed-off-by: Peter Kriens Peter.Kriens@aQute.biz

[chrisrueger]

LGTM. The changes to my code seem minor. test.ProcessorTest.testPropertyKeysFindVisibles() seems still working.
Besides my comment about the javadoc of findVisibles() I have nothing else.

I checked out the code locally and did a few manuial tests. still working.

[chrisrueger]

I noticed one new warning recently, but could not figure out when it came in:

Description	Resource	Path	Location	Type
No translation found for macro: .	bnd.bnd	/bndtools.core	line 1	Bndtools Problem Marker

[pkriens]

I saw the warning. I could also not find it. Will investigate

[pkriens]

Found the warning. You added two lines to the _plugin.xml with ${.}:

		    <property name="pom" type="string" description="Points to a pom.xml file. This is exclusive with revision. Can be a comma separated list of files." default="${workspace}/cnf/pom.xml" />

The ${.} is a very special macro. It is handled with included files during inclusion because we know the file location then. In the pre processing of a file with the macro processor we have no idea where we are.

We might want to think about supporting this in the -includeresource process ...

[pkriens]

Misunderstood the use of the ${.}. It had to be escaped and i think you do not want to have cnf in the path. ${.} refers to the directory of the preprocessed file.

[chrisrueger]

Misunderstood the use of the ${.}. It had to be escaped and i think you do not want to have cnf in the path. ${.} refers to the directory of the preprocessed file.

Thanks for finding this.