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 |
Patrik Suzzi Messages: 2 Registered: February 2018 |
Junior 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)
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 194 times)
|
|
| |
Re: Oomph issues with Project Set [message #1738075 is a reply to message #1738055] |
Fri, 15 July 2016 15:09 |
Patrik Suzzi Messages: 2 Registered: February 2018 |
Junior 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)
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 212 times)
|
|
|
Re: Oomph issues with Project Set [message #1738080 is a reply to message #1738075] |
Fri, 15 July 2016 15:34 |
Ed Merks Messages: 33137 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
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Re: Oomph issues with Project Set [message #1738081 is a reply to message #1738080] |
Fri, 15 July 2016 15:35 |
Ed Merks Messages: 33137 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
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| |
Re: Oomph issues with Project Set [message #1738086 is a reply to message #1738084] |
Fri, 15 July 2016 15:44 |
Ed Merks Messages: 33137 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
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Goto Forum:
Current Time: Fri Apr 19 14:37:12 GMT 2024
Powered by FUDForum. Page generated in 0.03169 seconds
|