You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Brett Porter <bp...@f2network.com.au> on 2003/12/12 02:10:50 UTC
maven site failures
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)
2) pom.build needs to be copied instead of assigned
BTW, I put this in JIRA under "log work done", but it seems it doesn't mail
those to the list - can someone update the notification scheme?
- Brett
--
Brett Porter
Team Leader, Core Systems
f2 network ~ everything essential
Re: maven site failures
Posted by Jason van Zyl <jv...@maven.org>.
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't be. I bootstrapped with all the plugins with 23mb of memory.
What's the figure currently?
> 2) pom.build needs to be copied instead of assigned
>
> BTW, I put this in JIRA under "log work done", but it seems it doesn't mail
> those to the list - can someone update the notification scheme?
>
> - Brett
>
> --
> Brett Porter
> Team Leader, Core Systems
> f2 network ~ everything essential
>
--
jvz.
Jason van Zyl
jason@zenplex.com
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org