{"action":"opened","issue":{"url":"https://api.github.com/repos/bparry02/jboss-modules-demo/issues/5","repository_url":"https://api.github.com/repos/bparry02/jboss-modules-demo","labels_url":"https://api.github.com/repos/bparry02/jboss-modules-demo/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/bparry02/jboss-modules-demo/issues/5/comments","events_url":"https://api.github.com/repos/bparry02/jboss-modules-demo/issues/5/events","html_url":"https://github.com/bparry02/jboss-modules-demo/issues/5","id":167089154,"number":5,"title":"Additional Steps for dynamic","user":{"login":"bparry02","id":5055116,"avatar_url":"https://avatars.githubusercontent.com/u/5055116?v=3","gravatar_id":"","url":"https://api.github.com/users/bparry02","html_url":"https://github.com/bparry02","followers_url":"https://api.github.com/users/bparry02/followers","following_url":"https://api.github.com/users/bparry02/following{/other_user}","gists_url":"https://api.github.com/users/bparry02/gists{/gist_id}","starred_url":"https://api.github.com/users/bparry02/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bparry02/subscriptions","organizations_url":"https://api.github.com/users/bparry02/orgs","repos_url":"https://api.github.com/users/bparry02/repos","events_url":"https://api.github.com/users/bparry02/events{/privacy}","received_events_url":"https://api.github.com/users/bparry02/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-22T17:03:14Z","updated_at":"2016-07-22T17:03:14Z","closed_at":null,"body":"Explain error message\r\n=====\r\nIf the deployment fails, you may get a message like the one below:\r\n\r\n       service jboss.module.spec.service.\"deployment.common-utils-1.0.jar\".main (missing)...\r\n\r\n\r\nSafely updating and redeploying dynamic modules\r\n======\r\n\r\nTIP: TODO: include steps to redeploy dynamic modules and restarting/reloading appropriately\r\n\r\nTIP: TODO: same for domain mode\r\n\r\nCreating a consistent name for the dynamic module JAR\r\n==== \r\n\r\nBy default, the dynamic module's name is the filename of the JAR file when it is deployed to JBoss. Since Maven appends the artifact version to the filename, the dynamic module's name will change for each new release. This means all dependent applications must update their respective jboss-deployment-structure.xml file and redeploy as well. \r\n\r\nNOTE: This can be a valid deployment strategy, see the next section Rolling deployments for dynamic modules.\r\n\r\nTIP: TODO: Can deployment name/runtime name be specified via cli to change module name?\r\n\r\nNOTE: Remember, if the `<finalName>` attribute is not specified in the EAR's pom.xml, the filename of the module will change each time the version changes. Consider using a `finalName` of `${project.artifactId}` for the ear to make new releases easier.\r\n\r\nRolling deployments for dynamic modules\r\n==== "}}
{"actor":{"display_login":"bparry02"}}