Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Unable to satisfy dependency error
Sometimes that error is a red herring -- a misleading error message that's reported AFTER the actual problem in the log. Look higher up in the log for the REAL problem.
If there is no other error logged, you might try mirroring the Eclipse Indigo or Juno site, then strip out the offending IUs & regenerating the metadata. We did that for JBoss Tools and it's worked pretty well.
Here are two ant scripts you can call from Eclipse (or via commandline) to mirror, clean, and regen the site, then use that in your builds. 

http://download.jboss.org/jbosstools/updates/requirements/indigo/build.xml
http://download.jboss.org/jbosstools/updates/requirements/juno/build.xml

HTH,

Nick

On 12/06/2012 05:31 PM, Alex Kravets wrote:

Hello,

During install I get the following error:

Unable to satisfy dependency from org.eclipse.jdt.core
3.7.0.v_OTDT_r200_201106070730 to
org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).",
"Unable to satisfy dependency from org.eclipse.jdt.core
3.7.1.v_OTDT_r201_201109101025 to
org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).",
"Unable to satisfy dependency from org.eclipse.jdt.core
3.7.3.v_OTDT_r202_201202051448 to
org.eclipse.objectteams.otdt.core.patch.feature.group [2.0.0,3.0.0).",
"No solution found because the problem is unsatisfiable."]

I read different threads about this error, and tried suggested
approaches, but still error occurs. I tried adding requirements for
dependency resolution:

<dependency-resolution>
	<extraRequirements>
		<requirement>
			<type>p2-installable-unit</type>
			<id>org.eclipse.jdt.feature.group</id>
			<versionRange>0.0.0</versionRange>
		</requirement>
	</extraRequirements>
</dependency-resolution>

but that didn't seem to do anything. In my target definition I see
that o.e.jdt.core is not org.eclipse.jdt.core
3.7.0.v_OTDT_r200_201106070730, so I am not sure why this version is
being considered. Unless I am failing to use binding of target
definition between target pom and parent pom correctly.

Can anyone suggest what is the solution for this error?

The are my parent pom: http://pastebin.com/FTMWBxKY and target
definition pom: http://pastebin.com/znQijxLz

Thanks,
Alex
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user



--
Nick Boldt :: http://nick.divbyzero.com

Back to the top