[ https://issues.jboss.org/browse/SRAMP-506?page=com.atlassian.jira.plugin.... ] David virgil naranjo commented on SRAMP-506: -------------------------------------------- The extended type has to be included for example for uploading switchyard applications. In that case, it is needed an extra param to specify the extended type. I have been checking the maven deploy:deploy-file plugin: http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html The easier solution is to add a classifier, and in the server side check if the classifier correspond to a extended type used by us, or check if the classifier is different than the common maven classifiers, test, sources... In case it is different than test or sources ( I do not know if by default they are more), then we could set the extended type. This is the easy solution.. But maybe it could be confusing, because maybe sometimes we want to add a classifier, that is not really an extended type. Another solution could be (thanks to Mark Savy), it is to include the artifact type in the META-INF MANIFEST file. Then the user should add this info to the jar, before deploying. Another option maybe could be to create our custom deploy plugin, that extends from the official one, and extends the functionality to add a param in the urls like artifactType. Here the only problem is that the user, when he wants to include an extended artifact type has to disable the official maven deploy plugin (skip) and include the s-ramp one. -- This message was sent by Atlassian JIRA (v6.2.6#6264)