Maven fails to include generated resources

I haven't spent any time looking into it but I would suspect that because on a clean the resource directory

			<resource>
				<directory>target/generated-sources/axistools/java2wsdl</directory>
			</resource>

does not exist that it is not included in the project model.

The second run works as expected because the directory was created on the first run.

Why isn't the axistools-maven-plugin programatically adding in additional resources so the user doesn't need to modify their pom?

I am experiencing the same problem.

AxisTools does add the resources. Its execute() method ends with:

projectHelper.addResource( project, outputDirectory.getAbsolutePath(), Collections.singletonList( "*/.wsdl" ),
Collections.EMPTY_LIST );

I have added some logs in a local modification of AxisTools. The plugin is executed, and after the above line, project.getResources() includes this new set.

However, the jar plugin seems to not include any resource outside of target/classes.

Maybe the following will be of help

if I execute:

mvn clean compile axistools:java2wsdl package

the resulting jar includes the wsdl file. If I just do:

mvn clean package

no wsdl is included into the jar.

I have found two workarounds:

1. The one described above. Only useful if you have control over the command line
2. Set the axis-tools output directory to "target/classes"

This a bug of the Axis Tools Plugin, not the Jar Plugin. The Jar Plugin is by design not responsible for resources, it takes the stuff from target/classes and produces an archive. It's the Resources Plugin that copies the resources to the build's output directory. Now, the Resources Plugin is run in the lifecycle phase "process-resources", which happens before "process-classes", which is the default phase for "java2wsdl". So whatever new resoureces the Axis Tools Plugin adds, they won't be seen by the Resources Plugin, and hence don't show up in the output directory.

In general, plugins that run after the Resources Plugin need to directly output their files to the project's build directory, just like one cannot add additional source directories once the Compiler Plugin has been run.

Adding an additonal execution of resources:resources could be a workaround, though I haven't though much about possible side effects.