I second Wendy's or Michael's suggestions - avoid system scope at all costs.
Moreover, it may be removed in future versions of Maven, so don't depend on
it being there forever. May as well make preperations now :)
--
Eric Redmond
http://blog.propellors.net
On 7/30/07, Wendy Smoak [EMAIL
When we run maven JUnits - and ensure that testing is successful. - run mvn
test
but its through out exception and looks like it did not run properly JUnit
in project.
How the first step to check where is error in configuration / setting sof
maven and fix this error
thanks,
DT
www.ejinz.com
On 7/20/07, Tawfik, Sameh E [EMAIL PROTECTED] wrote:
Hi,
I'm using the following code:
dependency
groupIdconnector/groupId
artifactIdconnector/artifactId
version1_0/version
scopesystem/scope
systemPath${Build_base}/ma-jdm-tck/lib/connector_1_0.jar/systemPath
trace which makes maven execution trace hard to read).
Can this issue be solved by using an inhouse repository ?
-Message d'origine-
De : Tawfik, Sameh E [mailto:[EMAIL PROTECTED]
Envoyé : mardi 24 juillet 2007 21:12
À : Maven Users List
Objet : RE: How to use ${project.build.directory
repository.
Thanks,
Sameh
-Original Message-
From: Michael Meyer [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 21, 2007 1:51 AM
To: Maven Users List
Subject: Re: How to use ${project.build.directory}?
Hi,
yes you can use maven properties. This should do what you want:
dependency
Hi,
yes you can use maven properties. This should do what you want:
dependency
groupIdconnector/groupId
artifactIdconnector/artifactId
version1_0/version
scopesystem/scope
systemPath${basedir}/../ma-jdm-tck/lib/connector_1_0.jar/systemPath
/dependency
But please don't do it! If you
Hi,
I'm using the following code:
dependency
groupIdconnector/groupId
artifactIdconnector/artifactId
version1_0/version
scopesystem/scope
systemPath${Build_base}/ma-jdm-tck/lib/connector_1_0.jar/systemPath
/dependency
This code is working fine, but it requires
