Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » Oomph issues with Project Set(I cannot use properly Git-clone and Project-set tasks to organize user's workspace. )
Oomph issues with Project Set [message #1738042] Fri, 15 July 2016 10:11 Go to next message
Patrik Suzzi is currently offline Patrik SuzziFriend
Messages: 91
Registered: June 2010
Location: Urdorf, Switzerland
Member

Hallo,

I'm creating an Oomph project setup for JSDT, and I have issues importing projects, in project sets, from multiple repositories.

I declare working sets, for the first repository of the project, and it works; but when I declare working sets related to projects on the second repo, this does not work. (see image, top, left)

After installing, you see the only the "JSDT" projects sets are filled with projects. But the WST project sets are not. (see image, top right)

I checked, and the projects are correctly cloned with Git/Gerrit.
(see image, bottom, right)

http://i.imgur.com/ZbL2Z5p.png

So, my question is: how can I import the projects from the second repository () in their projectsets ?


Thanks in advance for spending time on this.

Attached, you'll find also the complete .setup


Regards.
Patrik
  • Attachment: JSDT.setup
    (Size: 14.75KB, Downloaded 145 times)
Re: Oomph issues with Project Set [message #1738055 is a reply to message #1738042] Fri, 15 July 2016 12:11 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 31032
Registered: July 2009
Senior Member
Patrik,

The question is kind of misleading. You don't import projects into
their working sets. You import projects into the workspace, the
working set task organizes the project in the workspace into working
sets. So the problem is you've done nothing to import projects from
the second clone into your workspace.

You need a second source locator in the targlets task:

<?xml version="1.0" encoding="UTF-8"?>
<xmi:XMI xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:resources="http://www.eclipse.org/oomph/resources/1.0"
xsi:schemaLocation="http://www.eclipse.org/oomph/resources/1.0
http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/models/Resources.ecore">
<resources:SourceLocator
rootFolder="${git.clone.jsdt.location}"/>
<resources:SourceLocator
rootFolder="${git.clone.wtp.sourceediting.location}"/>
</xmi:XMI>

Note that I have both set not to search for nested projects. All kinds
of projects that are nested within test projects show up otherwise. I'm
pretty sure you don't need that.

You also have both a targlet task and a target definition task. That
doesn't make sense. You can only have on active target. Better would be
to delete your target definition task and make sure the fast pooled
targlet task is working well. Also, for your API baseline, it would
also be better (in my opinion) to use a targlet task to define the API
baseline. Look in the Platform.setup to see how that's done. The base
definition is built into the Eclipse.org Project catalog.

<?xml version="1.0" encoding="UTF-8"?>
<xmi:XMI 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.targlets="http://www.eclipse.org/oomph/setup/targlets/1.0"
xsi:schemaLocation="http://www.eclipse.org/oomph/setup/targlets/1.0
http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/models/SetupTarglets.ecore">
<setup:VariableTask
name="eclipse.api.baseline.target.platform"
value="Neon"
storageURI="scope://Workspace"/>
<setup.targlets:TargletTask
targetName="Modular API Baseline Target"
activateTarget="false">
<targlet
name="Platform"
activeRepositoryList="${eclipse.api.baseline.target.platform}"
includeSources="false">
<requirement
name="org.eclipse.platform.feature.group"/>
<requirement
name="org.eclipse.jdt.feature.group"/>
<requirement
name="org.eclipse.pde.feature.group"/>
<requirement
name="org.eclipse.equinox.executable.feature.group"/>
</targlet>
</setup.targlets:TargletTask>
</xmi:XMI>



On 15.07.2016 12:11, Patrik Suzzi wrote:
> So, my question is: how can I import the projects from the second repository () in their projectsets ?
Re: Oomph issues with Project Set [message #1738075 is a reply to message #1738055] Fri, 15 July 2016 15:09 Go to previous messageGo to next message
Patrik Suzzi is currently offline Patrik SuzziFriend
Messages: 91
Registered: June 2010
Location: Urdorf, Switzerland
Member

Ed,

That was a great suggestion!
Now, I have good control on ProjectSets, and I'm also using a Modular API Baseline, and a Modular Target. (see attachment)

http://i.imgur.com/PRPB1Gi.png

I have another question about imported projects, and project sets:
At the end of the import, Oomph opened the "desired" projects and put them into project sets.
Now, I'd like to get rid of the projects not included in the working sets. Is there a way to "un-import" the projects not listed in any of the project-sets?

Regards,
Patrik
  • Attachment: JSDT.setup
    (Size: 14.93KB, Downloaded 163 times)
Re: Oomph issues with Project Set [message #1738080 is a reply to message #1738075] Fri, 15 July 2016 15:34 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 31032
Registered: July 2009
Senior Member
Partik,

No, you have to control the projects in the workspace via the source
locator. You could do that on the source locator either by excluding
paths (these are repository relative paths) or by defining a predicate
for what should be included. Note be careful with your same repository
as predicate that it must list a project that will actually be in the
workspace so if you exclude org.eclipse.json that won't work well.


On 15.07.2016 17:09, Patrik Suzzi wrote:
> Ed,
>
> That was a great suggestion!
> Now, I have good control on ProjectSets, and I'm also using a Modular API Baseline, and a Modular Target. (see attachment)
>
>
>
> I have another question about imported projects, and project sets:
> At the end of the import, Oomph opened the "desired" projects and put them into project sets.
> Now, I'd like to get rid of the projects not included in the working sets. Is there a way to "un-import" the projects not listed in any of the project-sets?
>
> Regards,
> Patrik
Re: Oomph issues with Project Set [message #1738081 is a reply to message #1738080] Fri, 15 July 2016 15:35 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 31032
Registered: July 2009
Senior Member
Sorry for the name typo!


On 15.07.2016 17:34, Ed Merks wrote:
> Partik,
>
> No, you have to control the projects in the workspace via the source
> locator. You could do that on the source locator either by excluding
> paths (these are repository relative paths) or by defining a predicate
> for what should be included. Note be careful with your same
> repository as predicate that it must list a project that will actually
> be in the workspace so if you exclude org.eclipse.json that won't work
> well.
>
>
> On 15.07.2016 17:09, Patrik Suzzi wrote:
>> Ed,
>>
>> That was a great suggestion!
>> Now, I have good control on ProjectSets, and I'm also using a Modular
>> API Baseline, and a Modular Target. (see attachment)
>>
>>
>>
>> I have another question about imported projects, and project sets:
>> At the end of the import, Oomph opened the "desired" projects and put
>> them into project sets.
>> Now, I'd like to get rid of the projects not included in the working
>> sets. Is there a way to "un-import" the projects not listed in any of
>> the project-sets?
>>
>> Regards,
>> Patrik
>
Re: Oomph issues with Project Set [message #1738084 is a reply to message #1738081] Fri, 15 July 2016 15:41 Go to previous messageGo to next message
Patrik Suzzi is currently offline Patrik SuzziFriend
Messages: 91
Registered: June 2010
Location: Urdorf, Switzerland
Member

(NP; often I'm doing the same Very Happy)

Ed,
Thanks for the precious suggestion.
Actually, I read Christian Pontesegger Q&A, and I knew I could exclude projects "by directory", but I was hoping for something to "automagically exclude prjs".

Best Regards
Patrik

[Updated on: Fri, 15 July 2016 15:42]

Report message to a moderator

Re: Oomph issues with Project Set [message #1738086 is a reply to message #1738084] Fri, 15 July 2016 15:44 Go to previous message
Ed Merks is currently offline Ed MerksFriend
Messages: 31032
Registered: July 2009
Senior Member
Patrik,

A predicate is likely easier because it seems like a long list of things
to exclude.


On 15.07.2016 17:41, Patrik Suzzi wrote:
> NP; I also often do the same error :d
> Ed, Thanks for the precious suggestion. Actually, I read Christian
> Pontesegger Q&A, and I knew I could exclude projects "by directory",
> but I was hoping for something to "automagically exclude prjs".
> Best Regards
> Patrik
Previous Topic:Customize the git config in a GitCloneTask
Next Topic:Eclipse installer silently fails on Windows 7 64 bit
Goto Forum:
  


Current Time: Sat Apr 04 16:38:58 GMT 2020

Powered by FUDForum. Page generated in 0.02022 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top