Eclipse Community Forums: EMF » [Oomph] migrating target definition file (.target) into targlets

Home » Modeling » EMF » [Oomph] migrating target definition file (.target) into targlets

[Oomph] migrating target definition file (.target) into targlets [message #1473328]

Fri, 14 November 2014 09:30

Eclipse User

Hi there,

what is the best way to migrate my actual target definition file to an oomph targlets setup?

My TD resolves perfectly. Then, I simply copied all repositories and units into targlets. Now i get a lot of "Cannot satisfy dependency" errors. I thought to start building unit by unit from scratch... without success. There are some features which will not resolve properly.

Here's the error:

ERROR: org.eclipse.equinox.p2.director code=0 Software being installed: artificial_root 1.0.0.v1415974948309
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root 1.0.0.v1415974948309
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.emf.ecp.emfforms.sdk.feature.feature.group 0.0.0
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root 1.0.0.v1415974948309
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.rap.sdk.feature.feature.group 0.0.0
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: EMF Forms IDE Tooling 1.4.0.20140916-1322 (org.eclipse.emf.ecp.emfforms.idetooling.feature.feature.group 1.4.0.20140916-1322)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.emf.ecp.makeithappen.wizards [1.4.0.20140916-1322]
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: EMF Forms IDE Tooling 1.4.1.20141006-1346 (org.eclipse.emf.ecp.emfforms.idetooling.feature.feature.group 1.4.1.20141006-1346)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.emf.ecp.makeithappen.wizards [1.4.1.20141006-1346]
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: EMF Forms SDK 1.3.0.20140610-1606 (org.eclipse.emf.ecp.emfforms.sdk.feature.feature.group 1.3.0.20140610-1606)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.emf.ecp.view.template.helper.feature.feature.group [1.3.0.20140610-1606]
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: EMF Forms SDK 1.4.0.20140916-1322 (org.eclipse.emf.ecp.emfforms.sdk.feature.feature.group 1.4.0.20140916-1322)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.emf.ecp.emfforms.idetooling.feature.feature.group [1.4.0.20140916-1322]
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: EMF Forms SDK 1.4.1.20141006-1346 (org.eclipse.emf.ecp.emfforms.sdk.feature.feature.group 1.4.1.20141006-1346)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.emf.ecp.emfforms.idetooling.feature.feature.group [1.4.1.20141006-1346]
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: Make It Happen Examples 1.4.0.20140916-1322 (org.eclipse.emf.ecp.makeithappen.wizards 1.4.0.20140916-1322)
    ERROR: org.eclipse.equinox.p2.director code=0 To: bundle org.eclipse.swt [3.100.0,4.0.0)
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: Make It Happen Examples 1.4.1.20141006-1346 (org.eclipse.emf.ecp.makeithappen.wizards 1.4.1.20141006-1346)
    ERROR: org.eclipse.equinox.p2.director code=0 To: bundle org.eclipse.swt [3.100.0,4.0.0)
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: Template Controls SWT 1.3.0.20140610-1606 (org.eclipse.emf.ecp.view.template.controls.swt 1.3.0.20140610-1606)
    ERROR: org.eclipse.equinox.p2.director code=0 To: bundle org.eclipse.jface.databinding [1.4.0,2.0.0)
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: EMF Forms Template Model Controls 1.3.0.20140610-1606 (org.eclipse.emf.ecp.view.template.helper.feature.feature.group 1.3.0.20140610-1606)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.emf.ecp.view.template.controls.swt [1.3.0.20140610-1606]
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: RAP SDK 2.3.0.20140610-0925 (org.eclipse.rap.sdk.feature.feature.group 2.3.0.20140610-0925)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.jface.databinding 0.0.0
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: RAP SDK 2.3.0.20140610-0925 (org.eclipse.rap.sdk.feature.feature.group 2.3.0.20140610-0925)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.swt 0.0.0
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: RAP SDK 2.3.1.20140909-1638 (org.eclipse.rap.sdk.feature.feature.group 2.3.1.20140909-1638)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.jface.databinding 0.0.0
  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
    ERROR: org.eclipse.equinox.p2.director code=0 From: RAP SDK 2.3.1.20140909-1638 (org.eclipse.rap.sdk.feature.feature.group 2.3.1.20140909-1638)
    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.swt 0.0.0

Any ideas?

Re: [Oomph] migrating target definition file (.target) into targlets [message #1473418 is a reply to message #1473328]

Fri, 14 November 2014 11:05

Eclipse User

Phil,

I guess you meant to post this to the Oomph forum.

On 14/11/2014 3:30 PM, Phil Wim wrote:
> Hi there,
>
> what is the best way to migrate my actual target definition file to an
> oomph targlets setup?
>
> My TD resolves perfectly. Then, I simply copied all repositories and
> units into targlets.
Start small and start with things that have the fewest dependencies.

Eike recently added a Repository Explorer view and context actions on
Repository to open them in the explorer. There you can find what IUs
are in the repo and ensure you're picking sensible ones (and use drag
and drop or copy and paste into your targlet task).

> Now i get a lot of "Cannot satisfy dependency" errors. I thought to
> start building unit by unit from scratch... without success. There are
> some features which will not resolve properly.
> Here's the error:
> ERROR: org.eclipse.equinox.p2.director code=0 Software being
> installed: artificial_root 1.0.0.v1415974948309
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root
> 1.0.0.v1415974948309
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.emf.ecp.emfforms.sdk.feature.feature.group 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root
> 1.0.0.v1415974948309
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.rap.sdk.feature.feature.group 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: EMF Forms IDE
> Tooling 1.4.0.20140916-1322
> (org.eclipse.emf.ecp.emfforms.idetooling.feature.feature.group
> 1.4.0.20140916-1322)
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.emf.ecp.makeithappen.wizards [1.4.0.20140916-1322]
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: EMF Forms IDE
> Tooling 1.4.1.20141006-1346
> (org.eclipse.emf.ecp.emfforms.idetooling.feature.feature.group
> 1.4.1.20141006-1346)
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.emf.ecp.makeithappen.wizards [1.4.1.20141006-1346]
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: EMF Forms SDK
> 1.3.0.20140610-1606
> (org.eclipse.emf.ecp.emfforms.sdk.feature.feature.group
> 1.3.0.20140610-1606)
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.emf.ecp.view.template.helper.feature.feature.group
> [1.3.0.20140610-1606]
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: EMF Forms SDK
> 1.4.0.20140916-1322
> (org.eclipse.emf.ecp.emfforms.sdk.feature.feature.group
> 1.4.0.20140916-1322)
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.emf.ecp.emfforms.idetooling.feature.feature.group
> [1.4.0.20140916-1322]
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: EMF Forms SDK
> 1.4.1.20141006-1346
> (org.eclipse.emf.ecp.emfforms.sdk.feature.feature.group
> 1.4.1.20141006-1346)
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.emf.ecp.emfforms.idetooling.feature.feature.group
> [1.4.1.20141006-1346]
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: Make It Happen
> Examples 1.4.0.20140916-1322 (org.eclipse.emf.ecp.makeithappen.wizards
> 1.4.0.20140916-1322)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.swt [3.100.0,4.0.0)
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: Make It Happen
> Examples 1.4.1.20141006-1346 (org.eclipse.emf.ecp.makeithappen.wizards
> 1.4.1.20141006-1346)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.swt [3.100.0,4.0.0)
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: Template
> Controls SWT 1.3.0.20140610-1606
> (org.eclipse.emf.ecp.view.template.controls.swt 1.3.0.20140610-1606)
> ERROR: org.eclipse.equinox.p2.director code=0 To: bundle
> org.eclipse.jface.databinding [1.4.0,2.0.0)
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: EMF Forms
> Template Model Controls 1.3.0.20140610-1606
> (org.eclipse.emf.ecp.view.template.helper.feature.feature.group
> 1.3.0.20140610-1606)
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.emf.ecp.view.template.controls.swt [1.3.0.20140610-1606]
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP SDK
> 2.3.0.20140610-0925 (org.eclipse.rap.sdk.feature.feature.group
> 2.3.0.20140610-0925)
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.jface.databinding 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP SDK
> 2.3.0.20140610-0925 (org.eclipse.rap.sdk.feature.feature.group
> 2.3.0.20140610-0925)
> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.swt
> 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP SDK
> 2.3.1.20140909-1638 (org.eclipse.rap.sdk.feature.feature.group
> 2.3.1.20140909-1638)
> ERROR: org.eclipse.equinox.p2.director code=0 To:
> org.eclipse.jface.databinding 0.0.0
> ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:
> ERROR: org.eclipse.equinox.p2.director code=0 From: RAP SDK
> 2.3.1.20140909-1638 (org.eclipse.rap.sdk.feature.feature.group
> 2.3.1.20140909-1638)
> ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.swt
> 0.0.0
>
> Any ideas?
>

Re: [Oomph] migrating target definition file (.target) into targlets [message #1473477 is a reply to message #1473418]

Fri, 14 November 2014 12:10

Eclipse User

Ed,

of course! Next time in Oomph section. I relied on a different post which was written here some time ago. Tooo lazy Smile

I totally like the Oomph approach. I can see the big picture. Actually i was waiting for such an approach. Thanks for pointing me out - in a different post!!

I did not know about the explorer. This was the missing peace. Now working with targets makes fun ... THX!!!

Phil

Re: [Oomph] migrating target definition file (.target) into targlets [message #1473575 is a reply to message #1473477]

Fri, 14 November 2014 14:06

Eclipse User

Am 14.11.2014 um 18:10 schrieb Phil Wim:
> Ed,
>
> of course! Next time in Oomph section. I relied on a different post which was written here some time ago. Tooo lazy :)
>
> I totally like the Oomph approach. I can see the big picture. Actually i was waiting for such an approach. Thanks for
> pointing me out - in a different post!!
>
> I did not know about the explorer. This was the missing peace. Now working with targets makes fun ... THX!!!
Peace! :P

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Previous Topic:	[CDO] Installation and Setup instructions
Next Topic:	MissingResourceException for own messages in the validator

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Aug 30 16:20:03 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter