Eclipse Community Forums: Eclipse Platform » workingSets and headless environments

Home » Eclipse Projects » Eclipse Platform » workingSets and headless environments

workingSets and headless environments [message #335116]

Mon, 23 March 2009 12:35

Eclipse User

Build ID: 3.4

We (a product building on Eclipse) provide an environment for performing
headless, non UI builds, of Eclipse based projects. Included is an Ant
task which does the equivalent of File > Import > Team Project Set to
import a PSF file into the workspace. When importing a PSF file including
working sets, there does not appear to be any way to load the working set
into the workspace without interacting with UI based plugins. Note: the
projects from the PSF file can be loaded, just not the workingSets.

As this product runs in a completely headless manor and does not include
UI plugins it doesn't appear that the workingSets can be imported.

Questions:
1) Is there a means to headlessly import the working sets that I'm
missing, or a workaround to achieve this?

2) Is there reasoning, other than historical, for the working set to be
tied to UI code?

Any help/insight is appreciated,
mike.

Re: workingSets and headless environments [message #335134 is a reply to message #335116]

Tue, 24 March 2009 02:02

Eclipse User

Given that the WorkingSet API is defined by workbench:

> 1) Is there a means to headlessly import the working sets that I'm
> missing, or a workaround to achieve this?

Nope.

> 2) Is there reasoning, other than historical, for the working set to be
> tied to UI code?

WorkingSets were created as an easy means of filterning and/or grouping
the UI elements.

BTW why do you want to put the projects in a working set to build them? You
can do it even without working set right?

- Prakash
--
http://blog.eclipse-tips.com

Re: workingSets and headless environments [message #335163 is a reply to message #335134]

Tue, 24 March 2009 11:03

Eclipse User

Thanks for the prompt response!

The use case that my customer has is one that setups a developer
environment based on the headless script. It would be along the lines of:
1) Execute script pointing at a clean workspace
2) Set workspace preferences by importing an .epf or other.
3) Import projects from version control system using a .psf file.
3a) This would include setting up workingSets as defined by the same .psf
file.

So this particular use case isn't actually doing a build, it's doing a
setup.

But thinking longer term. If the workingSets weren't tied to UI, they
could potentially be used for defining sets that could be used to perform
builds or other non UI based actions.

- mike.

Re: workingSets and headless environments [message #335186 is a reply to message #335163]

Wed, 25 March 2009 10:37

Eclipse User

> So this particular use case isn't actually doing a build, it's doing a
> setup

Hack: After 3(a) is done, make your script to edit the <workspace
location> \.metadata\.plugins\org.eclipse.ui.workbench\workingsets.xml and
add the working set details.

> But thinking longer term. If the workingSets weren't tied to UI, they
> could potentially be used for defining sets that could be used to perform
> builds or other non UI based actions.

You might have to raise a bug for that.

- Prakash
--

http://blog.eclipse-tips.com
"Mike Melick" <melickm@ca.ibm.com> wrote in message
news:dd9e3d41b8f7df18719a4329607b8995$1@www.eclipse.org...
>
> Thanks for the prompt response!
>
> The use case that my customer has is one that setups a developer
> environment based on the headless script. It would be along the lines of:
> 1) Execute script pointing at a clean workspace
> 2) Set workspace preferences by importing an .epf or other. 3) Import
> projects from version control system using a .psf file. 3a) This would
> include setting up workingSets as defined by the same .psf file.
> So this particular use case isn't actually doing a build, it's doing a
> setup.
> But thinking longer term. If the workingSets weren't tied to UI, they
> could potentially be used for defining sets that could be used to perform
> builds or other non UI based actions.
> - mike.
>
>

Re: workingSets and headless environments [message #335202 is a reply to message #335116]

Wed, 25 March 2009 18:23

Eclipse User

Mike Melick skrev:

> headless, non UI builds, of Eclipse based projects. Included is an Ant
> task which does the equivalent of File > Import > Team Project Set to
> import a PSF file into the workspace. When importing a PSF file

I cannot answer your question, but I would like to know more about the
ant task to automate the import projectset? Are you using ant4eclipse
or something else?

Thanks for sharing :)

/Thorbjørn

Previous Topic:	Find a class
Next Topic:	why the old bundle loaded

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Mar 12 00:22:53 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter