Using TeamCity Enterprise 5.1.1 (build 13398) with TeamCity Artifactory Plugin 1.0.1.
I have a project "xyz" with group ID "a.b" which contains a child module "xyz-properties", from which the TeamCity Maven Runner produces a file xyz/xyz-properties/target/xyz-properties-VERSION.properties on the local filesystem. As expected, the TeamCity Artifactory plugin deploys:
[17:26:50]: Deploying artifact: a/b/xyz-properties/VERSION/xyz-properties-VERSION.pom
To deploy the actual properties artifact, I then configure the following in the Published Artifacts plugin config as described in http://confluence.jetbrains.net/display/TCD5/Build+Artifact:
However, instead of getting the expected artifact a/b/xyz/properties/VERSION/xyz-properties-VERSION.properties in Artifactory, I get the following:
[17:26:57]: Deploying artifact: a/b/xyz-properties/NETSTREAM-SNAPSHOT/twig/twig-properties/target/twig-properties-NETSTREAM-SNAPSHOT.properties
It looks as though the plugin is appending the local filesystem pathname to the target directory within Artifactory, when it should just append the local filesystem filename.
This is a serious problem for us as we wish to store application configuration within Artifactory. Please advise if a workaround is possible in the Published Artifacts configuration. Thanks.