Home » Language IDEs » Java Development Tools (JDT) » easiest way to get multiple incremental javabuilders
| easiest way to get multiple incremental javabuilders [message #255222] |
Thu, 24 July 2008 04:38  |
Eclipse User |
|
|
|
Originally posted by: jhscott.mit.edu
Hi,
I have multiple components in a single project that I would like to build
in a cascade, details below. I would like eclipse integration (autobuild,
problems in the Problems pane, %age-complete, etc) which eliminates using
an external builder such as ant, from what I can tell. I'm wondering
whether I have to build my own Builder from scratch as described in:
http://wiki.eclipse.org/FAQ_How_do_I_implement_an_Eclipse_bu ilder%3F
Or if there is an easier solution.
I have components A, B, and C such that B depends on A, and C depends on B
(but B doesn't depend on C, nor does A on B or C). My code is organized in
directories:
srcA/
srcB/
srcC/
which compile class files to binA/, binB/, binC/ .
I would like to trigger three builds, the first for srcA, the second for
srcB with binA on the classpath, the third for srcC with binA, binB on the
classpath.
Is there any easy way to do this? Crossposted from newcomers, as jdt seems
like it might be the appropriate place
Thanks,
Jacob
|
|
|
| Re: easiest way to get multiple incremental javabuilders [message #255239 is a reply to message #255222] |
Thu, 24 July 2008 09:50  |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Jacob wrote:
> Hi,
>
> I have multiple components in a single project that I would like to
> build in a cascade, details below. I would like eclipse integration
> (autobuild, problems in the Problems pane, %age-complete, etc) which
> eliminates using an external builder such as ant, from what I can tell.
> I'm wondering whether I have to build my own Builder from scratch as
> described in:
>
> http://wiki.eclipse.org/FAQ_How_do_I_implement_an_Eclipse_bu ilder%3F
>
> Or if there is an easier solution.
>
> I have components A, B, and C such that B depends on A, and C depends on
> B (but B doesn't depend on C, nor does A on B or C). My code is
> organized in directories:
>
> srcA/
> srcB/
> srcC/
>
> which compile class files to binA/, binB/, binC/ .
>
> I would like to trigger three builds, the first for srcA, the second for
> srcB with binA on the classpath, the third for srcC with binA, binB on
> the classpath.
If I understand your need correctly, you don't really need to do
anything special; Eclipse's incremental compiler will handle things for
you as long as you have the dependencies set up as you described (A is
the root, B depends on A, and C depends on B). The incremental compiler
knows all of the dependencies and compiles exactly what needs to be
recompiled in response to any change (triggered on save). This is, of
course, assuming that you have not turned off the Build Automatically
option.
Is there something specific that you are experiencing that leads you to
believe you need to do more?
Eric
|
|
| | |
| Re: easiest way to get multiple incremental javabuilders [message #255291 is a reply to message #255259] |
Fri, 25 July 2008 11:06 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
Jacob Scott wrote:
> This is in a single project, so I only get one classpath, as far as I
> know (so I can't have different dependencies for different
> components).
>
and later:
> After some reflection, I think what I would like is multiple
> classpath configurations (.classpathA, .classpathB, .classpathN)
> each with an associated Eclipse JavaBuilder, so that the JavaBuilders
> run in (e.g. alphabetical) sequence. I probably also need a "parent"
> JavaBuilder to correctly wrap the interactions with Eclipse (progress
> bar, problem views, etc). Is there any way to achieve this
> functionality with Eclipse? I guess my fallback option is to have
> multiple projects, but this is suboptimal since the components are
> tightly coupled and developers will always be working on them
> together.
Note: please quote the previous message when replying so that everyone
can see the context.
I missed the part in your original message about this being in a single
project, sorry. But I'm not clear what you're trying to do. Even in a
single project with multiple source directories, Eclipse should handle
this without requiring you to do anything special.
Can you take a step back and explain at a higher level what you
want/need to do and compare it to what you are seeing/getting with a
simple project setup with multiple source locations?
Eric
|
|
|
Goto Forum:
Current Time: Sat May 10 16:29:19 EDT 2025
Powered by FUDForum. Page generated in 0.04389 seconds |
Home