| Build hell...can some help?? [message #213868] |
Fri, 19 March 2004 22:30  |
Eclipse User |
|
|
|
Originally posted by: drathnow.yahoo.com
I'm starting to lose my hair over trying to figure out how Eclipse
determines
which projects to build.
I have a workspace with several projects. These projects have a reference
tree that contains no cycles. I was having a hell of a time trying to build
all
the project together so I closed all projects and opened them one at a time
and built them. That worked.
Then I made a change to a file in one project and tried to build just that
project. Eclipse told me it could not build the project until one of the
project's referenced projects was rebuilt; however, nothing changed in
the dependant project!!!
I then tried to do a "Rebuild All" and ended up with a whole bunch of
"The project cannot be built until XXX is rebuilt. Rebuilding all projects
is recommended"...but the rebuild won't work!!
Another odd bit of behavior I've seen is when I try to run a unit test,
Eclipse seem to feel that referenced project need to be built before
the current project is built and the test run. Can someone explain
this to me? Why can't I just change a file, build and run it without
having to rebuilt half my system!?!?
|
|
|
|
|
| Re: Build hell...can some help?? [message #214481 is a reply to message #214189] |
Mon, 22 March 2004 14:59  |
| Eclipse User |
|
|
|
Originally posted by: drathnow.wrx-ca.com
> It sounds like you have a prerequisite project that has errors with its
> build path.
Well, that's what annoying, there are no errors. I can do a "rebuild
all" and everything builds, if I change one file in any project, Eclipse
is attemping to rebuild one or more downstream projects. It then
breaks on these because it claims other dependent projects have to
be rebuilt, and on it goes until I do a complete rebuild. This just
seems broken. It shouldn't have to rebuild downstream projects
that have no changes.
can I assume that the behavior I'm seeing is normal? That
is, when you rebuild a project, Eclipse attempts to rebuild
any/all projects it depends on? If so, I really hope this changes!!
"John Arthorne" <John_Arthorne@oti.com_> wrote in message
news:405DDEEF.6050401@oti.com_...
> It sounds like you have a prerequisite project that has errors with its
> build path. If a project has build path errors (such as referencing a
> non-existent JAR or project), the Java builder will not even attempt to
> build it. All downstream projects will also fail to build until the
> build path errors are resolved. Look for red X's on the Properties >
> Java Build Path dialog for each of your projects.
>
> I should add that some of the "stupidity" of builders will be improved
> in 3.0 M8. Building a single project will now automatically build all
> pre-requisite projects before trying to build the specified "target".
> This now has a more of a "make" feel: just specify what end result you
> want built, and the system will take care of figuring out exactly which
> projects need building. We're looking for feedback on these changes, so
> please try it out and send comments to the platform-core-dev mailing list.
> --
>
>
> Dave Rathnow wrote:
> > I'm starting to lose my hair over trying to figure out how Eclipse
> > determines
> > which projects to build.
> >
> > I have a workspace with several projects. These projects have a
reference
> > tree that contains no cycles. I was having a hell of a time trying to
build
> > all
> > the project together so I closed all projects and opened them one at a
time
> > and built them. That worked.
> >
> > Then I made a change to a file in one project and tried to build just
that
> > project. Eclipse told me it could not build the project until one of
the
> > project's referenced projects was rebuilt; however, nothing changed in
> > the dependant project!!!
> >
> > I then tried to do a "Rebuild All" and ended up with a whole bunch of
> > "The project cannot be built until XXX is rebuilt. Rebuilding all
projects
> > is recommended"...but the rebuild won't work!!
> >
> > Another odd bit of behavior I've seen is when I try to run a unit test,
> > Eclipse seem to feel that referenced project need to be built before
> > the current project is built and the test run. Can someone explain
> > this to me? Why can't I just change a file, build and run it without
> > having to rebuilt half my system!?!?
> >
> >
>
|
|
|
|
| Re: Build hell...can some help?? [message #214921 is a reply to message #214576] |
Tue, 23 March 2004 11:19 |
| Eclipse User |
|
|
|
Originally posted by: drathnow.wrx-ca.com
"John Arthorne" <John_Arthorne@oti.com_> wrote in message
news:405F6565.6020406@oti.com_...
> Actually, just the opposite. Currently, if you select "Rebuild Project"
> it does NOT rebuild any projects it depends on.
I guess that's my point: that's not what I'm seeing. If I select "Rebuild
Project",
Eclipse won't build the project because it says a dependant projects
has to be rebuilt first. And this is right after a successful "Rebuild All"
so
everything should be freshly rebuilt and NOT require a rebuild.
There is a related behavior that I've observed: when rebuilding one of the
projects in my workspace that has no dependancies on any other project,
Eclipse is rebuilding two other projects in my workspace. These project
have no relation to the project I'm working on. Can you explain this?
> This is bad, because if
> there are errors in projects it depends on, the build will fail. The
> user is then forced to manually walk up the project prerequisite chain
> and perform "Rebuild Project" on each prerequisite.
The only reason I wouldn't like this is because if you have lots of projects
in
a workspace, with a deep dependency tree, building a single project could
take
a lot of time. This is particularily annoying if you're running repeated
unit
tests. It would be nice to have this as a configurable option, IMHO. In my
experience, we rarely work on more than a single project at a time so having
to do a check and rebuild each time you run a test is a waste of time.
Cheers,
Dave.
> We will (as of 3.0
> M8) now do this automatically. This now has more of a make or Ant feel
> - you select what project you want built, and Eclipse figures out what
> prereq projects need to be built in order to properly build that target.
> --
>
> Dave Rathnow wrote:
> > can I assume that the behavior I'm seeing is normal? That
> > is, when you rebuild a project, Eclipse attempts to rebuild
> > any/all projects it depends on? If so, I really hope this changes!!
>
|
|
|
Powered by
FUDForum. Page generated in 0.06265 seconds
Home