Eclipse Community Forums: Oomph » Using Oomph to activate a regular target platform (not a Target

Help

Home

Home » Eclipse Projects » Oomph » Using Oomph to activate a regular target platform (not a Target

Show: Today's Messages :: Show Polls :: Message Navigator

Using Oomph to activate a regular target platform (not a Target [message #1816149]

Tue, 22 October 2019 14:50

Lars Vogel

Messages: 1094
Registered: July 2009

Senior Member

I would like to update https://raw.githubusercontent.com/eclipse/dartboard/master/org.eclipse.dartboard.releng/Dartboard.setup kindly provided by Ed to use the target definition file directly after the installation instead of using the "Modular Target" from Oomph.

What I did was adding a "Target Platform" entry below the Modular Target and used "target-platform-latest.target" (the name of the target) and get activate to true.

The activate flag seems to be the default, as it does not show up in the XML

<setupTask
xsi:type="pde:TargetPlatformTask"
id=""
name="target-platform-latest.target"/>

See screenshot.

If I run this updated project task, the target-platform-latest.target is not activated.

What do I do wrong?

Attachment: dartboard-setup.png
(Size: 90.85KB, Downloaded 3 times)

Report message to a moderator

Re: Using Oomph to activate a regular target platform (not a Target [message #1816154 is a reply to message #1816149]

Tue, 22 October 2019 16:47

Eike Stepper

Messages: 6476
Registered: July 2009

Senior Member

The name attribute must specify the name of the target definition, not the full name of the .target file:

<setupTask
   xsi:type="pde:TargetPlatformTask"
   id=""
   name="target-platform-latest"/>

Out of curiosity, what was wrong with the Targlet Task?

Cheers
/Eike

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

Report message to a moderator

Re: Using Oomph to activate a regular target platform (not a Target [message #1816163 is a reply to message #1816154]

Tue, 22 October 2019 21:12

Lars Vogel

Messages: 1094
Registered: July 2009

Senior Member

Thanks Eike, but using the target file without extension did not do the trick.

<setupTask
xsi:type="pde:TargetPlatformTask"
name="target-platform-latest"/>

I attached the setup file, in case you can have a look at it to see my error.

>Out of curiosity, what was wrong with the Targlet Task?

Nothing, I just wanted to start with something we already have. At a later point I plan to generate the target file via Oomph based on the Targlet.

Attachment: Dartboard.setup
(Size: 8.23KB, Downloaded 17 times)

Report message to a moderator

Re: Using Oomph to activate a regular target platform (not a Target [message #1816230 is a reply to message #1816163]

Thu, 24 October 2019 13:49

Eike Stepper

Messages: 6476
Registered: July 2009

Senior Member

It seems you have no task to import the projects (in particular the one that contains the .target file) from the Git clone into the workspace. So PDE can't find the target definition. The Modular Target (Targlet) task would have done that for you. You can also use a task like this:

<?xml version="1.0" encoding="UTF-8"?>
<projects:ProjectsImportTask
    xmi:version="2.0"
    xmlns:xmi="http://www.omg.org/XMI"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:predicates="http://www.eclipse.org/oomph/predicates/1.0"
    xmlns:projects="http://www.eclipse.org/oomph/setup/projects/1.0"
    xsi:schemaLocation="http://www.eclipse.org/oomph/predicates/1.0 http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/models/Predicates.ecore http://www.eclipse.org/oomph/setup/projects/1.0 http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/models/Projects.ecore">
  <sourceLocator
      rootFolder="${git.clone.dartboard.location}"
      locateNestedProjects="true">
    <predicate
        xsi:type="predicates:NotPredicate">
      <operand
          xsi:type="predicates:NamePredicate"
          pattern="dartboard"/>
    </predicate>
  </sourceLocator>
</projects:ProjectsImportTask>

Cheers
/Eike

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

Report message to a moderator

Re: Using Oomph to activate a regular target platform (not a Target [message #1816433 is a reply to message #1816230]

Tue, 29 October 2019 13:25

Lars Vogel

Messages: 1094
Registered: July 2009

Senior Member

Thanks, Eike. I'm having problems testing changes in project setup files, I open a new thread for this.

Report message to a moderator

Re: Using Oomph to activate a regular target platform (not a Target [message #1816509 is a reply to message #1816433]

Wed, 30 October 2019 10:07

Lars Vogel

Messages: 1094
Registered: July 2009

Senior Member

Thanks Eike, import of project now works and I'm able to test that to the help of Ed and you.

Also activation of the target platform works fine. Thank you for your help.

Attachment: Dartboard.setup
(Size: 7.66KB, Downloaded 10 times)

Report message to a moderator

Re: Using Oomph to activate a regular target platform (not a Target [message #1816515 is a reply to message #1816509]

Wed, 30 October 2019 11:26

Ed Merks

Messages: 30883
Registered: July 2009

Senior Member

I would not use a target platform task if at all avoidable (and it's always avoidable). There are only downsides at development time:

https://wiki.eclipse.org/Oomph_Targlets

It's bloated (copies yet another copy of everything into the workspace metadata), it's slow (downloads everything you already have downloaded before), it's redundant (duplicates information already in your bundle/feature requirements), it's not resilient (destroys your current target platform if there is a network failure or a resolution failure,) it's not composeable (so your project cannot work with any other project), and of course the target editor is not a joy to use (believing it's necessary to resolve and download everything while editing). I cringe every time I accidentally open it to view the generated .target file...

Report message to a moderator