I've run into a strange problem with a fresh installation of m2. Some
of our unit tests require machine-specific system properties which we
usually supply at the command-line, e.g.
mvn install -Dmy.prop=value
I recently emptied the local repository on one of the (AMD64) machines
(running FC4),
On 6/28/06, Josh <[EMAIL PROTECTED]> wrote:
I've run into a strange problem with a fresh installation of m2. Some
of our unit tests require machine-specific system properties which we
usually supply at the command-line, e.g.
mvn install -Dmy.prop=value
I recently emptied the local repository
20:34
À : Maven Users List
Objet : Re: [m2] properties not available to unit tests
On 6/28/06, Josh <[EMAIL PROTECTED]> wrote:
> I've run into a strange problem with a fresh installation of m2. Some
> of our unit tests require machine-specific system properties which we
> usual
to an issue (I don't remember which one)
--
Olivier
-Message d'origine-
De : Wendy Smoak [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 28 juin 2006 20:34
À : Maven Users List
Objet : Re: [m2] properties not available to unit tests
On 6/28/06, Josh <[EMAIL PROTECTED]> wr