Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do I access project.build.directory for a maven clover build

clover runs two lifecycles, one normal and one forked. The default non-clover workspace is ${project.build.directory} and the default clover workspace is ${project.build.directory}/clover. I have maven plugins that will write to the workspace in order to get files into certain artifacts. For example, one plugin writes to the ${project.build.directory}/classes/ directory to include the file in the jar and another writes to ${project.build.directory}/${project.build.finalName} to have files included in the assembly package. In order to get these files written to both places I have to set up plugin executions twice; once to write to ${project.build.directory} and once to write to ${project.build.directory}/clover. Is there a better way to do this? Originally I epxected that the clover fork would just reset ${project.build.directory} to evaluate to the clover output directory and then I could just use that parameter. But it does not seem to work.

1 answer

0 votes

Which version of Maven do you use? 2.x or 3.x? Do you want to use ${project.build.directory} in the pom.xml or access it from your plugin?

If case you use Maven 3.x and ${project.build.directory} in the pom.xml then it won't work. A reason is that the way how properties are evaluated have changed in Maven 3. Their values are not being refreshed for the forked lifecycle (as Maven 2 does) in pom.xml. However, you can still access valid value in a forked lifecycle from the mojo. You can find an examplary "hack" here.

If your case is different, then please give me a little bit more details so that I could investigate it.

Cheers
Marek

BTW: the name of the forked lifecycle ("clover") had never changed since the beginning so it's quite safe to assume that the location is "${project.build.directory}/clover" :-)

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Jira Cloud Performance Improvements

Hello everyone, I am a product manager in the Jira Cloud team focused on making sure our customers have a delightful experience using our products. Towards that goal, one of the areas which is extr...

171 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you