Home » Eclipse Projects » Oomph » Project import via project catalog
|
| Re: Project import via project catalog [message #1702891 is a reply to message #1702883] |
Mon, 27 July 2015 09:16   |
 Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Matthias,
Comments below.
On 27/07/2015 10:28 AM, Matthias Nicklisch wrote:
> Hello there,
>
> I am still working on my setup environment. Finally, I was able to
> deploy my setups to git and access them in my installer.
>
> There is just something strange.
>
> When I don't redirect my installer to my git repository to use my own
> catalogs and add the setup file for my project manually to my
> installer, everything works fine.
So you mean dragging it to your <user> extension of the existing catalog
works fine. Why do you need your own catalog? It's no so easy to create
your own catalog (because it's easy to miss some of the important things
in the catalogs we provide).
> If I redirect my installer to use the same files from git (they are of
> course synchronized and absolutely the same) my git projects aren't
> imported anymore.
What exactly are you redirecting? Why do you need to do anything?
> The other tasks in this setup seem to work fine. The preferences are
> set, the plugins are installed, but no git repositories, projects or
> working sets. I don't receive an error message, from the point of view
> of the installer everything worked out fine, but there is something
> missing.
It's hard to speculate without knowing something about what you've done
with the redirection and what your own catalog looks like.
>
> Do you have an idea what could be the problem here?
Not yet.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Project import via project catalog [message #1702897 is a reply to message #1702891] |
Mon, 27 July 2015 09:51 |
Matthias Nicklisch
Messages: 20
Registered: July 2015 |
Junior Member |
|
|
Regarding the question about why am I doing this:
Maybe you've seen my first post here. We want to try Oomph in our company and want to setup an environment. We already have a lot of standards on how to setup our Eclipse environments and want to support and simplify that process for our developers. What I am doing here is a proof of concept. Our goal is to have a standard environment in our git repository, so that we can define our setups there and everyone can access those setups and keep our developers IDEs on one defined standard. As far as I could see it, Oomph is exactly for that purpose. Later we want to define setups for our projects to provide a standardized environment for all developers who are working on one project.
What I have done so far is, I have setup a product catalog which provides some standard Eclipse products we need in our company, I have simply copied the product entries from the standard eclipse catalog (http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/)
My catalog looks something like this:
NOTE: I've edited some names in the files to ensure privacy for my company. But only Labels and parts of the URL which would shows my company or would directly link to our repositories. I just wanna be safe here =)
<?xml version="1.0" encoding="UTF-8"?>
<setup:ProductCatalog
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
xmlns:setup.p2="http://www.eclipse.org/oomph/setup/p2/1.0"
name="org.eclipse.products"
label="mycompany">
<setupTask
xsi:type="setup:InstallationTask"
id="installation"/>
<setupTask
xsi:type="setup.p2:P2Task">
<requirement
name="org.eclipse.oomph.setup.feature.group"/>
<repository
url="${oomph.update.url}"/>
<repository
url="http://download.eclipse.org/modeling/emf/emf/updates/2.10/core/R201405190339"/>
</setupTask>
<setupTask
xsi:type="setup:EclipseIniTask"
option="-Doomph.setup"
value="=true"
vm="true"/>
<product name="epp.package.standard"
label="Eclipse Standard">
<version
name="latest"
label="Latest (Luna)"
requiredJavaVersion="1.7">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse Standard (Luna)">
<requirement
name="epp.package.standard"
versionRange="[4.4.0,5.0.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.4.0,5.0.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.4.0,5.0.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.10.0,4.0.0)"/>
<requirement
name="org.eclipse.pde.feature.group"
versionRange="[3.10.0,4.0.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/luna"/>
<repository
url="http://download.eclipse.org/releases/luna/201502271000"/>
</setupTask>
</version>
<version
name="latest.released"
label="Latest Release (Luna)"
requiredJavaVersion="1.7">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse Standard (Luna)">
<requirement
name="epp.package.standard"
versionRange="[4.4.0,4.5.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.4.0,4.5.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.4.0,4.5.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.10.0,3.11.0)"/>
<requirement
name="org.eclipse.pde.feature.group"
versionRange="[3.10.0,3.11.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/luna"/>
<repository
url="http://download.eclipse.org/releases/luna/201502271000"/>
</setupTask>
</version>
<version
name="luna"
label="Luna"
requiredJavaVersion="1.7">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse Standard (Luna)">
<requirement
name="epp.package.standard"
versionRange="[4.4.0,4.5.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.4.0,4.5.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.4.0,4.5.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.10.0,3.11.0)"/>
<requirement
name="org.eclipse.pde.feature.group"
versionRange="[3.10.0,3.11.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/luna"/>
<repository
url="http://download.eclipse.org/releases/luna/201502271000"/>
</setupTask>
</version>
<version
name="kepler"
label="Kepler"
requiredJavaVersion="1.6">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse Standard (Kepler)">
<requirement
name="epp.package.standard"
versionRange="[2.0.0,2.1.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.3.0,4.4.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.3.0,4.4.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.9.0,3.10.0)"/>
<requirement
name="org.eclipse.pde.feature.group"
versionRange="[3.9.0,3.10.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/kepler"/>
<repository
url="http://download.eclipse.org/releases/kepler/201402280900"/>
<repository
url="http://download.eclipse.org/modeling/emf/emf/updates/2.10.x/core/S201501230452"/>
</setupTask>
</version>
<description>
Package suited for development of Eclipse itself at Eclipse.org; based on the Eclipse Platform adding PDE, Git, Marketplace Client, source code and developer documentation.<br/>
<br/>
Click <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform">here</a> to file a bug against Eclipse Platform.<br/>
Click <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EGit">here</a> to file a bug against Eclipse Git team provider.
</description>
</product>
<product name="epp.package.java"
label="Eclipse IDE for Java Developers">
<annotation
source="http://www.eclipse.org/oomph/setup/BrandingInfo">
<detail
key="imageURI">
<value>http://www.eclipse.org/downloads/images/java.png</value>
</detail>
</annotation>
<version
name="latest"
label="Latest (Mars)"
requiredJavaVersion="1.7">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse IDE for Java Developers (Mars)">
<requirement
name="epp.package.java"
versionRange="[4.5.0,5.0.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.5.0,5.0.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.5.0,5.0.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.11.0,4.0.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/mars/R"/>
<repository
url="http://download.eclipse.org/releases/mars/201506241002"/>
</setupTask>
</version>
<version
name="latest.released"
label="Latest Release (Mars)"
requiredJavaVersion="1.7">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse IDE for Java Developers (Mars)">
<requirement
name="epp.package.java"
versionRange="[4.5.0,4.6.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.5.0,4.6.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.5.0,4.6.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.11.0,3.12.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/mars/R"/>
<repository
url="http://download.eclipse.org/releases/mars/201506241002"/>
</setupTask>
</version>
<version
name="mars"
label="Mars"
requiredJavaVersion="1.7">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse IDE for Java Developers (Mars)">
<requirement
name="epp.package.java"
versionRange="[4.5.0,4.6.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.5.0,4.6.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.5.0,4.6.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.11.0,3.12.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/mars/R"/>
<repository
url="http://download.eclipse.org/releases/mars/201506241002"/>
</setupTask>
</version>
<version
name="luna"
label="Luna"
requiredJavaVersion="1.6">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse IDE for Java Developers (Luna)">
<requirement
name="epp.package.java"
versionRange="[4.4.0,4.5.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.4.0,4.5.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.4.0,4.5.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.10.0,3.11.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/luna"/>
<repository
url="http://download.eclipse.org/releases/luna/201502271000"/>
</setupTask>
</version>
<version
name="kepler"
label="Kepler"
requiredJavaVersion="1.6">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse IDE for Java Developers (Kepler)">
<requirement
name="epp.package.java"
versionRange="[2.0.0,2.1.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.3.0,4.4.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.3.0,4.4.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.9.0,3.10.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/kepler"/>
<repository
url="http://download.eclipse.org/releases/kepler/201402280900"/>
<repository
url="http://download.eclipse.org/modeling/emf/emf/updates/2.10.x/core/S201501230452"/>
</setupTask>
</version>
<version
name="juno"
label="Juno"
requiredJavaVersion="1.5">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse IDE for Java Developers (Juno)">
<requirement
name="epp.package.java"
versionRange="[1.5.0,1.6.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.2.0,4.3.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.2.0,4.3.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.8.0,3.9.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/juno"/>
<repository
url="http://download.eclipse.org/releases/juno/201303010900"/>
<repository
url="http://download.eclipse.org/modeling/emf/emf/updates/2.10.x/core/S201501230452"/>
</setupTask>
</version>
<description>The essential tools for any Java developer, including a Java IDE, a Git client, XML Editor, Mylyn, Maven integration and WindowBuilder</description>
</product>
<product name="epp.package.jee"
label="Eclipse IDE for Java EE Developers">
<annotation
source="http://www.eclipse.org/oomph/setup/BrandingInfo">
<detail
key="imageURI">
<value>http://www.eclipse.org/downloads/images/javaee.png</value>
</detail>
</annotation>
<version
name="latest"
label="Latest (Mars)"
requiredJavaVersion="1.7">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse IDE for Java EE Developers (Mars)">
<requirement
name="epp.package.jee"
versionRange="[4.5.0,5.0.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.5.0,5.0.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.5.0,5.0.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.11.0,4.0.0)"/>
<requirement
name="org.eclipse.pde.feature.group"
versionRange="[3.11.0,4.0.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/mars/R"/>
<repository
url="http://download.eclipse.org/releases/mars/201506241002"/>
</setupTask>
</version>
<version
name="latest.released"
label="Latest Release (Mars)"
requiredJavaVersion="1.7">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse IDE for Java EE Developers (Mars)">
<requirement
name="epp.package.jee"
versionRange="[4.5.0,4.6.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.5.0,4.6.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.5.0,4.6.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.11.0,3.12.0)"/>
<requirement
name="org.eclipse.pde.feature.group"
versionRange="[3.11.0,3.12.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/mars/R"/>
<repository
url="http://download.eclipse.org/releases/mars/201506241002"/>
</setupTask>
</version>
<version
name="mars"
label="Mars"
requiredJavaVersion="1.7">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse IDE for Java EE Developers (Mars)">
<requirement
name="epp.package.jee"
versionRange="[4.5.0,4.6.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.5.0,4.6.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.5.0,4.6.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.11.0,3.12.0)"/>
<requirement
name="org.eclipse.pde.feature.group"
versionRange="[3.11.0,3.12.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/mars/R"/>
<repository
url="http://download.eclipse.org/releases/mars/201506241002"/>
</setupTask>
</version>
<version
name="luna"
label="Luna"
requiredJavaVersion="1.6">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse IDE for Java EE Developers (Luna)">
<requirement
name="epp.package.jee"
versionRange="[4.4.0,4.5.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.4.0,4.5.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.4.0,4.5.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.10.0,3.11.0)"/>
<requirement
name="org.eclipse.pde.feature.group"
versionRange="[3.10.0,3.11.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/luna"/>
<repository
url="http://download.eclipse.org/releases/luna/201502271000"/>
</setupTask>
</version>
<version
name="kepler"
label="Kepler"
requiredJavaVersion="1.6">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse IDE for Java EE Developers (Kepler)">
<requirement
name="epp.package.jee"
versionRange="[2.0.0,2.1.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.3.0,4.4.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.3.0,4.4.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.9.0,3.10.0)"/>
<requirement
name="org.eclipse.pde.feature.group"
versionRange="[3.9.0,3.10.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/kepler"/>
<repository
url="http://download.eclipse.org/releases/kepler/201402280900"/>
<repository
url="http://download.eclipse.org/modeling/emf/emf/updates/2.10.x/core/S201501230452"/>
</setupTask>
</version>
<version
name="juno"
label="Juno"
requiredJavaVersion="1.5">
<setupTask
xsi:type="setup.p2:P2Task"
label="Eclipse IDE for Java EE Developers (Juno)">
<requirement
name="epp.package.jee"
versionRange="[1.5.0,1.6.0)"/>
<requirement
name="org.eclipse.platform.feature.group"
versionRange="[4.2.0,4.3.0)"/>
<requirement
name="org.eclipse.rcp.feature.group"
versionRange="[4.2.0,4.3.0)"/>
<requirement
name="org.eclipse.jdt.feature.group"
versionRange="[3.8.0,3.9.0)"/>
<requirement
name="org.eclipse.pde.feature.group"
versionRange="[3.8.0,3.9.0)"/>
<repository
url="http://download.eclipse.org/technology/epp/packages/juno"/>
<repository
url="http://download.eclipse.org/releases/juno/201303010900"/>
<repository
url="http://download.eclipse.org/modeling/emf/emf/updates/2.10.x/core/S201501230452"/>
</setupTask>
</version>
<description>Tools for Java developers creating Java EE and Web applications, including a Java IDE, tools for Java EE, JPA, JSF, Mylyn, EGit and others.</description>
</product>
</setup:ProductCatalog>
I have setup a org.eclipse.setup file in which I reference to my catalogs.
I also have setup a project catalog which looks something like this:
<?xml version="1.0" encoding="UTF-8"?>
<setup:ProjectCatalog
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
name="org.eclipse"
label="mycompany">
<setupTask
xsi:type="setup:ResourceCreationTask"
content="MAX_RECENT_WORKSPACES=5
RECENT_WORKSPACES=${workspace.location|property}
RECENT_WORKSPACES_PROTOCOL=3
SHOW_WORKSPACE_SELECTION_DIALOG=true
eclipse.preferences.version=1"
targetURL="configuration:/.settings/org.eclipse.ui.ide.prefs"/>
<project name="GitHubContainer"
label="My company Projects">
<project
href="https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/mycompany_Standard_Mars.setup#/"/>
</project>
<description></description>
</setup:ProjectCatalog>
Ok, now my problem.
Yes, it is like you've said, in my first approach I used the Eclipse installer in advanced mode, chose Java EE as my Standard Eclipse product and then added via drag&drop my setup file to the <user> extension.
That way, everything works fine and everything I have defined in my setup is processed properly.
Now, I wanted to try everything via our git repository, so I modified the eclipse-inst.ini in the directory of the eclipse installer and added this line:
-Doomph.redirection.setups=http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/->https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/master/setups/
This is what I meant with redirection to our catalogs.
So, when I use that, I can choose my product and also my project setup, everything fine to this point. Generally, my project setup is working fine. I have defined some variables for my installation (e.g. the workspace and installation location, they should be the same on every computer here) I have alos defined a lot of properties for our code style which we have imported before via an epf file. I have parsed every line in that file and added a preference setup task for each line. I also defined some plugins we want to have installed and some standard projects from our git repository which are used in nearly all other projects. The setups looks something like this (I have deleted some things because the preference import is quite large:
<?xml version="1.0" encoding="UTF-8"?>
<setup:Project
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:git="http://www.eclipse.org/oomph/setup/git/1.0"
xmlns:jdt="http://www.eclipse.org/oomph/setup/jdt/1.0"
xmlns:predicates="http://www.eclipse.org/oomph/predicates/1.0"
xmlns:projects="http://www.eclipse.org/oomph/setup/projects/1.0"
xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
xmlns:setup.p2="http://www.eclipse.org/oomph/setup/p2/1.0"
xmlns:setup.workingsets="http://www.eclipse.org/oomph/setup/workingsets/1.0"
xsi:schemaLocation="http://www.eclipse.org/oomph/setup/git/1.0 http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/models/Git.ecore http://www.eclipse.org/oomph/setup/jdt/1.0 http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/models/JDT.ecore 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 http://www.eclipse.org/oomph/setup/workingsets/1.0 http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/models/SetupWorkingSets.ecore"
name="mycompany.standard"
label="mycompany">
<setupTask
xsi:type="setup:CompoundTask"
name="Eclipse Installation">
<setupTask
xsi:type="jdt:JRETask"
version="JavaSE-1.8"
location="${jre.location-1.8}"/>
<setupTask
xsi:type="setup:EclipseIniTask"
option="-Xmx"
value="4096m"/>
<setupTask
xsi:type="setup:VariableTask"
name="installation.id"
value="standard"/>
<setupTask
xsi:type="setup:VariableTask"
name="eclipse.target.platform"
value="Mars"
defaultValue=""
storageURI="scope://Workspace"/>
<setupTask
xsi:type="setup:VariableTask"
name="workspace.location"
value="C:\Java\Workspaces\${installation.id}"/>
<setupTask
xsi:type="setup:VariableTask"
name="installation.location"
value="C:\Java\Eclipse\${installation.id}"
label="Installation location rule">
<description>The rule for the absolute folder location where the product is installed</description>
</setupTask>
</setupTask>
<setupTask
xsi:type="setup:CompoundTask"
name="Codestyle Standards">
<setupTask
xsi:type="setup:PreferenceTask"
key="/instance/org.eclipse.wst.jsdt.core/org.eclipse.wst.jsdt.core.formatter.alignment_for_expressions_in_array_initializer"
value="16"/>
[A LOT more of those setupTasks...]
</setupTask>
<setupTask
xsi:type="setup:CompoundTask"
name="Plugin Installation">
<setupTask
xsi:type="setup.p2:P2Task">
<requirement
name="org.eclipse.team.svn.feature.group"/>
<requirement
name="org.eclipse.team.svn.revision.graph.feature.group"/>
<requirement
name="org.zeroturnaround.eclipse.feature.feature.group"/>
<requirement
name="org.zeroturnaround.eclipse.wtp.feature.feature.group"/>
<requirement
name="org.eclipse.recommenders.templates.rcp.feature.feature.group"/>
<requirement
name="org.eclipse.recommenders.templates.snipmatch.rcp.feature.feature.group"/>
<repository
url="${oomph.update.url}"/>
<repository
url="http://download.eclipse.org/releases/mars/201506241002"/>
<repository
url="http://download.eclipse.org/recommenders.incubator/snipmatch/updates/head/"/>
<repository
url="http://update.zeroturnaround.com/update-site/"/>
<repository
url="http://update.zeroturnaround.com/update-site/"/>
</setupTask>
</setupTask>
<setupTask
xsi:type="setup:CompoundTask"
name="Git">
<setupTask
xsi:type="git:GitCloneTask"
location="C:\git\project1"
remoteURI="https://gitlab.mycompany.de/project/project1.git"
pushURI=""
checkoutBranch="develop">
<description>Project 1</description>
</setupTask>
<setupTask
xsi:type="git:GitCloneTask"
location="C:\git\project2"
remoteURI="https://gitlab.mycompany.de/project/project2.git"
pushURI=""
checkoutBranch="develop">
<description>Project 2</description>
</setupTask>
<setupTask
xsi:type="git:GitCloneTask"
location="C:\git\project3"
remoteURI="https://gitlab.mycompany.de/project/project3.git"
pushURI=""
checkoutBranch="develop">
<description>Project 3</description>
</setupTask>
</setupTask>
<setupTask
xsi:type="setup:CompoundTask"
name="Projects">
<setupTask
xsi:type="projects:ProjectsImportTask"
id="1">
<sourceLocator
rootFolder="C:\git\project1"/>
<sourceLocator
rootFolder="C:\git\project2"/>
<sourceLocator
rootFolder="C:\git\project3"/>
</setupTask>
</setupTask>
<setupTask
xsi:type="setup.workingsets:WorkingSetTask"
id="">
<workingSet
name="Mycompany"
id="">
<predicate
xsi:type="predicates:LocationPredicate"
pattern="C:/git/.*"/>
</workingSet>
</setupTask>
<stream name="master"
label="Master"/>
<logicalProjectContainer
xsi:type="setup:ProjectCatalog"
href="index:/org.eclipse.setup#//@projectCatalogs[name='org.eclipse']"/>
<description>mycompany standard development environment</description>
</setup:Project>
So, ok, now you should see everything I have done so far in my environment.
To summarize it:
When I add my setup in the <user> extension of the standard catalog, everything works fine so far. If I use my own catalogs the projects are not imported anymore and I think some other thinks are also not working, have to verify that.
Thanks
|
|
|
| Re: Project import via project catalog [message #1702910 is a reply to message #1702897] |
Mon, 27 July 2015 10:48 |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Matthias,
You're missing this in your project catalog:
<?xml version="1.0" encoding="UTF-8"?>
<setup:WorkspaceTask
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
id="workspace"/>
If you want to make your project catalog extensible so that users can
try authoring their own setups locally and testing them, you might want
to consider adding this to your catalog as well (with URIs and
descriptions that match your catalog).
<project
href="user:/org.eclipse.projects.setup?name='user.project',label='<User>',description='A
container project for local user projects that are virtual members of
the Eclipse.org project catalog'#/"/>
On 27/07/2015 11:52 AM, Matthias Nicklisch wrote:
> Regarding the question about why am I doing this:
> Maybe you've seen my first post here. We want to try Oomph in our
> company and want to setup an environment. We already have a lot of
> standards on how to setup our Eclipse environments and want to support
> and simplify that process for our developers. What I am doing here is
> a proof of concept. Our goal is to have a standard environment in our
> git repository, so that we can define our setups there and everyone
> can access those setups and keep our developers IDEs on one defined
> standard.
That sounds good for everyone.
> As far as I could see it, Oomph is exactly for that purpose. Later we
> want to define setups for our projects to provide a standardized
> environment for all developers who are working on one project.
>
> What I have done so far is, I have setup a product catalog which
> provides some standard Eclipse products we need in our company, I have
> simply copied the product entries from the standard eclipse catalog
> (http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/)
>
> My catalog looks something like this:
>
> NOTE: I've edited some names in the files to ensure privacy for my
> company. But only Labels and parts of the URL which would shows my
> company or would directly link to our repositories. I just wanna be
> safe here =)
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <setup:ProductCatalog
> xmi:version="2.0"
> xmlns:xmi="http://www.omg.org/XMI"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
> xmlns:setup.p2="http://www.eclipse.org/oomph/setup/p2/1.0"
> name="org.eclipse.products"
> label="mycompany">
> <setupTask
> xsi:type="setup:InstallationTask"
> id="installation"/>
> <setupTask
> xsi:type="setup.p2:P2Task">
> <requirement
> name="org.eclipse.oomph.setup.feature.group"/>
> <repository
> url="${oomph.update.url}"/>
> <repository
> url="http://download.eclipse.org/modeling/emf/emf/updates/2.10/core/R201405190339"/>
> </setupTask>
> <setupTask
> xsi:type="setup:EclipseIniTask"
> option="-Doomph.setup"
> value="=true"
> vm="true"/>
> <product name="epp.package.standard"
> label="Eclipse Standard">
> <version
> name="latest"
> label="Latest (Luna)"
> requiredJavaVersion="1.7">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse Standard (Luna)">
> <requirement
> name="epp.package.standard"
> versionRange="[4.4.0,5.0.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.4.0,5.0.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.4.0,5.0.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.10.0,4.0.0)"/>
> <requirement
> name="org.eclipse.pde.feature.group"
> versionRange="[3.10.0,4.0.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/luna"/>
> <repository
> url="http://download.eclipse.org/releases/luna/201502271000"/>
> </setupTask>
> </version>
> <version
> name="latest.released"
> label="Latest Release (Luna)"
> requiredJavaVersion="1.7">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse Standard (Luna)">
> <requirement
> name="epp.package.standard"
> versionRange="[4.4.0,4.5.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.4.0,4.5.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.4.0,4.5.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.10.0,3.11.0)"/>
> <requirement
> name="org.eclipse.pde.feature.group"
> versionRange="[3.10.0,3.11.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/luna"/>
> <repository
> url="http://download.eclipse.org/releases/luna/201502271000"/>
> </setupTask>
> </version>
> <version
> name="luna"
> label="Luna"
> requiredJavaVersion="1.7">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse Standard (Luna)">
> <requirement
> name="epp.package.standard"
> versionRange="[4.4.0,4.5.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.4.0,4.5.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.4.0,4.5.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.10.0,3.11.0)"/>
> <requirement
> name="org.eclipse.pde.feature.group"
> versionRange="[3.10.0,3.11.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/luna"/>
> <repository
> url="http://download.eclipse.org/releases/luna/201502271000"/>
> </setupTask>
> </version>
> <version
> name="kepler"
> label="Kepler"
> requiredJavaVersion="1.6">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse Standard (Kepler)">
> <requirement
> name="epp.package.standard"
> versionRange="[2.0.0,2.1.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.3.0,4.4.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.3.0,4.4.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.9.0,3.10.0)"/>
> <requirement
> name="org.eclipse.pde.feature.group"
> versionRange="[3.9.0,3.10.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/kepler"/>
> <repository
> url="http://download.eclipse.org/releases/kepler/201402280900"/>
> <repository
> url="http://download.eclipse.org/modeling/emf/emf/updates/2.10.x/core/S201501230452"/>
> </setupTask>
> </version>
> <description>
> Package suited for development of Eclipse itself at Eclipse.org;
> based on the Eclipse Platform adding PDE, Git, Marketplace Client,
> source code and developer documentation.<br/>
> <br/>
> Click <a
> href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform">here</a>
> to file a bug against Eclipse Platform.<br/>
> Click <a
> href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EGit">here</a>
> to file a bug against Eclipse Git team provider.
> </description>
> </product>
> <product name="epp.package.java"
> label="Eclipse IDE for Java Developers">
> <annotation
> source="http://www.eclipse.org/oomph/setup/BrandingInfo">
> <detail
> key="imageURI">
> <value>http://www.eclipse.org/downloads/images/java.png</value>
> </detail>
> </annotation>
> <version
> name="latest"
> label="Latest (Mars)"
> requiredJavaVersion="1.7">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse IDE for Java Developers (Mars)">
> <requirement
> name="epp.package.java"
> versionRange="[4.5.0,5.0.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.5.0,5.0.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.5.0,5.0.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.11.0,4.0.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/mars/R"/>
> <repository
> url="http://download.eclipse.org/releases/mars/201506241002"/>
> </setupTask>
> </version>
> <version
> name="latest.released"
> label="Latest Release (Mars)"
> requiredJavaVersion="1.7">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse IDE for Java Developers (Mars)">
> <requirement
> name="epp.package.java"
> versionRange="[4.5.0,4.6.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.5.0,4.6.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.5.0,4.6.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.11.0,3.12.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/mars/R"/>
> <repository
> url="http://download.eclipse.org/releases/mars/201506241002"/>
> </setupTask>
> </version>
> <version
> name="mars"
> label="Mars"
> requiredJavaVersion="1.7">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse IDE for Java Developers (Mars)">
> <requirement
> name="epp.package.java"
> versionRange="[4.5.0,4.6.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.5.0,4.6.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.5.0,4.6.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.11.0,3.12.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/mars/R"/>
> <repository
> url="http://download.eclipse.org/releases/mars/201506241002"/>
> </setupTask>
> </version>
> <version
> name="luna"
> label="Luna"
> requiredJavaVersion="1.6">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse IDE for Java Developers (Luna)">
> <requirement
> name="epp.package.java"
> versionRange="[4.4.0,4.5.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.4.0,4.5.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.4.0,4.5.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.10.0,3.11.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/luna"/>
> <repository
> url="http://download.eclipse.org/releases/luna/201502271000"/>
> </setupTask>
> </version>
> <version
> name="kepler"
> label="Kepler"
> requiredJavaVersion="1.6">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse IDE for Java Developers (Kepler)">
> <requirement
> name="epp.package.java"
> versionRange="[2.0.0,2.1.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.3.0,4.4.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.3.0,4.4.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.9.0,3.10.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/kepler"/>
> <repository
> url="http://download.eclipse.org/releases/kepler/201402280900"/>
> <repository
> url="http://download.eclipse.org/modeling/emf/emf/updates/2.10.x/core/S201501230452"/>
> </setupTask>
> </version>
> <version
> name="juno"
> label="Juno"
> requiredJavaVersion="1.5">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse IDE for Java Developers (Juno)">
> <requirement
> name="epp.package.java"
> versionRange="[1.5.0,1.6.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.2.0,4.3.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.2.0,4.3.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.8.0,3.9.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/juno"/>
> <repository
> url="http://download.eclipse.org/releases/juno/201303010900"/>
> <repository
> url="http://download.eclipse.org/modeling/emf/emf/updates/2.10.x/core/S201501230452"/>
> </setupTask>
> </version>
> <description>The essential tools for any Java developer, including
> a Java IDE, a Git client, XML Editor, Mylyn, Maven integration and
> WindowBuilder</description>
> </product>
> <product name="epp.package.jee"
> label="Eclipse IDE for Java EE Developers">
> <annotation
> source="http://www.eclipse.org/oomph/setup/BrandingInfo">
> <detail
> key="imageURI">
> <value>http://www.eclipse.org/downloads/images/javaee.png</value>
> </detail>
> </annotation>
> <version
> name="latest"
> label="Latest (Mars)"
> requiredJavaVersion="1.7">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse IDE for Java EE Developers (Mars)">
> <requirement
> name="epp.package.jee"
> versionRange="[4.5.0,5.0.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.5.0,5.0.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.5.0,5.0.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.11.0,4.0.0)"/>
> <requirement
> name="org.eclipse.pde.feature.group"
> versionRange="[3.11.0,4.0.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/mars/R"/>
> <repository
> url="http://download.eclipse.org/releases/mars/201506241002"/>
> </setupTask>
> </version>
> <version
> name="latest.released"
> label="Latest Release (Mars)"
> requiredJavaVersion="1.7">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse IDE for Java EE Developers (Mars)">
> <requirement
> name="epp.package.jee"
> versionRange="[4.5.0,4.6.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.5.0,4.6.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.5.0,4.6.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.11.0,3.12.0)"/>
> <requirement
> name="org.eclipse.pde.feature.group"
> versionRange="[3.11.0,3.12.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/mars/R"/>
> <repository
> url="http://download.eclipse.org/releases/mars/201506241002"/>
> </setupTask>
> </version>
> <version
> name="mars"
> label="Mars"
> requiredJavaVersion="1.7">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse IDE for Java EE Developers (Mars)">
> <requirement
> name="epp.package.jee"
> versionRange="[4.5.0,4.6.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.5.0,4.6.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.5.0,4.6.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.11.0,3.12.0)"/>
> <requirement
> name="org.eclipse.pde.feature.group"
> versionRange="[3.11.0,3.12.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/mars/R"/>
> <repository
> url="http://download.eclipse.org/releases/mars/201506241002"/>
> </setupTask>
> </version>
> <version
> name="luna"
> label="Luna"
> requiredJavaVersion="1.6">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse IDE for Java EE Developers (Luna)">
> <requirement
> name="epp.package.jee"
> versionRange="[4.4.0,4.5.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.4.0,4.5.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.4.0,4.5.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.10.0,3.11.0)"/>
> <requirement
> name="org.eclipse.pde.feature.group"
> versionRange="[3.10.0,3.11.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/luna"/>
> <repository
> url="http://download.eclipse.org/releases/luna/201502271000"/>
> </setupTask>
> </version>
> <version
> name="kepler"
> label="Kepler"
> requiredJavaVersion="1.6">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse IDE for Java EE Developers (Kepler)">
> <requirement
> name="epp.package.jee"
> versionRange="[2.0.0,2.1.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.3.0,4.4.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.3.0,4.4.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.9.0,3.10.0)"/>
> <requirement
> name="org.eclipse.pde.feature.group"
> versionRange="[3.9.0,3.10.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/kepler"/>
> <repository
> url="http://download.eclipse.org/releases/kepler/201402280900"/>
> <repository
> url="http://download.eclipse.org/modeling/emf/emf/updates/2.10.x/core/S201501230452"/>
> </setupTask>
> </version>
> <version
> name="juno"
> label="Juno"
> requiredJavaVersion="1.5">
> <setupTask
> xsi:type="setup.p2:P2Task"
> label="Eclipse IDE for Java EE Developers (Juno)">
> <requirement
> name="epp.package.jee"
> versionRange="[1.5.0,1.6.0)"/>
> <requirement
> name="org.eclipse.platform.feature.group"
> versionRange="[4.2.0,4.3.0)"/>
> <requirement
> name="org.eclipse.rcp.feature.group"
> versionRange="[4.2.0,4.3.0)"/>
> <requirement
> name="org.eclipse.jdt.feature.group"
> versionRange="[3.8.0,3.9.0)"/>
> <requirement
> name="org.eclipse.pde.feature.group"
> versionRange="[3.8.0,3.9.0)"/>
> <repository
> url="http://download.eclipse.org/technology/epp/packages/juno"/>
> <repository
> url="http://download.eclipse.org/releases/juno/201303010900"/>
> <repository
> url="http://download.eclipse.org/modeling/emf/emf/updates/2.10.x/core/S201501230452"/>
> </setupTask>
> </version>
> <description>Tools for Java developers creating Java EE and Web
> applications, including a Java IDE, tools for Java EE, JPA, JSF,
> Mylyn, EGit and others.</description>
> </product>
> </setup:ProductCatalog>
>
>
> I have setup a org.eclipse.setup file in which I reference to my
> catalogs.
>
> I also have setup a project catalog which looks something like this:
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <setup:ProjectCatalog
> xmi:version="2.0"
> xmlns:xmi="http://www.omg.org/XMI"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
> name="org.eclipse"
> label="mycompany">
> <setupTask
> xsi:type="setup:ResourceCreationTask"
> content="MAX_RECENT_WORKSPACES=5
> RECENT_WORKSPACES=${workspace.location|property}
> RECENT_WORKSPACES_PROTOCOL=3
> SHOW_WORKSPACE_SELECTION_DIALOG=true
> eclipse.preferences.version=1"
> targetURL="configuration:/.settings/org.eclipse.ui.ide.prefs"/>
> <project name="GitHubContainer"
> label="My company Projects">
> <project
> href="https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/mycompany_Standard_Mars.setup#/"/>
> </project>
> <description></description>
> </setup:ProjectCatalog>
>
>
>
> Ok, now my problem.
>
> Yes, it is like you've said, in my first approach I used the Eclipse
> installer in advanced mode, chose Java EE as my Standard Eclipse
> product and then added via drag&drop my setup file to the <user>
> extension.
> That way, everything works fine and everything I have defined in my
> setup is processed properly.
>
> Now, I wanted to try everything via our git repository, so I modified
> the eclipse-inst.ini in the directory of the eclipse installer and
> added this line:
>
>
> -Doomph.redirection.setups=http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/->https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/master/setups/
>
>
>
> This is what I meant with redirection to our catalogs.
> So, when I use that, I can choose my product and also my project
> setup, everything fine to this point. Generally, my project setup is
> working fine. I have defined some variables for my installation (e.g.
> the workspace and installation location, they should be the same on
> every computer here) I have alos defined a lot of properties for our
> code style which we have imported before via an epf file. I have
> parsed every line in that file and added a preference setup task for
> each line. I also defined some plugins we want to have installed and
> some standard projects from our git repository which are used in
> nearly all other projects. The setups looks something like this (I
> have deleted some things because the preference import is quite large:
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <setup:Project
> xmi:version="2.0"
> xmlns:xmi="http://www.omg.org/XMI"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:git="http://www.eclipse.org/oomph/setup/git/1.0"
> xmlns:jdt="http://www.eclipse.org/oomph/setup/jdt/1.0"
> xmlns:predicates="http://www.eclipse.org/oomph/predicates/1.0"
> xmlns:projects="http://www.eclipse.org/oomph/setup/projects/1.0"
> xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
> xmlns:setup.p2="http://www.eclipse.org/oomph/setup/p2/1.0"
> xmlns:setup.workingsets="http://www.eclipse.org/oomph/setup/workingsets/1.0"
> xsi:schemaLocation="http://www.eclipse.org/oomph/setup/git/1.0
> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/models/Git.ecore
> http://www.eclipse.org/oomph/setup/jdt/1.0
> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/models/JDT.ecore
> 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
> http://www.eclipse.org/oomph/setup/workingsets/1.0
> http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/models/SetupWorkingSets.ecore"
> name="mycompany.standard"
> label="mycompany">
> <setupTask
> xsi:type="setup:CompoundTask"
> name="Eclipse Installation">
> <setupTask
> xsi:type="jdt:JRETask"
> version="JavaSE-1.8"
> location="${jre.location-1.8}"/>
> <setupTask
> xsi:type="setup:EclipseIniTask"
> option="-Xmx"
> value="4096m"/>
> <setupTask
> xsi:type="setup:VariableTask"
> name="installation.id"
> value="standard"/>
> <setupTask
> xsi:type="setup:VariableTask"
> name="eclipse.target.platform"
> value="Mars"
> defaultValue=""
> storageURI="scope://Workspace"/>
> <setupTask
> xsi:type="setup:VariableTask"
> name="workspace.location"
> value="C:\Java\Workspaces\${installation.id}"/>
> <setupTask
> xsi:type="setup:VariableTask"
> name="installation.location"
> value="C:\Java\Eclipse\${installation.id}"
> label="Installation location rule">
> <description>The rule for the absolute folder location where the
> product is installed</description>
> </setupTask>
> </setupTask>
> <setupTask
> xsi:type="setup:CompoundTask"
> name="Codestyle Standards">
> <setupTask
> xsi:type="setup:PreferenceTask"
> key="/instance/org.eclipse.wst.jsdt.core/org.eclipse.wst.jsdt.core.formatter.alignment_for_expressions_in_array_initializer"
> value="16"/>
> [A LOT more of those setupTasks...]
> </setupTask>
> <setupTask
> xsi:type="setup:CompoundTask"
> name="Plugin Installation">
> <setupTask
> xsi:type="setup.p2:P2Task">
> <requirement
> name="org.eclipse.team.svn.feature.group"/>
> <requirement
> name="org.eclipse.team.svn.revision.graph.feature.group"/>
> <requirement
> name="org.zeroturnaround.eclipse.feature.feature.group"/>
> <requirement
> name="org.zeroturnaround.eclipse.wtp.feature.feature.group"/>
> <requirement
> name="org.eclipse.recommenders.templates.rcp.feature.feature.group"/>
> <requirement
> name="org.eclipse.recommenders.templates.snipmatch.rcp.feature.feature.group"/>
> <repository
> url="${oomph.update.url}"/>
> <repository
> url="http://download.eclipse.org/releases/mars/201506241002"/>
> <repository
> url="http://download.eclipse.org/recommenders.incubator/snipmatch/updates/head/"/>
> <repository
> url="http://update.zeroturnaround.com/update-site/"/>
> <repository
> url="http://update.zeroturnaround.com/update-site/"/>
> </setupTask>
> </setupTask>
> <setupTask
> xsi:type="setup:CompoundTask"
> name="Git">
> <setupTask
> xsi:type="git:GitCloneTask"
> location="C:\git\project1"
> remoteURI="https://gitlab.mycompany.de/project/project1.git"
> pushURI=""
> checkoutBranch="develop">
> <description>Project 1</description>
> </setupTask>
> <setupTask
> xsi:type="git:GitCloneTask"
> location="C:\git\project2"
> remoteURI="https://gitlab.mycompany.de/project/project2.git"
> pushURI=""
> checkoutBranch="develop">
> <description>Project 2</description>
> </setupTask>
> <setupTask
> xsi:type="git:GitCloneTask"
> location="C:\git\project3"
> remoteURI="https://gitlab.mycompany.de/project/project3.git"
> pushURI=""
> checkoutBranch="develop">
> <description>Project 3</description>
> </setupTask>
> </setupTask>
> <setupTask
> xsi:type="setup:CompoundTask"
> name="Projects">
> <setupTask
> xsi:type="projects:ProjectsImportTask"
> id="1">
> <sourceLocator
> rootFolder="C:\git\project1"/>
> <sourceLocator
> rootFolder="C:\git\project2"/>
> <sourceLocator
> rootFolder="C:\git\project3"/>
> </setupTask>
> </setupTask>
> <setupTask
> xsi:type="setup.workingsets:WorkingSetTask"
> id="">
> <workingSet
> name="Mycompany"
> id="">
> <predicate
> xsi:type="predicates:LocationPredicate"
> pattern="C:/git/.*"/>
> </workingSet>
> </setupTask>
> <stream name="master"
> label="Master"/>
> <logicalProjectContainer
> xsi:type="setup:ProjectCatalog"
> href="index:/org.eclipse.setup#//@projectCatalogs[name='org.eclipse']"/>
> <description>mycompany standard development environment</description>
> </setup:Project>
>
>
> So, ok, now you should see everything I have done so far in my
> environment.
>
> To summarize it:
> When I add my setup in the <user> extension of the standard catalog,
> everything works fine so far. If I use my own catalogs the projects
> are not imported anymore and I think some other thinks are also not
> working, have to verify that.
>
> Thanks
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| | |
| Re: Project import via project catalog [message #1702956 is a reply to message #1702943] |
Mon, 27 July 2015 14:45 |
Matthias Nicklisch
Messages: 20
Registered: July 2015 |
Junior Member |
|
|
Well, this redirection thing I've got from this site here: https://github.com/joergreichert/oomph-catalogue#tasks-not-used-yet-in-this-example
Works fine. Is there another way to access my catalogs?
The tipp with the Navigate->OpenSetup in the installation was a good advice, there were some red crosses caused by the idiocy of me =) I had hoped that this was the cause of the problem, but nope, I fixed everything so that I have no errors left, but still the same problem.
From my point of view, it looks like that in the initial setup done by the installer itself, the setup from the project catalog is processed, all defined plugins are installed. The rest (project import, preferences and so on) are done when the eclipse client has started and the setup tasks are processed. At this point, it seems that the project setup file is not loaded anymore or even taken into consideration by eclipse, so that only the product setup is processed.
One interesting point is, when I manually want to reload the setup tasks (Help->Perform Setup Tasks...) the Eclipse client loads something, I assume from my repository, and then nothing happens, but in my task manager I can see that this eclipse process is growing bigger and bigger and even when I close this eclipse, something happens because I can't delete the workspace and the installation folder because the eclipse.exe is still active and.... doing things...
So, as I said, from my point of view it looks like my project setup is not loaded anymore after the initial setup is complete which is the cause that some tasks are not completed.
Do you have any idea what could be the problem?
|
|
|
| Re: Project import via project catalog [message #1702967 is a reply to message #1702956] |
Mon, 27 July 2015 15:16 |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Matthias,
Sorry for the quoting...
On 27/07/2015 4:45 PM, Matthias Nicklisch wrote:
> Well, this redirection thing I've got from this site here:
> https://github.com/joergreichert/oomph-catalogue#tasks-not-used-yet-in-this-example
Look at your eclipse.ini and show me all the -Doomph.redirection.*
options in that file.
>
> Works fine. Is there another way to access my catalogs?
>
> The tipp with the Navigate->OpenSetup in the installation was a good
> advice, there were some red crosses caused by the idiocy of me =) I
> had hoped that this was the cause of the problem, but nope, I fixed
> everything so that I have no errors left, but still the same problem.
>
> From my point of view, it looks like that in the initial setup done by
> the installer itself, the setup from the project catalog is processed,
> all defined plugins are installed.
Perhaps it works there because of the -D option you added there but it's
not there in your installation's eclipse.ini. That's why I ask what's
there.
> The rest (project import, preferences and so on) are done when the
> eclipse client has started and the setup tasks are processed.
So that sounds good. What isn't being done then? And are you sure it
should be getting done. After all, you seem to create a clone in a
specific location, so once that clone exists on disk, it won't be
created again.
> At this point, it seems that the project setup file is not loaded
> anymore or even taken into consideration by eclipse, so that only the
> product setup is processed.
> One interesting point is, when I manually want to reload the setup
> tasks (Help->Perform Setup Tasks...) the Eclipse client loads
> something, I assume from my repository, and then nothing happens,
You mean the dialog doesn't come up? I'd expect the dialog to come up.
If it does, advance to the confirmation page, and choose the show all
tasks via the checkbox; this should show all the tasks you expect, but
they might not need to be performed and hence are grayed out. If it
doesn't come up, and if you show the Progress View before doing this,
do you see jobs for loading the model?
> but in my task manager I can see that this eclipse process is growing
> bigger and bigger and even when I close this eclipse, something
> happens because I can't delete the workspace and the installation
> folder because the eclipse.exe is still active and.... doing things...
Which version of Java are you using? Do you have enough heap space
allocated and enough permgen for Java < 1.8? Either of those being to
small can cause this type of behavior...
>
> So, as I said, from my point of view it looks like my project setup is
> not loaded anymore after the initial setup is complete which is the
> cause that some tasks are not completed.
But the Navigate -> Open Setup -> ... shows choices for the Streams of
the project's you've chosen at install time?
>
> Do you have any idea what could be the problem?
What's in your
<workspace>\.metadata\.plugins\org.eclipse.oomph.setup\workspace.setup?
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Project import via project catalog [message #1702974 is a reply to message #1702967] |
Mon, 27 July 2015 15:51 |
Matthias Nicklisch
Messages: 20
Registered: July 2015 |
Junior Member |
|
|
Ok, first things first, I want to thank you for your support. I hope you havn't already enough of me =)
Ok, there was some confusion on my site about all those ini files.
I only knew about this redirection option in the eclipse-inst.ini of the installer itself, which I already showed you. But yes, there are some redirection options:
-startup
../../../../Users/mnicklisch/.p2/pool/plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar
--launcher.library
../../../../Users/mnicklisch/.p2/pool/plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417
-product
org.eclipse.epp.package.jee.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-install
C:/Java/Eclipse/standard/eclipse
-Xmx
4096m
-vmargs
-Dosgi.requiredJavaVersion=1.7
-Xms256m
-Xmx1024m
-Doomph.setup=true
-Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest
-Doomph.redirection.index.redirection=index:/->https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/
-Doomph.redirection.index.location.redirection=http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/->https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/
So, from my point of view this looks fine so far.
Regarding:
> The rest (project import, preferences and so on) are done when the
> eclipse client has started and the setup tasks are processed.
I think I was a bit unclear, I'm no native speaker, so sorry here.
What I was trying to say:
Tasks in my project setup:
1. some preferences like workspace location and so on
2. Resource copy for maven settings
3. Codestyle Preferences
4. Plugin Installation
5. Cloning Git Repositories
6. Project import
7. Working Sets
So, when installing from a local setup file via the <user> extension, all point from 1 to 7 are executed properly. When I use the same setup with my catalogs, the steps 2, 3 and 5 to 7 are not executed at all, but my plugins are installed. So what I assumed was that some of those tasks are executed when the installer runs and creates new new installation and some tasks are executed after the installation is started the first time. And these taks, which should run when the installation is started, are no executed.
Regarding the things I see in Navigation->Open Setups
In my installation I only see Open User, Open Workspace, Open Installation, Open Eclipse IDE for Java EE Developers (the standard product) and parent models. Shouldn't here be my project setup somewhere? I think in my installation with the local setup file I saw such an entry there. Because of that and the point before I assume that my project setup is not loaded anymore after the client hast started the first time.
Regarding the manual start of the setup tasks. No, this dialog doesn't come up. I see a loading bar twice and then nothing. Usually there would be this symbol in the bottom right corner with those twisting arrows, but they do not appear. So basically, nothing happens. When I installed it with a local setup file this step has worked fine. I started manually and the dialog did come up.
I am using Java 1.8. In my setup I have set the memory to 4Gb. I have changed nothing in my JVM or other properties, so heap size and everything is standard I assume.
In this workspace file I can see this:
<?xml version="1.0" encoding="UTF-8"?>
<setup:Workspace
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
name="workspace"/>
I assume there should be more and that's our problem right now, isn't it? =)
Thanks in advance.
|
|
|
| Re: Project import via project catalog [message #1702983 is a reply to message #1702974] |
Mon, 27 July 2015 16:54 |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Matthias,
Comments below. (It's a habit and lets me comment in the context of
your comments.)
On 27/07/2015 5:51 PM, Matthias Nicklisch wrote:
> Ok, first things first, I want to thank you for your support. I hope
> you havn't already enough of me =)
>
> Ok, there was some confusion on my site about all those ini files.
> I only knew about this redirection option in the eclipse-inst.ini of
> the installer itself, which I already showed you. But yes, there are
> some redirection options:
>
>
> -startup
> ./../../../Users/mnicklisch/.p2/pool/plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar
>
> --launcher.library
> ./../../../Users/mnicklisch/.p2/pool/plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417
>
> -product
> org.eclipse.epp.package.jee.product
> --launcher.defaultAction
> openFile
> --launcher.XXMaxPermSize
> 256M
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> --launcher.defaultAction
> openFile
> --launcher.appendVmargs
> -install
> C:/Java/Eclipse/standard/eclipse
> -Xmx
> 4096m
> -vmargs
> -Dosgi.requiredJavaVersion=1.7
> -Xms256m
> -Xmx1024m
> -Doomph.setup=true
> -Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest
>
> -Doomph.redirection.index.redirection=index:/->https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/
>
> -Doomph.redirection.index.location.redirection=http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/->https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/
>
>
>
>
> So, from my point of view this looks fine so far.
>
> Regarding:
>> The rest (project import, preferences and so on) are done when the
>> eclipse client has started and the setup tasks are processed.
>
> I think I was a bit unclear, I'm no native speaker, so sorry here.
>
> What I was trying to say:
>
> Tasks in my project setup:
> 1. some preferences like workspace location and so on
> 2. Resource copy for maven settings
> 3. Codestyle Preferences
> 4. Plugin Installation
> 5. Cloning Git Repositories
> 6. Project import
> 7. Working Sets
>
> So, when installing from a local setup file via the <user> extension,
> all point from 1 to 7 are executed properly. When I use the same setup
> with my catalogs, the steps 2, 3 and 5 to 7 are not executed at all,
> but my plugins are installed. So what I assumed was that some of those
> tasks are executed when the installer runs and creates new new
> installation and some tasks are executed after the installation is
> started the first time. And these taks, which should run when the
> installation is started, are no executed.
>
> Regarding the things I see in Navigation->Open Setups
> In my installation I only see Open User, Open Workspace, Open
> Installation, Open Eclipse IDE for Java EE Developers (the standard
> product) and parent models. Shouldn't here be my project setup somewhere?
Yes, but there isn't apparently, which would explain a lot of the problems.
> I think in my installation with the local setup file I saw such an
> entry there. Because of that and the point before I assume that my
> project setup is not loaded anymore after the client hast started the
> first time.
Yes, it must be there in your local case...
>
> Regarding the manual start of the setup tasks. No, this dialog doesn't
> come up. I see a loading bar twice and then nothing. Usually there
> would be this symbol in the bottom right corner with those twisting
> arrows, but they do not appear. So basically, nothing happens. When I
> installed it with a local setup file this step has worked fine. I
> started manually and the dialog did come up.
Are there errors showing in your Error Log view? It sounds like
something is going wrong.
>
> I am using Java 1.8. In my setup I have set the memory to 4Gb. I have
> changed nothing in my JVM or other properties, so heap size and
> everything is standard I assume.
>
> In this workspace file I can see this:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <setup:Workspace
> xmi:version="2.0"
> xmlns:xmi="http://www.omg.org/XMI"
> xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
> name="workspace"/>
This looks wrong. There is no stream being referenced. Are you sure
you've really double clicked and added the project during the
installation process. This should have at least one entry like this for
your project's stream.
<stream
href="index:/org.eclipse.setup#//@projectCatalogs[name='org.eclipse']/@projects[name='emf']/@projects[name='core']/@streams[name='R2_11_maintenance']"/>
>
>
> I assume there should be more and that's our problem right now, isn't
> it? =)
Exactly. This file is written by the installer based on the streams
you've selected on the Project page. Perhaps you should try replacing
<project name="GitHubContainer"
label="My company Projects">
<project
href="https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/mycompany_Standard_Mars.setup#/"/>
</project>
<description></description>
with
<project
href="https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/mycompany_Standard_Mars.setup#/"/>
</project>
in your project catalog.
On the project page you really see this project and you've added it to
the streams table on that page?
>
> Thanks in advance.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Project import via project catalog [message #1703001 is a reply to message #1702983] |
Mon, 27 July 2015 20:13 |
Matthias Nicklisch
Messages: 20
Registered: July 2015 |
Junior Member |
|
|
Hi,
I have to check some things tomorrow, but what I can tell you, yes, I definitely double clicked the setup from the project catalog. And in this first stept it works, because my plugins are installed, which is defined in my setup from the project catalog. If I had forgotten to click it, there would be no new Plugins.
I also delete everything from previous installation runs, I delete the installation directory and the workspace directory completely, so there should be no problem regarding this.
Also there should be no problems that an old version of the setup is fetched. I work with the program SourceTree and I make a commit for every new run and the installer fetches the file directly from git. So hopefully there is no problem with caching or something like this.
|
|
|
| Re: Project import via project catalog [message #1703024 is a reply to message #1703001] |
Tue, 28 July 2015 06:05 |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Matthias,
Some suggestions below.
On 27/07/2015 10:13 PM, Matthias Nicklisch wrote:
> Hi,
>
> I have to check some things tomorrow, but what I can tell you, yes, I
> definitely double clicked the setup from the project catalog.
Try this. Don't launch the installation automatically. When the
installer is finished look at the workspace.setup. In particular look
at the URI of the referenced Stream. There must be one at that point.
It should be of the form index:/...
> And in this first stept it works, because my plugins are installed,
> which is defined in my setup from the project catalog.
So it's definitely working in the installer, but the stream reference
could be a broken link in the installation if the URI redirections are
different there...
> If I had forgotten to click it, there would be no new Plugins.
Well, you also get plugins from your product choice...
> I also delete everything from previous installation runs, I delete the
> installation directory and the workspace directory completely, so
> there should be no problem regarding this.
But your clones you've also put somewhere globally, right?
> Also there should be no problems that an old version of the setup is
> fetched. I work with the program SourceTree and I make a commit for
> every new run and the installer fetches the file directly from git.
From your local clone?
> So hopefully there is no problem with caching or something like this.
Indeed. The fundamental problem appears to be that the stream reference
in your workspace.setup isn't there, so that's what we need to figure out...
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| |
| Re: Project import via project catalog [message #1703034 is a reply to message #1703029] |
Tue, 28 July 2015 07:34 |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Matthias,
Comments below.
On 28/07/2015 9:00 AM, Matthias Nicklisch wrote:
> Hi,
>
> I have tried not starting the installation after the installer has
> finished. But at this point there is no workspace.
The installer should save the workspace.setup.
> The workspace is created when I start the installation.
And then an empty workspace.setup is created if there isn't already a
workspace.setup there.
> When I start this eclipse, the workspace is created (but he asks me
> for the location of the workspace, this standard dialog from eclipse)
> and then the workspace.setup is nearly empty, as shown in the post
> before.
And does that suggest the location you expect, i.e., the one the
installer would have used when the installation was automatically launched?
>
> The plugins which are installed which I reference in my post are
> solely defined in the project setup, not in the product setup. Those
> are plugins which are not part of a standard eclipse installation.
This isn't an issue of the Workspace task being missing?
>
> My Git clones are in a local repository, yes. I share it with the
> eclipse installation I am using for my other work.
And that has the Workspace task in it now? I.e., that clone has pulled
so it's not stale and the Project Catalog there has the Workspace task
in it? (Of course you know that sharing clones across multiple IDEs
that might be running at the same time is a bad idea.)
Or another way of asking it, is there a Workspace task shown on the
confirmation page of the installer?
> I don't delete them every time. But the synchronization is working
> fine and useally the projects are imported. I think the only problem
> here is that with the workspace.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Project import via project catalog [message #1703039 is a reply to message #1703034] |
Tue, 28 July 2015 07:58 |
Matthias Nicklisch
Messages: 20
Registered: July 2015 |
Junior Member |
|
|
Hi,
> > I have tried not starting the installation after the installer has
> > finished. But at this point there is no workspace.
> The installer should save the workspace.setup.
> > The workspace is created when I start the installation.
> And then an empty workspace.setup is created if there isn't already a
> workspace.setup there.
No, there is no workspace folder at all. I have defined a fixed value for the location of my workspace in my project setup. And when I start the installation the workspace is created there. But there is no workspace folder at all before starting the installation.
> > The plugins which are installed which I reference in my post are
> > solely defined in the project setup, not in the product setup. Those
> > are plugins which are not part of a standard eclipse installation.
> This isn't an issue of the Workspace task being missing?
Regarding the plugins, no, that isn't an issue. Look at my list of tasks I have defined in my project setup (https://www.eclipse.org/forums/index.php?t=msg&th=1068840&goto=1702974&#msg_1702974) It seems that only step 1, 2 and 4 are executed by the installer.
And that has the Workspace task in it now? I.e., that clone has pulled
so it's not stale and the Project Catalog there has the Workspace task
in it? (Of course you know that sharing clones across multiple IDEs
that might be running at the same time is a bad idea.)
I know that sharing those clones across multiple IDEs is a bad idea and I wouldn't use that. It is only for testing oomph. I just have to work on other things at the same time =)
Here is the log of the installer when I run it. I have removed some lines where he installs the standard eclipse packages to keep it small:
And you can see there, for example the installation of the *org.zeroturnaround packages, those are defined in the project setup.
Executing bootstrap tasks
Product org.eclipse.products.epp.package.jee.latest.released
Project org.eclipse.mycompanyGitContainer.mycompany.standard.master
Bundle org.eclipse.oomph.setup 1.2.0.v20150630-0542, build=1516, branch=81eceb6fcc787b7f857d8858902958fa3a8d3704, commit=81eceb6fcc787b7f857d8858902958fa3a8d3704
Bundle org.eclipse.oomph.setup.core 1.2.0.v20150703-1301, build=1516, branch=81eceb6fcc787b7f857d8858902958fa3a8d3704, commit=81eceb6fcc787b7f857d8858902958fa3a8d3704
Bundle org.eclipse.oomph.setup.installer 1.2.0.v20150703-1301, build=1516, branch=81eceb6fcc787b7f857d8858902958fa3a8d3704, commit=81eceb6fcc787b7f857d8858902958fa3a8d3704
Bundle org.eclipse.oomph.setup.p2 1.1.0.v20150628-1013, build=1516, branch=81eceb6fcc787b7f857d8858902958fa3a8d3704, commit=81eceb6fcc787b7f857d8858902958fa3a8d3704
Performing P2 Director (Eclipse IDE for Java EE Developers (Mars))
Offline = false
Mirrors = true
Resolving 17 requirements from 7 repositories to C:\Java\Eclipse\standard\eclipse
Requirement org.eclipse.team.svn.feature.group
Requirement org.eclipse.team.svn.revision.graph.feature.group
Requirement org.zeroturnaround.eclipse.feature.feature.group
Requirement org.zeroturnaround.eclipse.wtp.feature.feature.group
Requirement org.eclipse.recommenders.templates.rcp.feature.feature.group
Requirement org.eclipse.recommenders.templates.snipmatch.rcp.feature.feature.group
Requirement epp.package.jee [4.5.0,4.6.0)
Requirement org.eclipse.platform.feature.group [4.5.0,4.6.0)
Requirement org.eclipse.rcp.feature.group [4.5.0,4.6.0)
Requirement org.eclipse.jdt.feature.group [3.11.0,3.12.0)
Requirement org.eclipse.pde.feature.group [3.11.0,3.12.0)
Requirement org.eclipse.oomph.setup.feature.group
Requirement org.eclipse.oomph.setup.jdt.feature.group
Requirement org.eclipse.oomph.setup.git.feature.group
Requirement org.eclipse.egit.feature.group
Requirement org.eclipse.oomph.setup.projects.feature.group
Requirement org.eclipse.oomph.setup.workingsets.feature.group
Repository http://download.eclipse.org/oomph/updates/milestone/latest
Repository http://download.eclipse.org/releases/mars/201506241002
Repository http://download.eclipse.org/recommenders.incubator/snipmatch/updates/head/
Repository http://update.zeroturnaround.com/update-site/
Repository http://download.eclipse.org/technology/epp/packages/mars/R
Repository http://download.eclipse.org/modeling/emf/emf/updates/2.10/core/R201405190339
Repository http://download.eclipse.org/egit/updates
Adding repository http://download.eclipse.org/egit/updates
Fetching p2.index from http://download.eclipse.org/releases/mars/201506241002/
Fetching p2.index from http://update.zeroturnaround.com/update-site/
Adding repository http://download.eclipse.org/releases/mars/201506241002
Adding repository http://update.zeroturnaround.com/update-site/
Adding repository http://download.eclipse.org/recommenders.incubator/snipmatch/updates/head/
Adding repository http://download.eclipse.org/modeling/emf/emf/updates/2.10/core/R201405190339
Adding repository http://download.eclipse.org/technology/epp/packages/mars/R
Adding repository http://download.eclipse.org/oomph/updates/milestone/latest
Fetching content.jar from http://download.eclipse.org/recommenders.incubator/snipmatch/updates/head/
Calculating requirements and dependencies.
Computing prerequisite plan
Downloading epp.package.jee.executable.win32.win32.x86_64
Downloading org.eclipse.platform.ide.executable.win32.win32.x86_64
Downloading org.eclipse.platform_root
Downloading org.eclipse.rcp_root
Installing a.jre.javase
Installing ch.qos.logback.classic
Installing ch.qos.logback.core
Installing ch.qos.logback.slf4j
Installing com.google.gson
Installing com.google.guava
Installing com.google.inject
Installing com.google.inject.multibindings
Installing com.ibm.icu
Installing com.jcraft.jsch
Installing com.sun.el
Installing config.a.jre.javase
Installing epp.package.jee
Installing epp.package.jee.executable.win32.win32.x86_64
Installing epp.package.jee.executable.win32.win32.x86_64.eclipse
Installing java_cup.runtime
Installing javaewah
Installing javax.activation
Installing javax.annotation
Installing javax.el
Installing javax.inject
Installing javax.jws
Installing javax.mail
Installing javax.persistence
Installing javax.servlet
Installing javax.servlet.jsp
Installing javax.wsdl
Installing javax.xml
Installing javax.xml.rpc
Installing javax.xml.soap
Installing javax.xml.stream
Installing javax.xml.ws
Installing net.sourceforge.lpg.lpgjavaruntime
Installing org.antlr.runtime
Installing org.apache.ant
Installing org.apache.axis
Installing org.apache.batik.css
Installing org.apache.batik.util
Installing org.apache.batik.util.gui
Installing org.apache.bcel
Installing org.apache.commons.cli
Installing org.apache.commons.codec
Installing org.apache.commons.collections
Installing org.apache.commons.compress
Installing org.apache.commons.discovery
Installing org.apache.commons.httpclient
Installing org.apache.commons.io
Installing org.apache.commons.jxpath
Installing org.apache.commons.lang
Installing org.apache.commons.lang3
Installing org.apache.commons.logging
Installing org.apache.commons.math
Installing org.apache.commons.net
Installing org.apache.commons.pool
Installing org.apache.felix.gogo.command
Installing org.apache.felix.gogo.runtime
Installing org.apache.felix.gogo.shell
Installing org.apache.httpcomponents.httpclient
Installing org.apache.httpcomponents.httpcore
Installing org.apache.jasper.glassfish
Installing org.apache.log4j
Installing org.apache.lucene.analysis
Installing org.apache.lucene.core
Installing org.apache.solr.client.solrj
Installing org.apache.velocity
Installing org.apache.ws.commons.util
Installing org.apache.wsil4j
Installing org.apache.xalan
Installing org.apache.xerces
Installing org.apache.xml.resolver
Installing org.apache.xml.serializer
Installing org.apache.xmlrpc
Installing org.eclipse.aether.api
[Intalling lots of eclipse packages...]
Installing org.hamcrest.core
Installing org.jboss.tools.maven.jaxrs
Installing org.jboss.tools.maven.jpa
Installing org.jboss.tools.maven.jsf
Installing org.jdom
Installing org.jsoup
Installing org.junit
Installing org.maven.ide.eclipse
Installing org.maven.ide.eclipse.wtp
Installing org.mozilla.javascript
Installing org.objectweb.asm
Installing org.objectweb.asm.tree
Installing org.sat4j.core
Installing org.sat4j.pb
Installing org.slf4j.api
Installing org.slf4j.impl.log4j12
Installing org.sonatype.m2e.mavenarchiver
Installing org.sonatype.m2e.mavenarchiver.feature.feature.group
Installing org.sonatype.m2e.mavenarchiver.feature.feature.jar
Installing org.tukaani.xz
Installing org.uddi4j
Installing org.w3c.css.sac
Installing org.w3c.dom.events
Installing org.w3c.dom.smil
Installing org.w3c.dom.svg
Installing org.zeroturnaround.eclipse
Installing org.zeroturnaround.eclipse.config
Installing org.zeroturnaround.eclipse.debug
Installing org.zeroturnaround.eclipse.embedder
Installing org.zeroturnaround.eclipse.feature.feature.group
Installing org.zeroturnaround.eclipse.feature.feature.jar
Installing org.zeroturnaround.eclipse.remoting
Installing org.zeroturnaround.eclipse.wtp
Installing org.zeroturnaround.eclipse.wtp.feature.feature.group
Installing org.zeroturnaround.eclipse.wtp.feature.feature.jar
Installing org.zeroturnaround.eclipse.wtp.websphere
Installing tooling.org.eclipse.update.feature.default
Installing tooling.osgi.bundle.default
Installing tooling.source.default
Installing toolingepp.package.jee.application
Installing toolingepp.package.jee.config.win32.win32.x86_64
Installing toolingepp.package.jee.configuration
Installing toolingepp.package.jee.executable.win32.win32.x86_64
Installing toolingepp.package.jee.ini.win32.win32.x86_64
Installing toolingorg.eclipse.equinox.launcher
Installing toolingorg.eclipse.equinox.launcher.win32.win32.x86_64
Installing toolingorg.eclipse.platform.configuration
Installing toolingorg.eclipse.platform.ide.application
Installing toolingorg.eclipse.platform.ide.config.win32.win32.x86_64
Installing toolingorg.eclipse.platform.ide.configuration
Installing toolingorg.eclipse.platform.ide.executable.win32.win32.x86_64
Installing toolingorg.eclipse.platform.ide.ini.win32.win32.x86_64
Installing toolingwin32.win32.x86_64org.eclipse.core.runtime
Installing toolingwin32.win32.x86_64org.eclipse.equinox.common
Installing toolingwin32.win32.x86_64org.eclipse.equinox.ds
Installing toolingwin32.win32.x86_64org.eclipse.equinox.event
Installing toolingwin32.win32.x86_64org.eclipse.equinox.p2.reconciler.dropins
Installing toolingwin32.win32.x86_64org.eclipse.equinox.simpleconfigurator
Installing toolingwin32.win32.x86_64org.eclipse.update.configurator
Preparing to commit the provisioning operation.
Committing the provisioning operation.
Performing Eclipse Ini -Doomph.setup=true
Changing C:\Java\Eclipse\standard\eclipse\eclipse.ini (-Doomph.setup=true)
Performing Eclipse Ini -Xmx 4096m
Changing C:\Java\Eclipse\standard\eclipse\eclipse.ini (-Xmx 4096m)
Performing Resource Creation configuration:/.settings/org.eclipse.ui.ide.prefs
Creating file:/C:/Java/Eclipse/standard/eclipse/configuration/.settings/org.eclipse.ui.ide.prefs
Performing Resource Copy https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/conf/settings.xml --> file:/C:/Java/
Copying resource https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/conf/settings.xml to file:/C:/Java//settings.xml
Performing post bootstrap tasks
Changing C:\Java\Eclipse\standard\eclipse\eclipse.ini (-Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest)
Changing C:\Java\Eclipse\standard\eclipse\eclipse.ini (-Doomph.redirection.index.redirection=index:/->https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/)
Changing C:\Java\Eclipse\standard\eclipse\eclipse.ini (-Doomph.redirection.index.location.redirection=http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/->https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/)
Took 30 seconds.
Press Finish to close the dialog.
|
|
|
| Re: Project import via project catalog [message #1703040 is a reply to message #1703039] |
Tue, 28 July 2015 08:04 |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Matthias,
Does the confirmation page on the installer include the workspace task
as in this image (where it's shown as the first task):
More comments below.
On 28/07/2015 9:58 AM, Matthias Nicklisch wrote:
> Hi,
>
>> > I have tried not starting the installation after the installer has
>> > finished. But at this point there is no workspace.
>> The installer should save the workspace.setup.
>> > The workspace is created when I start the installation. And then an
>> empty workspace.setup is created if there isn't already a
>> workspace.setup there.
> No, there is no workspace folder at all.
So that's a fundamental problem.
> I have defined a fixed value for the location of my workspace in my
> project setup. And when I start the installation the workspace is
> created there. But there is no workspace folder at all before starting
> the installation.
Unless that's addressed, nothing else is really worth discussing. The
workspace.setup must be written by the installer and must have the
Stream specified.
>
>> > The plugins which are installed which I reference in my post are >
>> solely defined in the project setup, not in the product setup. Those
>> > are plugins which are not part of a standard eclipse installation.
>> This isn't an issue of the Workspace task being missing?
> Regarding the plugins, no, that isn't an issue. Look at my list of
> tasks I have defined in my project setup
> (https://www.eclipse.org/forums/index.php?t=msg&th=1068840&goto=1702974&#msg_1702974)
> It seems that only step 1, 2 and 4 are executed by the installer.
> And that has the Workspace task in it now? I.e., that clone has pulled
> so it's not stale and the Project Catalog there has the Workspace task
> in it? (Of course you know that sharing clones across multiple IDEs
> that might be running at the same time is a bad idea.)
> I know that sharing those clones across multiple IDEs is a bad idea
> and I wouldn't use that. It is only for testing oomph. I just have to
> work on other things at the same time =)
My question is specifically about the Workspace task.
>
>
> Here is the log of the installer when I run it. I have removed some
> lines where he installs the standard eclipse packages to keep it small:
> And you can see there, for example the installation of the
> *org.zeroturnaround packages, those are defined in the project setup.
>
>
Yes, but you've said nothing about my questions about the Workspace task.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Project import via project catalog [message #1703041 is a reply to message #1703040] |
Tue, 28 July 2015 08:07 |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Here is image as attachment.
On 28/07/2015 10:04 AM, Ed Merks wrote:
> Matthias,
>
> Does the confirmation page on the installer include the workspace task
> as in this image (where it's shown as the first task):
>
>
>
> More comments below.
>
>
> On 28/07/2015 9:58 AM, Matthias Nicklisch wrote:
>> Hi,
>>
>>> > I have tried not starting the installation after the installer has
>>> > finished. But at this point there is no workspace.
>>> The installer should save the workspace.setup.
>>> > The workspace is created when I start the installation. And then
>>> an empty workspace.setup is created if there isn't already a
>>> workspace.setup there.
>> No, there is no workspace folder at all.
> So that's a fundamental problem.
>> I have defined a fixed value for the location of my workspace in my
>> project setup. And when I start the installation the workspace is
>> created there. But there is no workspace folder at all before
>> starting the installation.
> Unless that's addressed, nothing else is really worth discussing. The
> workspace.setup must be written by the installer and must have the
> Stream specified.
>>
>>> > The plugins which are installed which I reference in my post are >
>>> solely defined in the project setup, not in the product setup. Those
>>> > are plugins which are not part of a standard eclipse installation.
>>> This isn't an issue of the Workspace task being missing?
>> Regarding the plugins, no, that isn't an issue. Look at my list of
>> tasks I have defined in my project setup
>> (https://www.eclipse.org/forums/index.php?t=msg&th=1068840&goto=1702974&#msg_1702974)
>> It seems that only step 1, 2 and 4 are executed by the installer.
>> And that has the Workspace task in it now? I.e., that clone has
>> pulled so it's not stale and the Project Catalog there has the
>> Workspace task in it? (Of course you know that sharing clones across
>> multiple IDEs that might be running at the same time is a bad idea.)
>> I know that sharing those clones across multiple IDEs is a bad idea
>> and I wouldn't use that. It is only for testing oomph. I just have to
>> work on other things at the same time =)
> My question is specifically about the Workspace task.
>>
>>
>> Here is the log of the installer when I run it. I have removed some
>> lines where he installs the standard eclipse packages to keep it small:
>> And you can see there, for example the installation of the
>> *org.zeroturnaround packages, those are defined in the project setup.
>>
>>
> Yes, but you've said nothing about my questions about the Workspace task.
Attachment: Capture.PNG
(Size: 34.90KB, Downloaded 237 times)
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| | |
| Re: Project import via project catalog [message #1703197 is a reply to message #1703156] |
Wed, 29 July 2015 09:30 |
Matthias Nicklisch
Messages: 20
Registered: July 2015 |
Junior Member |
|
|
Hello,
yes, I do remember that you mentioned that, and I added that part back then.
My project catalog looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<setup:ProjectCatalog
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
name="org.eclipse"
label="mycompany">
<setup:WorkspaceTask
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
id="workspace"/>
<setupTask
xsi:type="setup:ResourceCreationTask"
content="MAX_RECENT_WORKSPACES=5
RECENT_WORKSPACES=${workspace.location|property}
RECENT_WORKSPACES_PROTOCOL=3
SHOW_WORKSPACE_SELECTION_DIALOG=true
eclipse.preferences.version=1"
targetURL="configuration:/.settings/org.eclipse.ui.ide.prefs"/>
<project name="mycompanyGitContainer"
label="mycompany Projects">
<project href="https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/mycompany_Standard_Mars.setup#/"/>
<project href="https://gitlab.mycompany.de/dev-tools/oomph-installer/raw/develop/setups/emptyProject.setup#/"/>
</project>
<project name="mycompanyOwnContainer"
label="Own Projects">
<project
href="user:/org.eclipse.projects.setup?name='user.project',label='<User>',description='A
container project for local user projects that are virtual members of
the Eclipse.org project catalog'#/"/>
</project>
<description></description>
</setup:ProjectCatalog>
It was there all the time. I think what's a problem here, is that I don't see the workspace task in the setup view (where I can create new childs and siblings in the setup). There should be a workspace task visible, correct? There is no, see the attached picture to see what I see. Maybe there is something wrong here and the setup doesn't recognize this task.
-
Attachment: screen.png
(Size: 13.40KB, Downloaded 1438 times)
|
|
| |
Goto Forum:
Current Time: Thu Apr 25 08:25:56 GMT 2024
Powered by FUDForum. Page generated in 0.05192 seconds |
] 
Search
Help
Register
Login
Home
