It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,884
×12,010

question asked: Sep 21 '12, 3:09 p.m.
question was seen: 3,777 times
last updated: Sep 21 '12, 5:06 p.m.

Related questions

Maven 3 environment properties not set from the build engine

0
Shyam Gavulla (1●1●1) | asked Sep 21 '12, 3:09 p.m.
 Hello everyone,
We are integrating Maven 3 and RTC and got into an issue. I am not able to pass custom properties using java arguments. I have a variable defined as enviornment.name whose default value is dev. When I pass -Denvironment.name=test, the value is still dev. The same works fine in command line using maven. 
"mvn -Denvironment.name=test clean" works fine from the command line. It looks like it is an issue with RTC and maven integration. 
Has anyone seen this issue before with Maven 3 and RTC?

Any help will be greatly appreciated. 

Thank you,
Shyam

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Shyam Gavulla (1●1●1) | answered Sep 21 '12, 5:06 p.m.
 Update:
It looks like if the default values exist then RTC is not using the JVM arguments. I removed the default values from the POM and it works. It seems like an issue with RTC and Maven integration. 


Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.