[jboss-jira] [JBoss JIRA] (WFLY-2725) Class-Path: . can cause JBAS011046: A component named 'TestBean' is already defined in this module

[Brad Maxwell (JIRA)]

Brad Maxwell created WFLY-2725:
----------------------------------

             Summary: Class-Path: . can cause JBAS011046: A component named 'TestBean' is already defined in this module
                 Key: WFLY-2725
                 URL: https://issues.jboss.org/browse/WFLY-2725
             Project: WildFly
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Server
    Affects Versions: 8.0.0.CR1
            Reporter: Brad Maxwell
            Assignee: Stuart Douglas


'JBAS011046: A component named
'TestBean' is already defined in this module', I have narrowed it
down to it occurs if they have a jar manifest with Class-Path: .
It looks like when deploying it looks at the jar with the manifest
entry which then must be having it scan the jar containing the EJB
again and failing.

Having the Class-Path: . doesn't really make sense to me, however it
also seems like we should not be trying to deploy it twice.

It appears ManifestClassPathProcessor ignores the . when the Class-Path is in a jar at the root of an ear but not when the jar is in a war's WEB-INF/lib

server/src/main/java/org/jboss/as/server/deployment/module/ManifestClassPathProcessor.java

--
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