ArtifactFile not overridable - issues with multi-configuration
Closed this issue · 1 comments
jbye commented
I'm using the beanstalk-maven-plugin in a multi-configuration project, and I am having problems uploading the source bundle because the artifactFile points at the finalName and it does not seem to be configurable.
When I build my project, I end up with 3 different WARs, each with its own classifier, for example:
"blah-ws-dev.war", "blah-ws-test.war", "blah-ws-prod.war". The beanstalk-maven-plugin will try to upload "blah-ws.war" which does not exist. If I could override artifactFile, I could then specify which artifact I want to be deployed.
aldrinleal commented
Beanstalker works with only 1 application per war.
An alternate would be to use m-w-p's Overlays Feature