Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.22
-
Fix Version/s: 1.26
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
In my case, Maven builds into a directory which isn't relative to the project's one
<build>
<directory>MyBuildDirectory</directory>
<outputDirectory>${project.build.directory}/classes</outputDirectory>
<testOutputDirectory>${project.build.directory}/test-classes</testOutputDirectory>
...
</buid>
Using maven-enunciate-slim-plugin assemble goal, many files are copied into $
{project.directory}/target/$
{project.build.finalName}, instead of ${project.build.directory}/${project.build.finalName}.
The war packaging fails after because a merged web.xml isn't found.
Setting webappDirectory to $
{project.build.directory}/$
{project.build.finalName}into configuration doesn't help, as mojo expects it to be relative to the project dir:
webAppConfig.setDir(new File(project.getBasedir(), webappDirectory).getAbsolutePath());
Thanks for the report.