]
Martin Malina updated JBIDE-13704:
----------------------------------
Affects Version/s: 4.0.1.Final
Cannot build integration-tests from branch 4.0.x
------------------------------------------------
Key: JBIDE-13704
URL:
https://issues.jboss.org/browse/JBIDE-13704
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: QA
Affects Versions: 4.0.1.Final
Reporter: Tomas Remes
Assignee: Martin Malina
Running mvn clean install -DskipTests on the clean repo, I got:
{noformat}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.jboss.ide.eclipse.as.ui.bot.test 4.0.0.qualifier
[ERROR] Missing requirement: org.jboss.tools.ui.bot.ext 4.0.0.qualifier requires
'bundle org.eclipse.zest.core 1.2.0' but it could not be found
[ERROR] Cannot satisfy dependency: org.jboss.ide.eclipse.as.ui.bot.test 4.0.0.qualifier
depends on: bundle org.jboss.tools.ui.bot.ext 1.0.0
[ERROR]
[ERROR] Internal error: java.lang.RuntimeException: "No solution found because the
problem is unsatisfiable.": ["Unable to satisfy dependency from
org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.core 1.2.0.",
"Unable to satisfy dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to
bundle org.eclipse.zest.layouts 1.1.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.ui.bot.ext 4.0.0.qualifier to bundle
org.eclipse.zest.core 1.2.0.", "Unable to satisfy dependency from
org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle org.eclipse.zest.layouts
1.1.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)
Caused by: java.lang.RuntimeException: "No solution found because the problem is
unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.ui.bot.ext
4.0.0.qualifier to bundle org.eclipse.zest.core 1.2.0.", "Unable to satisfy
dependency from org.jboss.tools.ui.bot.ext 4.0.0.qualifier to bundle
org.eclipse.zest.layouts 1.1.0.", "No solution found because the problem is
unsatisfiable."]
at
org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:77)
at
org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:89)
at
org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:122)
at
org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveProject(P2ResolverImpl.java:80)
at
org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:377)
at
org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:354)
at
org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:103)
at
org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:82)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
... 11 more
{noformat}
--
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: