Yes, in our defaults.properties in maven.jar we have...
maven.src.dir = ${basedir}/src
maven.conf.dir = ${maven.src.dir}/conf
But it shouldn't be adding an additional edog should it? When I run
'maven -p edog/project.xml my-boostrap-goal' from c:\projects\crap\scm
it works fine. Its only when run from <maven:maven> it fails.
--Norm
---------------------------
Norm Deane
MIS Consultant
Vanderbilt University
(615) 322-7855
[EMAIL PROTECTED]
-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 27, 2004 4:06 PM
To: 'Maven Users List'
Subject: RE: [scm] Problem Running scm:bootstrap-project
Dsoes maven.conf.dir include ${basedir}? It looks like an additional
"edog" path is being added.
- Brett
> -----Original Message-----
> From: Norm Deane [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 28 January 2004 3:22 AM
> To: Maven Users List
> Subject: [scm] Problem Running scm:bootstrap-project
>
>
> I'm trying to get the scm:bootstrap-project working and am
> running into a problem.
>
> I'm running 'maven scm:boostrap-project
> -Dmaven.scm.cvs.module=edog' from c:\projects\crap\scm. The
> cvs checkout completes successfully (creating
> c:\projects\crap\scm\edog) but when it tries to run my
> bootstrap goal I get an error.
>
> In my bootstrap goal I'm doing the following...
>
> <util:available
> file="${maven.conf.dir}/${pom.artifactId}.filters">
> <ant:filter
> filtersfile="${maven.conf.dir}/${pom.artifactId}.filters"/>
> </util:available>
>
> And am getting an error...
>
file:/c:/tools/apache/maven_local/plugins/maven-mis-util-plugin-1.0.0/:8
6:84
: <a
nt:filter> Must specify a file not a directory in the filtersfile
attribute:C:\p rojects\crap\scm\edog\edog\src\conf\edog.filters
com.werken.werkz.UnattainableGoalException: Unable to obtain goal
[scm:bootstrap -project] --
file:/c:/tools/apache/maven_local/plugins/maven-scm-plugin-1.1/:77:
9: <maven:maven>
file:/c:/tools/apache/maven_local/plugins/maven-mis-util-plugin
-1.0.0/:86:84: <ant:filter> Must specify a file not a directory in the
filtersfi le
attribute:C:\projects\crap\scm\edog\edog\src\conf\edog.filters
Apparently, the file path is correct when the <util:available> is
evaluated or else we would never get inside the body of the tag.
However, when the <ant:filter> is evaluated an extra 'edog' is added
into the absolute file path.
Any ideas?
--Norm
--
Norm Deane
MIS Consultant
Vanderbilt University
(615) 322-7855
[EMAIL PROTECTED]
---------------------------------------------------------------------
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]
