[ https://issues.jboss.org/browse/JBIDE-9410?page=com.atlassian.jira.plugin... ] Nick Boldt updated JBIDE-9410: ------------------------------ Description: I have been wrestling with this problem (or similar) for about the last two weeks: {code} [INFO] [Software being installed: com.jboss.jbds.site raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT, Only one of the following can be installed at once: [ org.jboss.tools.xulrunner.initializer 3.1.0.v20110726-1048-H409-M3, org.jboss.tools.xulrunner.initializer 3.1.0.v20110726-1947-H410-M3], Cannot satisfy dependency: com.jboss.jbds.site raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT depends on: org.jboss.tools.richfaces.feature.feature.group 0.0.0, Cannot satisfy dependency: com.jboss.jbds.site raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT depends on: org.jboss.tools.xulrunner.feature.feature.group 0.0.0, Cannot satisfy dependency: org.jboss.tools.richfaces.feature.feature.group 3.3.0.v20110726-1419-H339-M3 depends on: org.jboss.tools.xulrunner.initializer [3.1.0.v20110726-1048-H409-M3], Cannot satisfy dependency: org.jboss.tools.xulrunner.feature.feature.group 1.9.216.v20110726-1947-H410-M3 depends on: org.jboss.tools.xulrunner.initializer [3.1.0.v20110726-1947-H410-M3]] {code} Basically, this is caused by: 1. VPE spinning a build which includes org.jboss.tools.xulrunner.initializer 3.1.0.v20110726-1048-H409-M3, then 2. JSF (richfaces) spins and picks up that H409 build and includes it in its site. Then, 3. while the JBDS update site is spinning, 4. the VPE build spins again and now depends on H410 instead of H409. 5. Because the aggregate can only include ONE version and each feature has strict plugin version requirements, there is no solution for p2 to be able to create a site with the two versions of the plugins installed concurrently. So, either we need to build these two components together as a single job, or we need some other way to ensure this "vpe respin breaks jsf installability" problem is solved. Maybe the richfaces.feature should DEPEND ON the xulrunner.feature instead of INCLUDING the org.jboss.tools.xulrunner.initializer plugin? Or just depend on that single plugin (again, rather than including it) ? was: I have been wrestling with this problem (or similar) for about the last two weeks: {code} [INFO] [Software being installed: com.jboss.jbds.site raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT, Only one of the following can be installed at once: [ org.jboss.tools.xulrunner.initializer 3.1.0.v20110726-1048-H409-M3, org.jboss.tools.xulrunner.initializer 3.1.0.v20110726-1947-H410-M3], Cannot satisfy dependency: com.jboss.jbds.site raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT depends on: org.jboss.tools.richfaces.feature.feature.group 0.0.0, Cannot satisfy dependency: com.jboss.jbds.site raw:0.0.2.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.2-SNAPSHOT depends on: org.jboss.tools.xulrunner.feature.feature.group 0.0.0, Cannot satisfy dependency: org.jboss.tools.richfaces.feature.feature.group 3.3.0.v20110726-1419-H339-M3 depends on: org.jboss.tools.xulrunner.initializer [3.1.0.v20110726-1048-H409-M3], Cannot satisfy dependency: org.jboss.tools.xulrunner.feature.feature.group 1.9.216.v20110726-1947-H410-M3 depends on: org.jboss.tools.xulrunner.initializer [3.1.0.v20110726-1947-H410-M3]] Basically, this is caused by VPE spinning a build which includes org.jboss.tools.xulrunner.initializer 3.1.0.v20110726-1048-H409-M3, then JSF (richfaces) spins and picks up that H409 build and includes it in its site. Then, while the JBDS update site is spinning, the VPE build spins again and now depends on H410 instead of H409. Because the aggregate can only include ONE version and each feature has strict version requirements, there is no solution for p2 to be able to create a site with the two inputs. So, either we need to build these two components together as a single job, or we need some other way to ensure this "vpe respin breaks jsf installability" problem is solved. Maybe the richfaces.feature should DEPEND ON the xulrunner.feature instead of INCLUDING the org.jboss.tools.xulrunner.initializer plugin? Or just depend on that single plugin? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9410?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-9410: ----------------------------------- Patch applied to see if this helps w/ build workflow. Have also set VPE set to block when BOTH upstream and downstream are building, and JSF to block when upstream is building. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9410?page=com.atlassian.jira.plugin... ] Vlado Pakan closed JBIDE-9410. ------------------------------ Verified on Hudson -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira