On 24/05/2015 12:57 PM, Aleksandar Toshovski wrote:
> What I achieved so far works with the custom catalogs/projects. The
> only problem I have is creating of files in the downloaded repository
> before importing them into eclipse. Can you give me some hints how to
> make this work? 1. Download repository
> 2. Add files into the repository (.project and .cproject)
I see you have this:

<setupTask
xsi:type="setup:ResourceCreationTask"
id="project"
excludedTriggers="STARTUP MANUAL"
content="......"
targetURL="${git.clone.gitcentral.erp}/.project"
encoding="UTF-8">
<description>Create .project file</description>

So of course the targetURL expands to the web-hosted location of the
repository. Here's an example from the Platform.setup (in which one
needs to copy one of the many .classpath_* files to be the one
.classpath file that matches the current windowing system:

<?xml version="1.0" encoding="UTF-8"?>
<setup:ResourceCopyTask
xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:setup="http://www.eclipse.org/oomph/setup/1.0"
excludedTriggers="BOOTSTRAP"
sourceURL="${git.clone.platform.swt.location|uri}/bundles/org.eclipse.swt/.classpath_${osgi.ws}"
targetURL="${git.clone.platform.swt.location|uri}/bundles/org.eclipse.swt/.classpath"/>

I.e., so in your case, you would use
${git.clone.gitcentral.erp.location|uri} to specify the file URI for the
clone's local disk location.

> 3. Import repository projects
>
> Here is my view about support:
> I don't like the approach with adding of projects in the projects
> catalog for every user.
No, that's why we maintain a catalog. You can ask for your projects to
be included in the Eclipse catalog if it's an Eclipse project or in the
Github catalog if it's a Github project that is no also an Eclipse project.

> If I have a C-Project and the developer choose Eclipse Classic
> Package, the project configuration won't work at all.
That should not be the case. Your project description should include
the high level features that it needs. So it should specify it needs
CDT and then no matter what product is chosen CDT will be added to it.
(Note how the product catalog even has a bare bones Eclipse Platform
product, which does not include Egit, JDT, PDE, or really anything
useful for much of anything at all. You should design your project
description so that it ensures the necessary features are installed,
rather than assuming a certain product (with the dependencies implied by
the product) will be chosen first.

> So I need a way map project to eclipse package
No, it's best to avoid that.
> and also I need to be sure, that the configuration works with this
> package. That's way i chose to use a own product catalog with custom
> project catalog. So I can control remotely the possible combinations
> between eclipse package and a project.
I think this is the wrong approach. Better would be to author your
project so it works with the Eclipse Platform product as a starting
point, and when you get that right, it should be possible for the end
user to choose any product and still end up with a result that contains
what your project needs and that contains what that end-user also
wants. E.g., someone might want to work with Java projects and C
projects, and of course that's possible with Eclipse, so best if you
enable that rather than try to constrain what's possible...