[jboss-jira] [JBoss JIRA] (AS7-6449) jboss-cli deploy --force fails for OSGi bundles

Jarkko Rantavuori (JIRA) jira-events at lists.jboss.org
Mon Feb 18 04:59:56 EST 2013


     [ https://issues.jboss.org/browse/AS7-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarkko Rantavuori updated AS7-6449:
-----------------------------------

    Description: If you try to deploy already-deployed .jar from cli, it says "already exists in the deployment repository (use --force to replace the existing content in the repository)". However, using --force errors with "service already registered" if it is an OSGi bundle.  (was: If you try to deploy already-deployed .war from cli, it says "already exists in the deployment repository (use --force to replace the existing content in the repository)". However, using --force errors with "service already registered" if it is an OSGi bundle.)

    
> jboss-cli deploy --force fails for OSGi bundles
> -----------------------------------------------
>
>                 Key: AS7-6449
>                 URL: https://issues.jboss.org/browse/AS7-6449
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: CLI, OSGi
>    Affects Versions: 7.2.0.Alpha1
>         Environment: Windows 7, 64-bit
>            Reporter: Jarkko Rantavuori
>            Assignee: Thomas Diesler
>             Fix For: 7.2.0.CR1
>
>
> If you try to deploy already-deployed .jar from cli, it says "already exists in the deployment repository (use --force to replace the existing content in the repository)". However, using --force errors with "service already registered" if it is an OSGi bundle.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list