When I read the configuration doc for war:war, it says:
excludes (Optional) The comma separated list of tokens to exclude
from the WAR.
Except it doesn't seem to work like that. I'm trying to use
<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<excludes>**/*.fla,**/*.as</excludes>
</configuration>
</plugin>
In this incarnation nothing is excluded. I also have tried replacing
the comma with a space. When I say
<excludes>**/*.fla</excludes>
Then the expected files are included, but that's only have the game.
I can go through the several other incarnations I've tried, but I
suspect it would be merely tiresome to the reader.
Is this a bug, known or otherwise? Or am I missing something so
obvious I can't see it?
Ken
P.S. I got into this because I was working with Flash whose input
files (.fla and .as) want to live with their various configuration
files (mostly .xml). I had tried to set up src/main/flash, but then
I could get resources from there *and* from src/main/webapp into the
top level of the war. That was my preferred model, but the war
plugin seems tightly wedded to the single input directory model.
Which is well and good, but this required me to merge all the flash
stuff into webapp so I could do flash development with the
configuration files that would end up in the war, and then I got to
the exclusion problem above. This is mostly just context, but if
someone has another way to solve the original issue I'm open to
suggestions.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
