search

jbossas / jboss-as-maven-plugin

Maven plugin to deploy applications to JBoss AS 7 (moved to https://github.com/wildfly/wildfly-maven-plugin)
74 stars 69 forks source link

It is not allowed to deploy from a pom module #16

Closed flatstep closed 12 years ago

flatstep commented 12 years ago

We have a project with a separate war module and a separate deployment module. It is not needed to create a jar for the last one, because it only updates the datebase structure and redeploys the application. All we need is a pom deployment module and specify the depend module to deploy.

Sadly this is not possible without workarounds.

POM is not allowed.

It is also not possible to specify the dependend module directly. We need to copy the war artifact in the target folder. After that it is possible to specify which artifact to deploy with the undocumented configuration filename.

In my point of view this is a convenient usecase which should be directly supported by the plugin.

jamezp commented 12 years ago

Would something like the following work? https://github.com/jamezp/jboss-as-maven-plugin/commit/290c6cd7f9474d0754aa5d1f4a18f01d42df0a2a

What you would do is use a <checkPackaging>false</checkPackaging> or -DcheckPackinging=false option to ignore the check for the package type.

jamezp commented 12 years ago

Added a property <check-packaging>false</check-packaging>. Command line option would be -DcheckPackaging=false. The default is true.