|
Re: Why does "Build Working Set" always build my entire project? [message #187859 is a reply to message #187850] |
Sat, 13 January 2007 00:13 |
Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"David Karr" <david.karr@wamu.net> wrote in message
news:35cca794753c541606080c6c15cee0b4$1@www.eclipse.org...
>I may have asked about this before, but why is that when I attempt to
>"Build Working Set", it ignores me and attempts to build the entire
>project? I don't know if I've ever seen this actually work.
>
> I've carefully viewed the working set I want to build, making sure it only
> specifies a small subset of the project, and carefully selected that
> working set when I make the "Build Working Set" request, but it still
> spends many minutes building other packages outside of my working set.
>
> I'm on Eclipse 3.2.1.
I was under the impression that Working Set applied to collections of
projects, not to subsets of projects. I don't remember seeing any code
within the Java builder that suggests that it pays attention to working set
when deciding what to build within a single project. Perhaps I'm wrong
about that.
|
|
|
|
Re: Why does "Build Working Set" always build my entire project? [message #187874 is a reply to message #187866] |
Sat, 13 January 2007 04:49 |
Eclipse User |
|
|
|
Originally posted by: wegener.cboenospam.com
David Karr wrote:
> If that's the case, it's pretty misleading. The "Working Set"
> specification dialog allows you to drill down well below the level of
> the project, specifying individual subprojects.
>
In order to build classes in your Working Set, any class referenced by
classes in your Working Set need to be built as well. Depending on the
classes referenced outside your Working Set, this could be a significant
portion of your project. Is this possibly what you are seeing?
|
|
|
Powered by
FUDForum. Page generated in 0.08275 seconds