Ivy changes for JBESB-1988 cause a clean ivy build to fail ---------------------------------------------------------- Key: JBESB-2029 URL: https://jira.jboss.org/jira/browse/JBESB-2029 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.4 CP1, 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP1, 4.5 The reason for one of the changes is that the mvel pom.xml does not match the hierarchy in which it is found. This causes ivy to reject the configuration. I thought I had fixed this issue but my changes actually broke the build. This was hidden from me/CI as we had already downloaded the appropriate metadata. The real way to fix this is to change the mvel organisation to org.codehaus.mvel (reflecting the pom organisation) and include a module definition in the ivysettings which will override the normal path configuration of the m2 repository. My bad, apologies to all. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira