>>>>> "Stuart McCulloch" <[EMAIL PROTECTED]>:
> yes, the <manifestLocation> is a File parameter, so if you use a
> relative path Maven will calculate it relative to the ${basedir}
Hm... thinking back, where I've seen issues with this have been when I
have inherited a setting from a parent with packaging POM, and then
verified that it have worked when running in the project in question,
but then have failed when running the project as part of a
multi-project.
Then I've had to go in and add ${basedir} to the settings, and it have
worked (the plugins I've seen these issues in have been pde-maven-plugin
and maven-clean-plugin).
But you're saying leaving ${basedir} out is safe?
I put it in there yesterday just to be sure, and it seemed to work as
well. I put the <manifestLocation> setting into a parent with packaging
POM, together with a maven-clean-plugin setting telling it to delete the
MANIFEST.MF directory on "mvn clean".
