On 02/15/2011 12:58 PM, Steve Cohen wrote:
I can set the permissions of <fileSet>s and <moduleSet>s and
<dependencySet>s in the maven-assembly-plugin, but it seems from the
online documentation that I can't do so on the <baseDir>. What is more,
when assembling a <zip> format, the perms default to 777. At least
that's what I get when I unzip the file (having erased the basedir
previously so that there's no chance of previous permissions persisting).
Is there any way to control this? I am using my own assembly descriptor.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
This worked for me:
<fileSets>
<fileSet>
<outputDirectory>/</outputDirectory>
<fileMode>750</fileMode>
<directoryMode>750</directoryMode>
<includes>
<include>./</include>
</includes>
</fileSet>
...
Is there a THOROUGH description of include/exclude wildcards anywhere?
I had to hunt and peck my way through all kinds of possibilities before
I found something that worked as I wanted it to. For example
<excludes>
<exclude>**</exclude>
</excludes>
didn't work because the root directory was included in the exclusion,
yet, without the <include> I had above, the root directory was not
included. This topic could do with a bit of rigorous documentation that
seems lacking. It's treated as self-evidently obvious how this works,
and usually it is, but then you have these odd cases to scratch your
head on.
I think the problem here is that <includes> has a dual meaning. It's
main meaning is whether the set should be included in the archive, but
it also has this subsidary use that defines where the modes should apply
and the two are not in synch.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
