It doesn't surprise me too much that the maven-jar-plugin still creates empty directories even when all files that were in that directory have been excluded. I haven't checked myself, but it sounds like a situation that the plugin author could easily have overlooked.
But it doesn't cause any problems does it? Just a minor wastage of space in the generated jarfile? In this case, it is probably worth filing a jira issue for this, but it should be marked "minor" or even "trivial" unless it causes actual problems for programs. Regards, Simon Patrizio Munzi schrieb: > Thanks for your answer, > > so is it a real problem...? > > Thanks > > Olivier Lamy wrote: >> Post an issue in jira. >> And attach a simple project test case to reproduce the issue. >> >> Thanks, >> -- >> Olivier >> >> 2008/3/11, Patrizio Munzi <[EMAIL PROTECTED]>: >> >>> Hi All, >>> >>> I'm trying to exclude some files from the built jar by using the >>> maven-jar-plugin exclude feature. >>> >>> Here's my configuration: >>> >>> <excludes> >>> <exclude>**/*.properties</exclude> >>> <exclude>**/*.xml</exclude> >>> <exclude>**/*.xsd</exclude> >>> </excludes> >>> >>> Although all the specified files are actually excluded from the >>> deployed >>> jar, the directory paths of the excluded files are still created into >>> the jar. >>> >>> I mean, if I have the following files under the resources directory: >>> >>> resources/log4j.properties >>> resources/xml/file.xml >>> resources/xml/schema/schema.xsd >>> >>> These files won't be included in the built jar, but I'll still have >>> the >>> following path into it: >>> >>> resources/xml/schema/ >>> >>> Is anyone aware of this problem with the maven-jar-plugin...? >>> >>> Thanks. >>> >>> Cheers >>> Patrizio >>> >>> -- > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
