Jenkins/Artifactory Integration

I've been mulling over how best to get the deployment packages we create in Jenkins into BuildMaster and am at a bit of a loss as to the best approach so I've come here for some guidance.

Background:
We build, test and create deployment packages in Jenkins.
There are 4 components to our application - client, server, server config, database - a release may consist of one or more of those components.
We only create the deployment packages when we are ready to deploy to test (ie we run a job in Jenkins for each component we want to include)
We have just started placing the resulting packages into Artifactory (previously just saved to file system)

Options:
Here's some of my thoughts:

When we create a build enter name of packages want into variables and use that to retrieve correct package from Artifactory (this is what we do right now)
Query Artifactory (just assuming this possible) for the latest set of files and store that value in a variable and pull the artifacts out of Artifactory for each environment deploying to
Pretty much same as #2 but add files into BuildMasters internal artifact library for releasing to subsequent environments (this makes me question why use Artifactory at all)

I'm leaning towards option 2, although I am a little concerned that I'm loosing clarity about what's going into a build, but I think that it reduces the chance of a typo causing the wrong set of files getting into a release.

What would your approach be?

All of these seem valid approaches... #1 obviously has the most flexibility in getting any artifact version.

We will soon be releasing an Artifactory Extension that will make Artifactory interactions a little easier.