Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-13594

org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.1.0.Alpha2
    • 4.1.0.Alpha1
    • arquillian, build, esb
    • None

      jbosstools integration tests job in jenkins is currently blocked because of unsatisfied dependency:

      Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.layouts 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130128-1848-B1149 to bundle org.eclipse.zest.layouts 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.Alpha1-v20130215-0533-B1152 to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."]
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)

      See https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Trunk/job/jbosstools-integration-tests.aggregate_master/48/consoleText

      This happens because zest has been removed from the core target platform into JBTIS target platform as described in JBIDE-13435.

      I originally thought this needs to be fixed by the esb compoment owner, but after learning that zest is now in JBTIS target platform, what actually seems needs to be done is use the JBTIS target platform for the job.

      Or disregard this JIRA and split the integration tests and soa integration tests sites/jobs as suggested in JBIDE-12974.

        1. dependencies.png
          dependencies.png
          4 kB

          1.
          		 integration-tests should use JBTIS target platform to resolve SOA-related requirements like Zest Sub-task Closed Major Martin Malina

              nickboldt Nick Boldt
              exd-mmalina Martin Malina
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: