maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Siveton (JIRA)" <>
Subject [jira] Closed: (MNG-3213) Please update to plexus-utils 1.4.3 or later for PLXUTILS-36
Date Sun, 06 Jan 2008 15:29:57 GMT


Vincent Siveton closed MNG-3213.

         Assignee: Vincent Siveton
       Resolution: Fixed
    Fix Version/s:     (was: 2.0.x)

Already fixed in mvn 2.0.8 with plexus-utils:1.4.6
If a given maven project doesn't use it yet, please open another issue for the given project.

> Please update to plexus-utils 1.4.3 or later for PLXUTILS-36
> ------------------------------------------------------------
>                 Key: MNG-3213
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.0.7
>            Reporter: Max Bowsher
>            Assignee: Vincent Siveton
>             Fix For: 2.0.8
> Please update to plexus-utils 1.4.3 or later to get the fix for PLXUTILS-36.
> This is a fairly minor bug, but the failure mode is extremely puzzling and quite difficult
to debug if you have not seen it before.
> The problem is that, if an envvar with a single-character name is defined, then plexus-utils
will mangle another envvar at random (depending on the random sort order of the environment
block). For three developers in my office, it has impacted the SSH_AUTH_SOCK envvar, causing
Subversion operations and Maven scpexe deployments to fail with mysterious-seeming authentication

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message