[jbosstools-issues] [JBoss JIRA] (JBIDE-13594) org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core

[Denis Golovin (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757017#comment-12757017 ] 

Denis Golovin edited comment on JBIDE-13594 at 2/26/13 6:16 PM:
----------------------------------------------------------------

You are mixing modules and sub-components in your comment. On picture above I show only modules (read - git repositories). Integration-stack/aggregated-site *subcomponent* which adds esb dependency to integration-stack module. At the same time esb requires integration-stack/target-platform *sub-component* to be built which adds integration-stack dependency to esb.

So there is a cycle between modules.
                
      was (Author: dgolovin):
    You are mixing modules and sub-components in your comment. On picture above I show only modules (read - git repositories). Integration-stack/aggregated-site *subcomponent* which adds esb dependency to integration-stack module. At the same time esb requires integration-stack/target-platform *sub-component* to be built which adds integration-stack dependency to esb.

So there is cycle between modules.
                  
> org.jboss.tools.esb.project.ui cannot be build due to missing org.eclipse.zest.core
> -----------------------------------------------------------------------------------
>
>                 Key: JBIDE-13594
>                 URL: https://issues.jboss.org/browse/JBIDE-13594
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, esb, testing
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Martin Malina
>            Assignee: Nick Boldt
>             Fix For: 4.1.0.Alpha2
>
>         Attachments: dependencies.png
>
>
> jbosstools integration tests job in jenkins is currently blocked because of unsatisfied dependency:
> {code}
> 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)
> {code}
> 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.

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