[JIRA] (JENKINS-36095) already exists in the deployment repository
Title: Message Title Erra Jaggi assigned an issue to Dan Dillingham Jenkins / JENKINS-36095 already exists in the deployment repository Change By: Erra Jaggi Assignee: Daniel Dan Dillingham Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36095) already exists in the deployment repository
Title: Message Title Erra Jaggi assigned an issue to Daniel Jenkins / JENKINS-36095 already exists in the deployment repository Change By: Erra Jaggi Assignee: Daniel Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36095) already exists in the deployment repository
Title: Message Title Erra Jaggi assigned an issue to Unassigned Jenkins / JENKINS-36095 already exists in the deployment repository Change By: Erra Jaggi Assignee: Erra Jaggi Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36095) already exists in the deployment repository
Title: Message Title Erra Jaggi commented on JENKINS-36095 Re: already exists in the deployment repository I am also facing same issue. Have to manually undeploy ear from the server. We are using Jboss eap 7 and ant so cannot use maven plugin. Please suggest any workaround? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36095) already exists in the deployment repository
Title: Message Title Erra Jaggi assigned an issue to Erra Jaggi Jenkins / JENKINS-36095 already exists in the deployment repository Change By: Erra Jaggi Assignee: Erra Jaggi Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36095) already exists in the deployment repository
Title: Message Title sined sined created an issue Jenkins / JENKINS-36095 already exists in the deployment repository Issue Type: Bug Assignee: Unassigned Components: wildfly-deployer-plugin Created: 2016/Jun/20 8:52 PM Environment: Jenkins last version, Wildfly last version Priority: Critical Reporter: sined sined Hi All, the first deploy works fine. From the second it fails with the subject error. If I go to Wildfly management console and I undeploy, the Wildfly deploy manager plugin is able to deploy. There's a way to tell to wildfly deploy plugin to force the deploy, also if already presents? Add Comment
