|
| Re: Build working set always builds entire project [message #174025 is a reply to message #172910] |
Mon, 09 October 2006 19:36   |
Eclipse User |
|
|
|
Originally posted by: markackerman.hotmail.com
We're getting similiar behavior with Build All. Whats happening to us is
we have two Projects open that are just different versions of the same
application. So both Projects contain almost exactly the same classfiles.
When we go and build the development Project Eclipse also builds the other
Project. It didn't used to do that prior to 3.2. There are no
dependencies between the two versions of the Projects.
|
|
|
| Re: Build working set always builds entire project [message #174783 is a reply to message #172910] |
Fri, 13 October 2006 20:47 |
| Eclipse User |
|
|
|
Originally posted by: john.eclipsefaq.org
Build working set has always built entire projects. This has not
changed in Eclipse 3.1 or 3.2. Here is the planning document describing
the original feature:
http://www.eclipse.org/eclipse/platform-core/documents/scope d_builds.html
--
David Karr wrote:
> Along when I was using Eclipse 3.1.1 and 3.1.2, I used to use "Build
> Working Set", selecting only a portion of my project. This worked
> pretty well. Somewhere around 3-4 weeks ago, I upgraded to Eclipse
> 3.2. Sometime around that time, I noticed that "Build Working Set"
> started building the entire project. I cannot get it to only build the
> working set now. I did some obvious searches in the bugs list, and I
> didn't see anything about this.
>
> Is there something new in Eclipse 3.2 that might prevent this from
> working as I expect?
>
|
|
|
| Re: Build working set always builds entire project [message #174818 is a reply to message #174025] |
Sat, 14 October 2006 17:44 |
| Eclipse User |
|
|
|
Originally posted by: wayne.beaton._NOSPAM_eclipse.org
Mark Ackerman wrote:
> We're getting similiar behavior with Build All. Whats happening to us
> is we have two Projects open that are just different versions of the
> same application. So both Projects contain almost exactly the same
> classfiles. When we go and build the development Project Eclipse also
> builds the other Project. It didn't used to do that prior to 3.2. There
> are no dependencies between the two versions of the Projects.
>
Perhaps I'm misunderstanding... I expect "Build All" to build all projects.
Wayne
|
|
|
| Re: Build working set always builds entire project [message #174965 is a reply to message #174818] |
Mon, 16 October 2006 16:39 |
| Eclipse User |
|
|
|
Originally posted by: markackerman.hotmail.com
Wayne Beaton wrote:
> Mark Ackerman wrote:
>> We're getting similiar behavior with Build All. Whats happening to us
>> is we have two Projects open that are just different versions of the
>> same application. So both Projects contain almost exactly the same
>> classfiles. When we go and build the development Project Eclipse also
>> builds the other Project. It didn't used to do that prior to 3.2. There
>> are no dependencies between the two versions of the Projects.
>>
> Perhaps I'm misunderstanding... I expect "Build All" to build all projects.
> Wayne
In releases prior to 3.2 when I hit ctrl-b to build the class that I've
been working on, it built all the classes that have been modified or that
had dependencies on the classes that have been modified (not sure exactly
how it determines what the dependencies are, and this might not be the
correct description of what its really doing).
In 3.2 I can modify a class in one project and hit ctrl-b to build it and
Eclipse will that class and build the entire other project, every time.
i.e. Modify A.java in project Foo and project Bar will build. Modify
B.java in project Foo and project Bar will build. Since the projects have
something like 3000+ classes building the entire Bar project is not
instantaneous.
This is definitely new behavior in 3.2 (or versions prior to 3.2 weren't
working the way they were supposed to). My solution for now is to close
the other project (which I have to open constantly and then close again)
Or maybe a better question is how do I get Eclipse to only build the
classfiles that have been changed without building other projects that
haven't changed?
Mark
|
|
|
| Re: Build working set always builds entire project [message #175173 is a reply to message #174965] |
Tue, 17 October 2006 23:28 |
| Eclipse User |
|
|
|
Originally posted by: eclipse4.rizzoweb.com
Mark Ackerman wrote:
> Or maybe a better question is how do I get Eclipse to only build the
> classfiles that have been changed without building other projects that
> haven't changed?
That is the default behavior - have you turned off the Build
Automatically in the Preferences? If so, whatever your reasons for doing
so, you'll have to weigh them against missing the benefits of
incremental compilation.
Hope this helps,
Eric
|
|
|
| Re: Build working set always builds entire project [message #175244 is a reply to message #175173] |
Wed, 18 October 2006 16:10 |
| Eclipse User |
|
|
|
Originally posted by: markackerman.hotmail.com
Oh yeah turned that off long ago. We often are making changes across many
classes and everyone here found it really annoying to have Eclipse start
building when you know you're not even close to being ready. So none of
the programmers here like the automatic build and we've all turned it off.
|
|
|
| Re: Build working set always builds entire project [message #175558 is a reply to message #175244] |
Thu, 19 October 2006 16:35 |
| Eclipse User |
|
|
|
Originally posted by: eclipse4.rizzoweb.com
Mark Ackerman wrote:
> Oh yeah turned that off long ago. We often are making changes across
> many classes and everyone here found it really annoying to have Eclipse
> start building when you know you're not even close to being ready. So
> none of the programmers here like the automatic build and we've all
> turned it off.
>
Strange preference, since the auto build is usually non-intrusive and
gives immediate feedback about what is left to do. The incremental
compilation is one of the major selling points of Eclipse and its
predecessors.
Making lots of changes across many classes is kind of irrelevant because
Eclipse will only rebuild what is absolutely necessary. I do that all
the time; sometimes I ignore the Problems view and error markers for a
while when I'm the middle of a broad change, but that is not enough to
drive me to disable the incremental compilation.
Anyway, as I said you will have to decide if turning it off is worth the
cost of doing so; specifically, having more monolithic builds. It sounds
like you want incremental/partial compilation but don't want to turn it
on - in other words sounds a bit contradictory.
Hope this helps,
Eric
|
|
|
| Re: Build working set always builds entire project [message #175665 is a reply to message #175558] |
Thu, 19 October 2006 21:55 |
| Eclipse User |
|
|
|
Originally posted by: markackerman.hotmail.com
Its not just me, none of the other developers here like it either. Maybe
we're still stuck in the JBuilder mindset from years ago.
Actually it seems to build just fine with it off, well up until the move
to 3.2.
I deleted the offending project (the one that was getting rebuilt all the
time) and recreated it with exactly the same settings (near as I can tell)
and Eclipse seems to behaving like it was prior to 3.2. In other words
its back to only building what needs to be built, instead of everything in
that project all the time.
So it appears that something in the migration of the project from 3.1 to
3.2 seems to have been confusing Eclipse.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03628 seconds
] 
Search
Help
Register
Login
Home
