Using version in artifact filename, fix for APEX-237

[pramodin]

No description provided.

[pramodin]

@tweise see

[tweise]

This does not work as depending on the profile there are other artifacts that will match in the script. That's the reason why the artifact name was set to be a constant name in the target directory in first place. What problem are you trying to solve here?

[pramodin]

You mean there could be other artifacts than tests? The other way I was thinking was to get the version of the project by running a maven command and then constructing the jar filename. The way to get the version is explained here
http://stackoverflow.com/questions/3545292/how-to-get-maven-project-version-to-the-bash-command-line
Thought that would be an overkill for what we have now so didn't do that.

There is no immediate problem but this is being suggested an improvement. Seems that we are doing this because it helps coding the scripts easier but there is ambiguity when someone sees the jar file. It is not consistent with the other jar names.

[tweise]

As you say you end up with convoluted logic in the script. Let's find out whether the file name in the target directory is really important for other use.

[243826]

May be look at resource formatting. There is also another way to pass this kind of information through maven. If you can dig up jarpath source code, probably I had used something similar there.