Eclipse Community Forums: Oomph » Working Sets Tasks: Use case for prefix?

Home » Eclipse Projects » Oomph » Working Sets Tasks: Use case for prefix?

Working Sets Tasks: Use case for prefix? [message #1771686]

Tue, 29 August 2017 10:04

Eclipse User

I ran into an issue when I had a workspace with 2 project setups imported. Each has a working sets task, but one of the working sets disappeared when I manually ran the setup tasks. It turned out that one working sets task had no prefix attribute set while the other had a string there. Removing the prefix fixed the issue, and now all working sets show up all the time.

I assume that there is a use case for having a prefix set when I have multiple working set tasks, but I can't think of one.

I'd like to understand when I should set the prefix, and what may be a use case for having different values for this attribute.

Re: Working Sets Tasks: Use case for prefix? [message #1771698 is a reply to message #1771686]

Tue, 29 August 2017 11:52

Eclipse User

Even if one isn't set, the value is inferred from the containing scope (ensuring uniqueness). An explicit attribute was added for https://bugs.eclipse.org/bugs/show_bug.cgi?id=497278 but generally you shouldn't need one.

Previous Topic:	org.eclipse.mylyn.builds.core [1.0.0,2.0.0)' but it could not be found
Next Topic:	How to add a user specific xml-catalog entry with oomph?

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jul 07 18:47:41 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter