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

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

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

Mon, 13 March 2017 15:51

Eclipse User

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.

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

Tue, 14 March 2017 02:30

Eclipse User

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.

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

Tue, 14 March 2017 08:32

Eclipse User

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.

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

Wed, 25 October 2017 11:21

Eclipse User

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

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

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Nov 09 03:02:24 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter