Hi,
I'm having a project with some 15 or so modules. All those modules have
a manifest file which is provided by the developers. So I put some
config for the jar plugin in the parent pom to include that manifest for
all modules:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifestFile>path/to/MANIFEST.MF</manifestFile>
</archive>
</configuration>
</plugin>
OK, this is working, so far, so good. Now I have one other modul which
doesn't have a manifest file. Maven complains about the missing manifest
which is configured in the parent. How can I unset the manifestFile
configuration so the jar-plugin will go back to it's default behaviour
and create one?
My naive approach was this plugin configuration in the module's pom:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifestFile />
</archive>
</configuration>
</plugin>
which I thought might the the plugin make forget the manifestFile config
from the parent, but that doesn't work.
What would be the correct solution for this problem?
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
