Rethink your approach.
It is very common to use e.g. 1.4.2 for a release version and then 1.4.3-SNAPSHOT for the development to the next.
When you need to maintain release 1.4.2 THEN branch it from the commit that originated your 1.4.2 artifact.
Then you tell Jenkins the location of your repository and the branch name, resulting in a file set being checked out, and then you tell Jenkins to use maven on your project to build it.
Note: I've found that it is very beneficial to use a single pom.xml to build the actual artifact and another pom.xml to create the actual bits to go to the customer.