Wow, that's great! I can't wait to take it for a spin.
john
On Fri, 2003-12-12 at 19:17, [EMAIL PROTECTED] wrote:
> It is fixed in the 1.0 branch.
>
> The branch still has a few more issues to be resolved, but it's looking
> good.
> --
> dIon Gillard, Multitask Consulting
> Blog: http://bl
It is fixed in the 1.0 branch.
The branch still has a few more issues to be resolved, but it's looking
good.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
John Casey <[EMAIL PROTECTED]> wrote on 13/12/2003 09:39:06 AM:
> I have scanned the bugs listed
BTW, I have been able to deduce from my own usage patterns that most of
the leak seems to take place in the jelly ant task wrapper tag...for
whatever it's worth, this is always where the memory disappears never to
reappear again...
-j
On Fri, 2003-12-12 at 17:39, John Casey wrote:
> I have scanne
I have scanned the bugs listed in jira, looking for the memory leak I'm
experiencing when I run a reactor-ized multiproject:xxx build.
What I find are several bugs which talk about various memory leaks, and
are marked fixed (most in the relatively distant past), and some more
which describe the "
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1080
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPWIZARD-2
Here is an overview of the issue:
-
Hi Jason,
Noticed yesterday the a faq link still pops up in the project
documentation, although people don't necessarily have a main faq entry
(meaning in the root of the xdoc directory).
Couldn't find the code however that puts it there and I am not sure if
we want to keep the faq link in the pr
On Thu, 2003-12-11 at 20:10, Brett Porter wrote:
> I think have this fixed - just requires some more testing before
> committing.
>
> Solutions:
> 1) push/pop plugin contexts around goal attainment (I'm worried about the
> memory usage here though - will compare and look at necessity)
Shouldn
On Thu, 2003-12-11 at 18:34, Brett Porter wrote:
> ${pom.build.sourceDirectory}?
>
> I think we'll definitely need access to ${pom} in plugins and the project
> plugin (maven.xml or whatever the non-Jelly replacement is).
For certain, what I'm limiting is access to the ${pom} in the
project.prop
