On Mon, Jun 05, 2006 at 10:44:27AM -0500, Dominique Devienne wrote:
> >Ok, great ! I just saw the code to the jaxb task. Indeed, it looks quite
> >easy to use the Java task for that. Thanks a lot for the pointer !
>
> Always glad to help ;-)
Wow, i tried using Java in the tom task to run the compi
Ok, great ! I just saw the code to the jaxb task. Indeed, it looks quite
easy to use the Java task for that. Thanks a lot for the pointer !
Always glad to help ;-)
I did that, running tom compilation from a java app for fifteen files in
an infinite loop: it ran for 2 days without showing any m
Hi,
On Mon, Jun 05, 2006 at 09:05:03AM -0500, Dominique Devienne wrote:
> >I guess the more elegant way would be to add a "fork" attribute to our
> >tom task, but i don't know how difficult it would be, as to is simply a
> >java application.
>
> That would be the way to go, indeed. It's rather si
I guess the more elegant way would be to add a "fork" attribute to our
tom task, but i don't know how difficult it would be, as to is simply a
java application.
That would be the way to go, indeed. It's rather simple to compose the
Java task in another task. I've used this approach to add "smart
On Sun, Jun 04, 2006 at 09:17:13PM +0100, Steve Loughran wrote:
> Antoine Reilles wrote:
> >Hi,
> >
> >For building the examples of the tom project (http://tom.loria.fr), we
> >use the subant task, each example containing a build.xml snippet, using
> >
> >
> >
> >
> >
> >Those exa
Antoine Reilles wrote:
Hi,
For building the examples of the tom project (http://tom.loria.fr), we
use the subant task, each example containing a build.xml snippet, using
Those examples do use the tom ant task to compile tom sources to java,
and then javac. The tom ant task
>Probably not. Ideally there would be a fork attribute for (and
>) to ensure each sub-build runs in its own VM,
>ensuring proper release of memory (when the process exists),
>but it's never been done and is non-trivial, since a
>cross-process logger/listener thing needs to be put in place,
>an
On 5/31/06, Antoine Reilles <[EMAIL PROTECTED]> wrote:
Also, if I change the build to avoid the use of subant, by inlining all
subprocesses, the build goes farther, since it loads all tom's compiler
classes only once, instead of once for each subant part.
Using , just like , creates a new proje
On Tue, May 30, 2006 at 07:49:26AM -0500, Dominique Devienne wrote:
> It's quite possible Ant or SubAnt itself hold on to too many
> references. There have been fixes in Ant's ComponentHelper in the
> past. But maybe Tom's compiler could be at fault as well, no? This
> would need to be investigated
It's quite possible Ant or SubAnt itself hold on to too many
references. There have been fixes in Ant's ComponentHelper in the
past. But maybe Tom's compiler could be at fault as well, no? This
would need to be investigated using a JProbe-like tool.
--DD
On 5/29/06, Antoine Reilles <[EMAIL PROTE
Hi,
For building the examples of the tom project (http://tom.loria.fr), we
use the subant task, each example containing a build.xml snippet, using
Those examples do use the tom ant task to compile tom sources to java,
and then javac. The tom ant task require to load the tom
11 matches
Mail list logo
