Eclipse Community Forums: Oomph » API Baseline and and Targets in Project setup

Help

Home

Home » Eclipse Projects » Oomph » API Baseline and and Targets in Project setup

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

API Baseline and and Targets in Project setup [message #1756203]

Mon, 13 March 2017 19:51

Velizar Nenov

Messages: 13
Registered: July 2016

Junior Member

Hello,

Could you please provide a real life example of Project setup file with Api baseline and Target/s. I'm trying to find how to improve my project setups.

Thank you in advance.

Report message to a moderator

Re: API Baseline and and Targets in Project setup [message #1756214 is a reply to message #1756203]

Tue, 14 March 2017 06:30

Ed Merks

Messages: 33137
Registered: July 2009

Senior Member

You can always browse through all the existing project setups in the catalog. In any setup editor (use Navigate -> Open Setup -> ... to open one even if you don't have a *.setup file) you can use the use the "Show all resources" toolbar button to show all the resources in the resource set. This will include index:/org.eclipse.setup and that is the Index resource that contains every catalog, including the Eclipse and Github project catalogs. There you can look at how other projects have defined their setups.

Ed Merks
Professional Support: https://www.macromodeling.com/

Report message to a moderator

Re: API Baseline and and Targets in Project setup [message #1756240 is a reply to message #1756214]

Tue, 14 March 2017 12:32

Abel Hegedus

Messages: 197
Registered: September 2015

Senior Member

The VIATRA setup contains API Baseline configuration ( https://git.eclipse.org/c/viatra/org.eclipse.viatra.git/tree/releng/org.eclipse.viatra.setup/VIATRAEMF.setup#n997 ) and also Modular Targlets to define the target platform.

If you mean using .target files, I have not used that part, but I saw it used in the Tycho project setup. I seem to remember that the task name must match the name of the target definition for this to work.

Report message to a moderator

Re: API Baseline and and Targets in Project setup [message #1775166 is a reply to message #1756240]

Wed, 25 October 2017 15:21

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

Hi

Add a "New Child" "API Baseline" to a Stream.

"Remote URI" is important. It is what is read. Set it to a zipped repo of the baseline such as "http://download.eclipse.org/mmt/qvto/downloads/drops/3.7.0/R201706041316/mmt-qvto-Update-3.7.0.zip". On no account use the mirror syntax such as "https://www.eclipse.org/downloads/download.php?file=/mmt/qvto/downloads/drops/3.7.0/R201706041316/mmt-qvto-Update-3.7.0.zip" which will give you a bad \remoteURI,txt stack trace.

The "Location" is also important. It is what is written/cached. Set it to e.g. "${installation.location}/api/v3.7/" to unzip "mmt-qvto-Update-3.7.0.zip" to "api/v3.7/" in your installation.

"Description", "Name" and "Version"" are cosmetic. They can make the tree editor rendering more helpful.

Regards

Ed Willink

Report message to a moderator

Previous Topic:	Eclipse Docker plugin error while building source code
Next Topic:	Targlet's Source Locator

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 19:46:09 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter