I think that the local repo needs to be make canonical when
initialized (from settings.xml or from system property), should fix
the bulk of strange problems which are related.
--jason
On Feb 3, 2007, at 2:32 PM, Jorg Heymans wrote:
Jason Dillon wrote:
When I was building locally and on remote systems, I was using -
Dmaven.repo.local=repository to use a specific repository
directoy. But it looks like something inside of Maven or Surefire
is not happy if this value is not absolute or canonical. While
most of Maven is happy with the relative path downloading a ton of
artifacts into the correct directory, something gets screwy when
going to launch tests.
I've fixed my harness to make this path canonical, but my guess is
that Maven should always resolve maven.repo.local to a canonical
file before attempting to use it for sanity.
Any Maven peeps out there know if this is a known issue?
FWIW i can confirm this, had the same problem when building Cocoon
with a relative repository set in settings.xml.
Jorg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
