|
Re: Error "Dependency X is defined more then once in component Y" should not occur [message #383586 is a reply to message #383584] |
Sun, 29 March 2009 07:57 |
|
Hi Scott,
Buckminster had a bug earlier that caused this behavior. It was changed
so that no exception would be thrown unless the dependencies had
conflicting version ranges (i.e. ranges that does not intersect).
I can successfully resolve org.eclipse.emf.sdk. Both from their CVS and
from the galileo update and both with the 3.4.x and 3.5.x releases of
Buckminster. What Buckminster version are you using and from where do
you attempt the resolution?
Regards,
Thomas Hallgren
Scott Hendrickson wrote:
> I'd like to import org.eclipse.emf.sdk as an eclipse.feature. However, the
> feature apparently depends on org.eclipse.emf multiple times, which causes
> an error. I'm not sure why this is an error. It seems like this should be
> okay. DEBUG output includes:
>
> ERROR [0002] : Resolution attempt ended with exception: Dependency
> org.eclipse.emf is defined more then once in component org.eclipse.emf.sdk
>
> -- Scott
>
> P.S. it should be "than" not "then"
>
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03164 seconds