Venkata Krishnan wrote:
Alright, I played around with
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-shade-plugin/src/main/java/org/apache/maven/plugins/shade/resource/XmlAppendingTransformer.javaa
bit and it seems like it gives all that I have been looking for - a
neat
aggregated xml file that is valid.  I will now go and see how to plug this
in our dist bundle.


If I understand correctly, it looks like you're now going away from the solution we discussed before in this thread (and which was going to work), and are going to use the above shade plugin transformer to merge multiple definitions.xml files.

I'm OK with that if you make it really work, but at first sight the logic in the XmlAppendingTransformer looks a little 'fragile' :)

Can you please try two things?

- two definitions.xml files that use different namespaces for their policySets?

- two definitions.xml files that use a namespace prefix 'policy' mapped to two different namespaces?

If it works, then, great! If it doesn't work you'll just need to write your own shade transformer, and/or contribute a fix to Shade.
--
Jean-Sebastien

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to