| setup with git clone and project import of non-Eclipse project [message #1750221] |
Sun, 18 December 2016 23:51  |
 Hallvard Traetteberg
Messages: 673
Registered: July 2009
Location: Trondheim, Norway |
Senior Member |
|
|
Hi,
I'm using Eclipse in a large programming course using java, and the installation they are supposed to use includes e(fx)clipse and some custom features I've made. In addition, they need to create a standard java project with an extra library jar in the class path. Later they need to download and import junit tests for the exercises.
In previous years I've made a detailed setup guide explaining which Eclipse variant to download and install, how to add the necessary additional plugins and then configure the java project, but this year I thought I'd use Oomph to 1) install the custom Eclipse and 2) clone a git repo and import a pre-configured java project.
It was pretty easy to create a product setup file including the necessary features, but I have problems with the project setup file. The symptom is that nothing seems to happen after the new eclipse instance has started up. The workspace is empty, while I thought that the git clone and project import tasks would be triggered automatically, so the workspace would contain all the projects in the newly clones git repo.
Currently, the project setup (also attached) just includes a stream node with a git clone task and a project import task. The git clone task uses ${user.home/git} as git clone location and a github repo of mine as the URI. The project import has a source locator that refers to the newly cloned repo using ${tdt4100.clone.location} where tdt4100.clone is the id of the clone task.
So, what haven't I understood correctly?
|
|
|
|
|
|
|
| Re: setup with git clone and project import of non-Eclipse project [message #1750262 is a reply to message #1750250] |
Mon, 19 December 2016 11:28  |
Ed Merks
Messages: 33264
Registered: July 2009 |
Senior Member |
|
|
Our product catalogs include this task at the root of the catalog so all product versions will include the Oomph setup feature.
<?xml version="1.0" encoding="UTF-8"?>
<setup.p2:P2Task
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:setup.p2="http://www.eclipse.org/oomph/setup/p2/1.0">
<requirement
name="org.eclipse.oomph.setup.feature.group"/>
<repository
url="${oomph.update.url}"/>
</setup.p2:P2Task>
It's not necessary for a product to include any Oomph features, but of course if you want your product to have the setup feature, you must define it that way...
We generally leave the location empty and then the attribute rules for where to locate it are used which choices such as these:
${installation.location/git/}${@id.remoteURI|gitRepository}
${workspace.location/.git/}${@id.remoteURI|gitRepository}
The later locates the clone in the workspace...
When we prepare an Oomph tutorial, we of course have an Oomph setup for setting up the tutorial environment. And do all kinds of tricks to ensure that the tutorial will work without internet access. I.e., we mirror various repos and create local clones and use redirections to ensure these locally distributed things are used for the tutorial environment.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03961 seconds
] 
Search
Help
Register
Login
Home
