Re: [iam-dev] Support for locally installed maven

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [iam-dev] Support for locally installed maven

From: "Michael Poindexter" <staticsnow@xxxxxxxxx>
Date: Sat, 22 Nov 2008 16:00:57 -0800
Delivered-to: iam-dev@xxxxxxxxxxx
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=FGmzdO46MjoVURQkRqRfRHAfCCzohriDp0PiIk7HPOREQf/4tLAwakL/aS0kAW81Df mmlEvv7bb/bpXSc/CH6Pp60tgViMCqS4CldNa5rHUbJuI7EBHmeqzDDm7yBGQ4jhPxBu yYdgUv+78HcPI4W6BEQvRs91+dZIqj58/KsGE=
List-archive: <https://dev.eclipse.org/mailman/private/iam-dev>
List-help: <mailto:iam-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/iam-dev>, <mailto:iam-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/iam-dev>, <mailto:iam-dev-request@eclipse.org?subject=unsubscribe>

Perhaps we could execute Maven externally and hook an agent/listener into it, similar to the way Hudson (https://hudson.dev.java.net/) works? This would let us inject whatever code we need into the external Maven while solving our out of memory problems (and allow users to control how much memory to allow Maven to use) and keep us from doing nasty things like parsing console output.

Mike

PS - Sorry I haven't been active lately, I'm swamped at work, but hopefully I can get back to writing some code in January.

Follow-Ups:
- Re: [iam-dev] Support for locally installed maven
  - From: Abel Muiño Vizcaino

Prev by Date: Re: [iam-dev] More extension point ideas.
Next by Date: Re: [iam-dev] Task: scan codebase for q4e references
Previous by thread: [iam-dev] TPTP profiling of IAM
Next by thread: Re: [iam-dev] Support for locally installed maven
Index(es):
- Date
- Thread

Breadcrumbs