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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,455,449
Community Members
 
Community Events
175
Community Groups

Specify maven executable to path in checked out repository

Edited

I have a project where the maven version I'd like to use for the build is part of the project's git repository.  I'd like to define a Maven 3 executable to use the version in the checked-out repository (the one that is part of the build).

I tried to define an executable path as 

${bamboo_build_working_directory}/env/thirdparty/apache-maven-3.5.2

and

${bamboo.build.working.directory}/env/thirdparty/apache-maven-3.5.2

But it doesn't seem that the executable is being found. 

Is it possible to use Bamboo environment variables in defining an Executable?

1 answer

1 accepted

1 vote
Answer accepted

No, using variables as Executable paths is not supported.

Using relative path:

env/thirdparty/apache-maven-3.5.2

seems to work for me though, so you might want to give it a shot.

Great suggestion.  That works for me too.  Thanks for the help.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events