<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I sent PR with changes that works for
me
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://github.com/jbosstools/jbosstools-build/pull/130">https://github.com/jbosstools/jbosstools-build/pull/130</a><br>
<br>
Denis<br>
<br>
<br>
On 12/02/2013 01:50 PM, Alexey Kazakov wrote:<br>
</div>
<blockquote cite="mid:529D0090.100@exadel.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">I got the following error when added
org.eclipse.osgi.compatibility.state as a dependency:<br>
<br>
[ERROR] Cannot resolve project dependencies:<br>
[ERROR] Software being installed:
org.jboss.tools.common.all.test.feature.source.feature.group
3.6.0.qualifier<br>
[ERROR] Missing requirement:
org.jboss.tools.common.model.ui.test 3.6.0.qualifier requires
'bundle org.eclipse.osgi.compatibility.state.source 0.0.0' but
it could not be found<br>
[ERROR] Cannot satisfy dependency:
org.jboss.tools.common.all.test.feature.feature.group
3.6.0.qualifier depends on: org.jboss.tools.common.model.ui.test
0.0.0<br>
[ERROR] Cannot satisfy dependency:
org.jboss.tools.common.all.test.feature.source.feature.group
3.6.0.qualifier depends on:
org.jboss.tools.common.all.test.feature.feature.group
[3.6.0,3.6.1)<br>
[ERROR] <br>
[ERROR] Internal error: java.lang.RuntimeException: No solution
found because the problem is unsatisfiable.: [Unable to satisfy
dependency from org.jboss.tools.common.model.ui.test
3.6.0.qualifier to bundle
org.eclipse.osgi.compatibility.state.source 0.0.0.; No solution
found because the problem is unsatisfiable.] -> [Help 1]<br>
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.common.model.ui.test 3.6.0.qualifier to bundle
org.eclipse.osgi.compatibility.state.source 0.0.0.; No solution
found because the problem is unsatisfiable.]<br>
at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)<br>
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)<br>
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)<br>
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)<br>
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)<br>
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)<br>
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)<br>
at java.lang.reflect.Method.invoke(Method.java:606)<br>
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)<br>
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)<br>
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)<br>
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)<br>
Caused by: java.lang.RuntimeException: No solution found because
the problem is unsatisfiable.: [Unable to satisfy dependency
from org.jboss.tools.common.model.ui.test 3.6.0.qualifier to
bundle org.eclipse.osgi.compatibility.state.source 0.0.0.; No
solution found because the problem is unsatisfiable.]<br>
at
org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:98)<br>
at
org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:88)<br>
at
org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63)<br>
at
org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:134)<br>
at
org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:87)<br>
at
org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:369)<br>
at
org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:345)<br>
at
org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:109)<br>
at
org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75)<br>
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274)<br>
at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)<br>
... 11 more<br>
<br>
<br>
On 11/29/2013 10:10 AM, Mickael Istria wrote:<br>
</div>
<blockquote cite="mid:5298D889.8010606@redhat.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hi all,<br>
<br>
As part of Luna came a change that we've not correctly
estimated: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://wiki.eclipse.org/Equinox/Luna_Framework#Removal_of_the_PlatformAdmin_Service_Implementation">http://wiki.eclipse.org/Equinox/Luna_Framework#Removal_of_the_PlatformAdmin_Service_Implementation</a>
. This cause some parts of Eclipse to be failing with surefire
as they depend on a class which is not available in default
Equinox bundles any more. The TEMPORARY workaround is to add a
dependency to your tycho-surefire-plugin to fragment
org.eclipse.osgi.compatibility.state.<br>
So in case of failing test, try to add the fragment locally, and
if it works better, open a bug to keep track of that change
(make me a dep of JBIDE-16161). This should be fine for JBT
4.2.0.Alpha1 build and tests against Luna M3.<br>
<br>
Then by Luna M4, this should happen: <a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=417429">https://bugs.eclipse.org/bugs/show_bug.cgi?id=417429</a>
, and hopefully, it will remove most of our dependencies on this
somehow deprecated PlatfromAdmin service. We'll be able to get
rid of the additional dependency on surefire, and everything
will be fine.<br>
<br>
In case you have a message in your tycho-surefire-plugin saying
"Could not acquire PlatformAdmin", you can safely ignore it <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=417429">https://bugs.eclipse.org/bugs/show_bug.cgi?id=417429</a>
. It's just a warning. What's important is whether your tests do
work or not, and if not, whether adding the fragment helps.<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a moz-do-not-send="true"
href="http://www.jboss.org/tools">JBoss, by Red Hat</a><br>
<a moz-do-not-send="true"
href="http://mickaelistria.wordpress.com">My blog</a> - <a
moz-do-not-send="true"
href="http://twitter.com/mickaelistria">My Tweets</a></div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jbosstools-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jbosstools-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></pre>
</blockquote>
<br>
</body>
</html>