Skip to content
This repository was archived by the owner on Nov 5, 2024. It is now read-only.

#9 fixes - execution of quasar-maven-plugin by inheritance from a pom parent fails#10

Open
cvuillecard wants to merge 1 commit intovy:masterfrom
cvuillecard:master
Open

#9 fixes - execution of quasar-maven-plugin by inheritance from a pom parent fails#10
cvuillecard wants to merge 1 commit intovy:masterfrom
cvuillecard:master

Conversation

@cvuillecard
Copy link
Copy Markdown

… submodules fails

  • deletion of unnecessary condition when buildDirectory is null.

Note : tested with multiple submodules in a maven project. Now we can declare the plugin execution in a parent pom inherited by other poms as maven sub-modules

…th submodules fails

- deletion of unnecessary condition when buildDirectory is null.

Note : tested with multiple submodules in a maven project. Now we can declare the plugin execution in a parent pom inherited by other poms as maven sub-modules
public void execute() throws MojoExecutionException {
getLog().info("Instrumenting Quasar classes...");

if (buildDirectory == null || !buildDirectory.isDirectory())
Copy link
Copy Markdown
Author

@cvuillecard cvuillecard Aug 27, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

buildDirectory points to ${project.build.directory} default maven build property.

Even if the 'target' directory doesn't exist, the plugin execution is not blocked. Normally we don't need to check if the current working directory is a directory because ${project.build.directory} always points to the 'target' directory of the pom's parent directory.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant