[ https://issues.jboss.org/browse/AS7-2067?page=com.atlassian.jira.plugin.s... ] Candice Chen updated AS7-2067: ------------------------------ Attachment: migrate.ear -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2067?page=com.atlassian.jira.plugin.s... ] jaikiran pai updated AS7-2067: ------------------------------ Priority: Major (was: Critical) Component/s: (was: EJB) Forum Reference: http://community.jboss.org/message/630869#630869 (was: http://community.jboss.org/message/630869#630869) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2067?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-2067: ---------------------------------- Fix Version/s: 7.1.0.Final Forum Reference: http://community.jboss.org/message/630869#630869 (was: http://community.jboss.org/message/630869#630869) This says "Pull Request Sent" but has no linked pull request. I suspect it's been merged and this can be resolved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2067?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-2067: ----------------------------------- Hmm, how do I change the "Pull request sent" workflow status? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2067?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-2067: ----------------------------------- I had a look at this issue. The problem is due to the inconsistency with the ServiceName of the subdeployment unit. The SubDeploymentProcessor (correctly) takes into account the relative path of the subdeployment while adding a dependency to the phase context: {code} final ResourceRoot parentRoot = deploymentUnit.getAttachment(Attachments.DEPLOYMENT_ROOT); final String relativePath = childRoot.getRoot().getPathNameRelativeTo(parentRoot.getRoot()); final ServiceName serviceName = Services.deploymentUnitName(deploymentUnit.getName(), relativePath); ... //we also need a dep on the first phase of the sub deployments phaseContext.addToAttachmentList(Attachments.NEXT_PHASE_DEPS, serviceName.append(ServiceName.of(Phase.STRUCTURE.name()))); {code} However, the AbstractDeploymentUnitService/SubDeploymentUnitService don't take into account the relative path while creating a ServiceName out of the DeploymentUnit. The fix doesn't appear to be straightforward since the DeploymentUnit creation would need to know the ResourceRoot if we have to take into account the relative path while creating the ServiceName for that deployment unit. Also given the fact that this requires a change to the very core of deployment unit processing, I don't think it's worth introducing this fix at this stage for 7.1.0.Final. I'm pushing this out for 7.1.1. For now the workaround mentioned in the description (i.e. moving the subdeployment to the root of the .ear) should work fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2067?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-2067: ------------------------------ Fix Version/s: 7.1.2.Final (was: 7.1.1.Final) This issue is being relocated to 7.1.2 so that 7.1.1 only contains criticals, blockers, and EAP LA issues (which are probably not yet at the right status, or need an extra triage pass). If these issues are completed in a 7.1.1 timeframe please change the fix version. Although if you forget I will bulk correct. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2067?page=com.atlassian.jira.plugin.s... ] jaikiran pai updated AS7-2067: ------------------------------ Assignee: David Lloyd (was: jaikiran pai) Forum Reference: http://community.jboss.org/message/630869#630869 (was: http://community.jboss.org/message/630869#630869) I'm going to unassign myself from this for now and set it the assignee to Automatic. The change might impact a lot of EE related DUP code. My comment in this JIRA has the details on what the issue is and at this point I haven't investigated for a fix. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-2067?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-2067: ---------------------------------- Summary: An ear file with modules in subfolders can not deploy under AS 7.0 (was: The ear file can not deploy under AS 7.0) Forum Reference: http://community.jboss.org/message/630869#630869 (was: http://community.jboss.org/message/630869#630869) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira