Home » Language IDEs » Java Development Tools (JDT) » Builders do not follow displayed order
| Builders do not follow displayed order [message #169709] |
Wed, 21 July 2004 18:00  |
Eclipse User |
|
|
|
Folks,
I'm in the process of moving from Eclipse 2.1 to 3.0. Our project build
consists of 3 steps: 1. an ANT pre compile operation, 2. the Java builder,
and
3. an ANT post compile operation. These must be performed in order.
Under 2.1, these executed in order (1, 2, 3) and all worked fine.
Under 3.0, the order is not being forced as displayed in the Builders
dialog...the build is failing miserably. The ordered executed appears to
be 1, 3, 2.
How to I force the order of build displayed in the Builders dialog within
Eclipse 3.0?
Cheers,
|
|
| | | | |
| Re: Builders do not follow displayed order [message #170090 is a reply to message #170069] |
Mon, 26 July 2004 17:14  |
| Eclipse User |
|
|
|
My step 1 is ANT creating a dir structure and running JavaCC to build a few
..java source files from a syntax description.
Step 2 is the full Java source compile (includes those files generated in
step 1).
Step 3 is basically ANT moving files around to enable run/debug.
This all worked fine under 2.1
"Dave Carlson" <dcarlson@xmlmodeling.com> wrote in message
news:ce3ltt$ton$1@eclipse.org...
> Did you configure the "working set of relevant resources" in your two Ant
> builds?
No. We didn't touch anything when we moved from 2.1 to 3.0
>
> I have a build configuration that is a subset of this, only steps 1 & 2.
I
> was also seeing step 1 repeat after the Java builder, until I narrowed the
> working set to the source files relevant to the Ant build. I believe that
> the default is the entire project, so the Java build modifies the bin dir,
> which triggers a new build of the Ant builder.
>
> Can't explain why 3 runs before 2...
Looks like it runs all the the ANT steps, does the Java Build, then runs all
the ANT steps again.
>
> -- Dave
>
> "P Duffy" <paduffy@cisco.com> wrote in message
> news:ce3jl9$pir$1@eclipse.org...
> > I've just tried all of Darin's and Vladimir's suggestions. No
> > change...build is failing badly. Problem is actually worse than I
> > originally described. Instead of running the displayed build order of:
> >
> > 1. Ant target pre compile
> > 2. Eclipse Java build
> > 3. Ant target post compile.
> >
> > ...what I'm seeing is : 1, 3, 2, 1, 3.
> >
> > ???
> >
> > "Darin Swanson" <Darin_Swanson@us.ibm.com> wrote in message
> > news:cdqd8b$trm$1@eclipse.org...
> > > You have all of the Ant builders set to run in the foreground?
> > > Ensure that the "Launch in background" option on the Build Options tab
> is
> > > not toggled
> > >
> > > HTH
> > > Darins
> > >
> > > "vladimir" <vladimir@none.com> wrote in message
> > > news:cdpmeu$v5v$1@eclipse.org...
> > > > That's odd. Are you adding these ant builders through external
tools?
> > Are
> > > > you sure that your ant builder points to appropriate ant targets? Do
> > > > everything again from scratch...
> > > >
> > > > Cheers.
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
| Re: Builders do not follow displayed order [message #170270 is a reply to message #170090] |
Tue, 27 July 2004 10:03 |
| Eclipse User |
|
|
|
Is your step 1 creating java files in a java source dir for the project?
If not, it won't trigger the java build.
Also -- does your step 1 refresh the project? If not, it won't trigger
the java build.
So...
my guess would be
1) builder 1 is triggered because some non-java code was modified
(javacc grammar, perhaps), but step 1 isn't refreshing.
2) builder 2 is *not* triggered because eclipse doesn't see any java
files in a source dir changing
3) builder 3 is triggered for the same reason as step 1, but refreshes
the project after running
4) builder 2 is invoked because step 3 refreshed and now eclipse sees
java file changes (however those changes aren't in the working set of
step 1...)
5) builder 1 is triggered because it's watching the output dir(s), which
is changed by step 2
6) builder 3 is triggered because it sees changes made by builder 1, and
refreshes
7) no trigger files have changed so we're done
I don't know if that's exactly what is happening, but that may give you
something to work with... I've had similar fun when working with (the
vastly superior) ANTLR.
Ok, so I'm biased because I contributed to ANTLR ;)
Anyway, hope this helps a bit...
- Scott
In article <ce3s4d$8ab$1@eclipse.org>, paduffy@cisco.com says...
> My step 1 is ANT creating a dir structure and running JavaCC to build a few
> .java source files from a syntax description.
> Step 2 is the full Java source compile (includes those files generated in
> step 1).
> Step 3 is basically ANT moving files around to enable run/debug.
>
> This all worked fine under 2.1
>
> "Dave Carlson" <dcarlson@xmlmodeling.com> wrote in message
> news:ce3ltt$ton$1@eclipse.org...
> > Did you configure the "working set of relevant resources" in your two Ant
> > builds?
>
> No. We didn't touch anything when we moved from 2.1 to 3.0
>
> >
> > I have a build configuration that is a subset of this, only steps 1 & 2.
> I
> > was also seeing step 1 repeat after the Java builder, until I narrowed the
> > working set to the source files relevant to the Ant build. I believe that
> > the default is the entire project, so the Java build modifies the bin dir,
> > which triggers a new build of the Ant builder.
> >
> > Can't explain why 3 runs before 2...
>
> Looks like it runs all the the ANT steps, does the Java Build, then runs all
> the ANT steps again.
> >
> > -- Dave
> >
> > "P Duffy" <paduffy@cisco.com> wrote in message
> > news:ce3jl9$pir$1@eclipse.org...
> > > I've just tried all of Darin's and Vladimir's suggestions. No
> > > change...build is failing badly. Problem is actually worse than I
> > > originally described. Instead of running the displayed build order of:
> > >
> > > 1. Ant target pre compile
> > > 2. Eclipse Java build
> > > 3. Ant target post compile.
> > >
> > > ...what I'm seeing is : 1, 3, 2, 1, 3.
> > >
> > > ???
> > >
> > > "Darin Swanson" <Darin_Swanson@us.ibm.com> wrote in message
> > > news:cdqd8b$trm$1@eclipse.org...
> > > > You have all of the Ant builders set to run in the foreground?
> > > > Ensure that the "Launch in background" option on the Build Options tab
> > is
> > > > not toggled
> > > >
> > > > HTH
> > > > Darins
> > > >
> > > > "vladimir" <vladimir@none.com> wrote in message
> > > > news:cdpmeu$v5v$1@eclipse.org...
> > > > > That's odd. Are you adding these ant builders through external
> tools?
> > > Are
> > > > > you sure that your ant builder points to appropriate ant targets? Do
> > > > > everything again from scratch...
> > > > >
> > > > > Cheers.
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
>
|
|
|
| Re: Builders do not follow displayed order [message #170285 is a reply to message #170270] |
Tue, 27 July 2004 10:34 |
| Eclipse User |
|
|
|
"Scott Stanchfield" <scott@javadude.com> wrote in message
news:MPG.1b702acc98b978dd989711@news.eclipse.org...
> Is your step 1 creating java files in a java source dir for the project?
Yes
> If not, it won't trigger the java build.
>
> Also -- does your step 1 refresh the project? If not, it won't trigger
> the java build.
Yes
Like I said, this all worked fine under 2.1
>
> So...
>
> my guess would be
>
> 1) builder 1 is triggered because some non-java code was modified
> (javacc grammar, perhaps), but step 1 isn't refreshing.
>
> 2) builder 2 is *not* triggered because eclipse doesn't see any java
> files in a source dir changing
>
> 3) builder 3 is triggered for the same reason as step 1, but refreshes
> the project after running
>
> 4) builder 2 is invoked because step 3 refreshed and now eclipse sees
> java file changes (however those changes aren't in the working set of
> step 1...)
>
> 5) builder 1 is triggered because it's watching the output dir(s), which
> is changed by step 2
>
> 6) builder 3 is triggered because it sees changes made by builder 1, and
> refreshes
>
> 7) no trigger files have changed so we're done
>
> I don't know if that's exactly what is happening, but that may give you
> something to work with... I've had similar fun when working with (the
> vastly superior) ANTLR.
>
> Ok, so I'm biased because I contributed to ANTLR ;)
>
> Anyway, hope this helps a bit...
>
> - Scott
>
>
>
>
> In article <ce3s4d$8ab$1@eclipse.org>, paduffy@cisco.com says...
> > My step 1 is ANT creating a dir structure and running JavaCC to build a
few
> > .java source files from a syntax description.
> > Step 2 is the full Java source compile (includes those files generated
in
> > step 1).
> > Step 3 is basically ANT moving files around to enable run/debug.
> >
> > This all worked fine under 2.1
> >
> > "Dave Carlson" <dcarlson@xmlmodeling.com> wrote in message
> > news:ce3ltt$ton$1@eclipse.org...
> > > Did you configure the "working set of relevant resources" in your two
Ant
> > > builds?
> >
> > No. We didn't touch anything when we moved from 2.1 to 3.0
> >
> > >
> > > I have a build configuration that is a subset of this, only steps 1 &
2.
> > I
> > > was also seeing step 1 repeat after the Java builder, until I narrowed
the
> > > working set to the source files relevant to the Ant build. I believe
that
> > > the default is the entire project, so the Java build modifies the bin
dir,
> > > which triggers a new build of the Ant builder.
> > >
> > > Can't explain why 3 runs before 2...
> >
> > Looks like it runs all the the ANT steps, does the Java Build, then runs
all
> > the ANT steps again.
> > >
> > > -- Dave
> > >
> > > "P Duffy" <paduffy@cisco.com> wrote in message
> > > news:ce3jl9$pir$1@eclipse.org...
> > > > I've just tried all of Darin's and Vladimir's suggestions. No
> > > > change...build is failing badly. Problem is actually worse than I
> > > > originally described. Instead of running the displayed build order
of:
> > > >
> > > > 1. Ant target pre compile
> > > > 2. Eclipse Java build
> > > > 3. Ant target post compile.
> > > >
> > > > ...what I'm seeing is : 1, 3, 2, 1, 3.
> > > >
> > > > ???
> > > >
> > > > "Darin Swanson" <Darin_Swanson@us.ibm.com> wrote in message
> > > > news:cdqd8b$trm$1@eclipse.org...
> > > > > You have all of the Ant builders set to run in the foreground?
> > > > > Ensure that the "Launch in background" option on the Build Options
tab
> > > is
> > > > > not toggled
> > > > >
> > > > > HTH
> > > > > Darins
> > > > >
> > > > > "vladimir" <vladimir@none.com> wrote in message
> > > > > news:cdpmeu$v5v$1@eclipse.org...
> > > > > > That's odd. Are you adding these ant builders through external
> > tools?
> > > > Are
> > > > > > you sure that your ant builder points to appropriate ant
targets? Do
> > > > > > everything again from scratch...
> > > > > >
> > > > > > Cheers.
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
|
|
|
Goto Forum:
Current Time: Wed May 07 18:32:08 EDT 2025
Powered by FUDForum. Page generated in 0.04275 seconds |
Home