${basedir} :-)
Technically, this gives the directory where the pom is located, not the
directory from which you run mvn.
Paul
EJ Ciramella-2 wrote:
Is there some property readily available that represents the directory
from which maven was run from?
Something like ${basedir} in ant
I haven't been able to get that kind of thing to work when running
process-resources.
Additionally, if I have three levels, (parent pom.xml - parent pom.xml
- module pom.xml) and the resource processing happens at the module
level, would the basedir be of the parent pom or of the module pom
Hmm. It works for me in a plain, single-module setup. You may need to say
filteringtrue/filtering; I don't know if it's the default. I'm not sure
what ${basedir} means with many modules. Are you getting weird results, or
is it just not getting replaced at all?
Paul
EJ Ciramella-2 wrote:
I
Ahh - I'm not talking about having it IN a resource, I'm talking about
having it in the resource mapping in the POM file.
-Original Message-
From: pjungwir [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 25, 2006 3:31 PM
To: users@maven.apache.org
Subject: RE: basedir
Hmm. It works
directorysrc/main/scripts/directory
targetPath${basedir}/scripts/targetPath
filteringtrue/filtering
/resource
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 25, 2006 3:36 PM
To: Maven Users List
Subject: RE: basedir
Oh, okay. By default, all paths are relative to basedir already, so I'm not
sure why you'd need it. But in my setup, this still works:
resource
directory${basedir}/foo/directory
/resource
Again, I'm not sure what it means with multiple modules, but it should at
least get resolved. What
\LTY-P39\frontoffice\memberApp\target\classes\E:\work\LTY-P00
0039\frontoffice\memberApp\scripts\startApp.sh (The filename, directory
name, or volume label syn
tax is incorrect)
When I have this:
resource
directorysrc/main/scripts/directory
targetPath${basedir
So what I'm attempting to do is pull in a resource from another modules
target directory. So if basedir was /toplevel and not
/toplevel/project/module1, that would help. Instead we'll continue to
use relative paths.
Bummer...
-Original Message-
From: pjungwir [mailto:[EMAIL PROTECTED
Basedir depends entirely on where you are executing Maven from...
Instead of pulling files directly out of other modules (using relative
paths), I would suggest packaging those shared modules by themselves
and adding a dependency on them in both modules, or perhaps use the
assembly plugin
:
http://www.nabble.com/basedir-tf2509183.html#a7001106
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
If I use cygwin to make a Maven 2.x project by default the basedir is -
Value: C:\cygwin\home\MyName. How can I change this? I want to set the
basedir to C:\mavenWorkspace\projects. I tried passing
-Dbasedir=C:\mavenWorkspace\projects but it just seems to be ignored?
Thanks
--
View this message
Changing the basedir?
Please respond to
Maven Users
List
Ah, ok thanks Ian. I didn't realize mvn created new projects in the current
working directory.
Thanks again.
--
View this message in context:
http://www.nabble.com/Changing-the-basedir--tf2196173.html#a6081877
Sent from the Maven - Users forum at Nabble.com
Is/are there some variable that allows something like ${basedir} type
usage in pom.xml? Is there some variable for the current working
directory of the pom.xml that's getting used?
Can Clover read your license file from the classpath ?
Then you could deploy your (jarred) license to your maven repo and add
it as a dependency to the clover plugin. See the checkstyle plugin
docs [1] for more information - it allows you to do a similar thing
with checkstyle configurations.
Tom
pom.xml
src
test
clover
clover.license
pom.xml == my super pom
I like to define in my super pom.xml that the clover license is in the
directory /src/test/clover/clover.license but all possible variables I
found like ${basedir}or ${pom.dir
is in the
directory /src/test/clover/clover.license but all possible variables I
found like ${basedir}or ${pom.dir} doesn't work.
Any ideas?
Regards,
Ingo
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
This is not really a good solution, because then you have to be always
online and must have contact to the server.
No other solution?
Regards,
Ingo
Emmanuel Venisse schrieb:
No you can't.
It would be better to use an url to reference your clover license file.
Emmanuel
Could you just symlink the license file around to the various directories?
On 8/16/06, Wayne Fay [EMAIL PROTECTED] wrote:
Set up Apache on your box and point it to the top root directory. Then
its always online and you're obviously connected to the server, so
you can use a URL to the file.
Is there a maven equivalent to Ant's basedir?
With this project that I've talking about that has 100s of custom builds,
I'd like to use 1 POM file that uses a dynamic basedir that is set via a
property or profile.
Any thoughts?
__
Douglas W
Try ${project.build.directory}.
-jason
-Original Message-
From: David J. M. Karlsen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 26, 2006 11:37 AM
To: Maven Users List
Subject: [m2] variable for ${basedir}/target ?
Hi!
Does any variable exist for ${basedir}/target
and a variable for the main resource directory?
On 7/26/06, David J. M. Karlsen [EMAIL PROTECTED] wrote:
Hi!
Does any variable exist for ${basedir}/target - or is this the closest I
can come?
Does there exist a list over variable expressions in maven2 poms?
--
David J. M. Karlsen - +47
for ${basedir}/target - or is this the closest I
can come?
Does there exist a list over variable expressions in maven2 poms?
--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
Eric Redmond wrote:
You can get most (all?) element values from the pom in the form of
parameters, nesting by dot notation.
for example:
project
build
directoryVALUE/directory
is ${project.build.directory}
etc.
If you want to play with viewing the value of any parameter, try the ant
On 7/20/06, Mike Perham [EMAIL PROTECTED] wrote:
Is it JavaSource or JavaSources? You use both below.
I'm sorry , that was a typo.It's JavaSource
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Can we have a look at your parent pom?
Looks like maven is trying to build a war out of your parent project
Sure thing.There goes :
project
modelVersion4.0.0/modelVersion
groupIdza.co.mycompany.eportal/groupId
artifactIdmycompany-eportal/artifactId
namemycompany ePortal/name
, isn't it?)
Denis.
--
View this message in context:
http://www.nabble.com/basedir-JavaSource-does-not-exist-tf1973672.html#a5430061
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
On 7/21/06, dcabasson [EMAIL PROTECTED] wrote:
Jeff Mutonho wrote:
Can we have a look at your parent pom?
Looks like maven is trying to build a war out of your parent project
Sure thing.There goes :
Ok, that was not the interesting parent. Guess I wanted to say the eportal
pom
m2 is spitting out the error message basedir JavaSource does not exist
.I have the following in my maven-war-plugin config in my web
project pom(i.e D:\MAVEN-WORK\eportal\eportal-web\pom.xml)
resource
!-- this is relative to the pom.xml directory --
directoryJavaSource/directory
excludes
Is it JavaSource or JavaSources? You use both below.
-Original Message-
From: Jeff Mutonho [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 20, 2006 7:18 AM
To: Maven Users List
Subject: basedir JavaSource does not exist
m2 is spitting out the error message basedir JavaSource does
Jeff Mutonho wrote:
m2 is spitting out the error message basedir JavaSource does not exist
.I have the following in my maven-war-plugin config in my web
project pom(i.e D:\MAVEN-WORK\eportal\eportal-web\pom.xml)
Can we have a look at your parent pom?
Looks like maven is trying to build
On 7/20/06, Jeff Mutonho [EMAIL PROTECTED] wrote:
m2 is spitting out the error message basedir JavaSource does not exist
.I have the following in my maven-war-plugin config in my web
project pom(i.e D:\MAVEN-WORK\eportal\eportal-web\pom.xml)
resource
!-- this is relative to the pom.xml
Am I misreading the process by which expressions are evaluated?
Consider project A with pom.xml containing
properties
target.binary.dir${basedir}/target/bin/target.binary.dir
/properties
and A's sub-project B with pom.xml containing
build
directory${target.binary.dir
On 6/22/06, Brad Harper [EMAIL PROTECTED] wrote:
Am I misreading the process by which expressions are evaluated?
Consider project A with pom.xml containing
properties
target.binary.dir${basedir}/target/bin/target.binary.dir
/properties
and A's sub-project B with pom.xml containing
of ${basedir} in an Expression
That is the expected behavior, even thou it seems odd, and i hope it stays
that way.
Fixing this will break lots of builds, mine for sure.
build
directory../target/bin/directory
...
/build
should work for B. Again it is a little odd since you are forced
rich client repository/name
urlfile:${basedir}/maven2repository/url
snapshots
enabledtrue/enabled
/snapshots
/repository
/repositories
It found my dependencies spring-richclient-core without a problem.
Because the module directories
The module refactor had nothing do with it.
In fact
repository
idspringRichclientRepository/id
nameSpring rich client repository/name
urlfile:${basedir}/maven2repository/url
snapshots
enabledtrue/enabled
hi Brett,
thanks so much the following tag is working fine!
outputDirectory${project.build.directory}/lib/outputDirectory
firstly, I would like to thanks to all Maven's developer for the hard
work.
M2 is exactly what I am dreaming to have for a long time.
I just hope m2 could be more
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
With the changes you *can* now do this in the jar-plugin: ...
to achieve what you are doing, you *can* also use a custom
assembly descriptor, ...
I think he was saying that its not just a matter of what *can* be done,
On 1/7/06, Christopher Cobb [EMAIL PROTECTED] wrote:
I think he was saying that its not just a matter of what *can* be done, it's
a matter of things just working. The constellation of maven plugins
should be set up so that you *normally* don't have customize a descriptor
over here to make
Man-Chi Leung wrote:
how can I change the generated jar location from default
project_dir/target/ to project_dir/target/lib?
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
basedir
basedir/target/lib/basedir I want to
do something like this. but ERROR!
archive
manifest
addClasspathtrue/addClasspath
mainClasscom.ever.beetles.SimpleJxtaApp/mainClass
project_dir/target/ to project_dir/target/lib?
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
basedir/target/lib/basedir I want to
do something like
basedir/target/lib/basedir I want
to do something like this. but ERROR!
archive
manifest
addClasspathtrue/addClasspath
mainClasscom.ever.beetles.SimpleJxtaApp/mainClass
Hmm.
I just saw that basedir is not basedir, but the directory I was
expecting. And outputDirectory is already used.
Since both are readonly, I think there is no harm in renaming them.
I'll do that now.
- Brett
On 1/6/06, Henry Isidro [EMAIL PROTECTED] wrote:
Brett Porter wrote:
It's
?
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
configuration
basedir/target/lib/basedir I
want to
do something like this. but ERROR!
archive
manifest
On 1/6/06, Man-Chi Leung [EMAIL PROTECTED] wrote:
hi Brett,
I believe this issue is more important than just a path configuration.
You've misunderstood. With the changes you can now do this in the jar-plugin:
outputDirectory${project.build.directory}/lib/outputDirectory
so the jar appears in
/war into your artifact for install or deploy)
-Original Message-
From: Man-Chi Leung [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 05, 2006 11:52 PM
To: Maven Users List
Subject: Re: [m2] how to change maven-jar-plugin's basedir ?
hi Brett,
I believe this issue is more important
basedir/target/lib/basedir I want to do something
like this. but ERROR!
archive
manifest
addClasspathtrue/addClasspath
Hi all,
I'm trying to access a directory which is on the same level as ${basedir} like
projects
maven project
resource dir
running maven from maven project I'm trying to access the resource dir
within maven.xml to copy a file, and I didn't find any way to specify relative
path
Hi all,
I'm trying to access a directory which is on the same level as ${basedir} like
projects
maven project
resource dir
running maven from maven project I'm trying to access the resource dir
within maven.xml to copy a file, and I didn't find any way to specify relative
path
Hi all,
I'm trying to access a directory which is on the same level as ${basedir} like
projects
maven project
resource dir
running maven from maven project I'm trying to access the resource dir
within maven.xml to copy a file, and I didn't find any way to specify relative
path
something like ${basedir}/../resource dir/file.txt (this doesn't work) ?
Is there a space in 'resource dir'? Can you try if it works with
directories without spaces?
-Lukas
-
To unsubscribe, e-mail: [EMAIL PROTECTED
hi,
according to http://maven.apache.org/plugins/maven-ejb-plugin/ejb-mojo.html
the ejb plugin has a basedir/ parameter that has the description
The directory for the generated EJB. i need to create multiple
versions of the EJB and its client so i added this to the
configuration of the plugin
On 11/15/05, Anuerin Diaz [EMAIL PROTECTED] wrote:
hi,
according to http://maven.apache.org/plugins/maven-ejb-plugin/ejb-mojo.html
the ejb plugin has a basedir/ parameter that has the description
The directory for the generated EJB. i need to create multiple
versions of the EJB and its
There seems to be a bug when you use ${basedir} inside of
module{$basedir}/somemodule/module
For example, if your basedir is d:\app\module2, it expands to
d:\app\module2d:\app\module2
On Mon, 2005-10-31 at 07:26 -0800, Frank Mena wrote:
There seems to be a bug when you use ${basedir} inside of
module{$basedir}/somemodule/module
For example, if your basedir is d:\app\module2, it expands to
d:\app\module2d:\app\module2
Don't specify a ${basedir}. This is a bad habit left
${basedir} for the parent pom
(Would be nice to have ${parent.pom.basedir}
BTW, does this mean that there is not a bug in ${basedir} used in module?
On 10/31/05, Jason van Zyl [EMAIL PROTECTED] wrote:
On Mon, 2005-10-31 at 07:26 -0800, Frank Mena wrote:
There seems to be a bug when you use
Porter [EMAIL PROTECTED]:
basedir is always the location of the POM file, it can't be changed.
You can do something using custom properties in the POM. Note however
that using relative paths including .. is discouraged as it prevents
the subprojects from being checked out and built in isolation
I've filed MNG-805 to look into this.
- Brett
On 8/30/05, Trygve Laugstøl [EMAIL PROTECTED] wrote:
On Tue, Aug 30, 2005 at 01:59:52AM +0200, [EMAIL PROTECTED]:
Hei,
I have recognised that the evaluation of ${basedir} has changed from my
Maven2 build on 23.august to the one I
to look into this.
|
| - Brett
|
| On 8/30/05, Trygve Laugstøl [EMAIL PROTECTED] wrote:
|
|On Tue, Aug 30, 2005 at 01:59:52AM +0200, [EMAIL PROTECTED]:
|
|Hei,
|
|I have recognised that the evaluation of ${basedir} has changed from my
|Maven2 build on 23.august to the one I downloaded and built on 29
recognised that the evaluation of ${basedir} has changed from my
|Maven2 build on 23.august to the one I downloaded and built on
29.august
|
|.
|
|Building with Maven2 of 23.august would give the value of the actual
|directory where the POM is situated also when this POM is deep down
Title: [M2] - The value of ${basedir} has changed?
Hei,
I have recognised that the evaluation of ${basedir} has changed from my Maven2 build on 23.august to the one I downloaded and built on 29.august.
Building with Maven2 of 23.august would give the value of the actual directory where
relative to the parent POM level rather then child POM.
[EMAIL PROTECTED] wrote:
Hei,
I have recognised that the evaluation of ${basedir} has changed from
my Maven2 build on 23.august to the one I downloaded and built on
29.august.
Building with Maven2 of 23.august would give the value
On Tue, Aug 30, 2005 at 01:59:52AM +0200, [EMAIL PROTECTED] wrote:
Hei,
I have recognised that the evaluation of ${basedir} has changed from my
Maven2 build on 23.august to the one I downloaded and built on 29.august.
Building with Maven2 of 23.august would give the value of the actual
Did you file a JIRA issue for this?
On 5/2/05, Corey Klaasmeyer [EMAIL PROTECTED] wrote:
It's basedir.
Corey
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, May 02, 2005 4:45 PM
To: Maven Users List
Subject: Re: scm:bootstrap-project does
I'm using scm:bootstrap-project with Maven, and I would expect
${basedir} to be updated to the directory of the clean checkout
directory after doing an scm:bootstrap-project, but that doesn't seem to
be the case. Here is the
start maven output ==
maven.scm.bootstrap.goals
:05 PM
To: Maven Users List
Subject: Re: scm:bootstrap-project does not update ${basedir}
${basedir} should be, but ${user.dir} is not - it is run inside a
reactor. Is this not the case?
- Brett
On 5/3/05, Corey Klaasmeyer [EMAIL PROTECTED] wrote:
I'm using scm:bootstrap-project with Maven, and I
No, I mean Maven essentially runs a reactor to start the new project,
so the basedir variable should be set, but the current working
directory will remain where you started Maven from.
- Brett
On 5/3/05, Corey Klaasmeyer [EMAIL PROTECTED] wrote:
I don't know whether it's running inside
Back to the original question: is this a bug or am I missing something?
Corey
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, May 02, 2005 4:21 PM
To: Maven Users List
Subject: Re: scm:bootstrap-project does not update ${basedir}
No, I mean Maven
It depends :)
Is it the basedir variable that is set incorrectly, or the working directory?
If it is basedir - it is a bug.
- Brett
On 5/3/05, Corey Klaasmeyer [EMAIL PROTECTED] wrote:
Back to the original question: is this a bug or am I missing something?
Corey
-Original Message
It's basedir.
Corey
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Monday, May 02, 2005 4:45 PM
To: Maven Users List
Subject: Re: scm:bootstrap-project does not update ${basedir}
It depends :)
Is it the basedir variable that is set incorrectly, or the working
Is there a property for specifying the ${basedir} of the highest level
of my pom inheritnace tree?
Thanks,
Ben
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
the ${basedir} of the highest level
of my pom inheritnace tree?
Thanks,
Ben
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
${basedir} refers to maven/. However, this means
that when I try to run a cvs update, it only updates the maven/
directory, and as far as I can see, there is no way to do a cvs up ../
Does anyone know a solution to this problem? Ideally, I'd set ${basedir}
to be ../, but if there's some way
Simple: because I have a project directory with a subdir for IDEA, Together
and (hopefully) Maven, instead of having the project files cluttering around
in the basedir. Therefore it would be nice not to have to change all
settings when moving the project file but only one.
I just wanna know
Its possible to move the project file (I understand why you want that), but
not possible to move basedir. You'll have to edit project.xml and
project.properties to include '..'
Alternatively, you could set myBaseDir=${basedir}/.. And use ${myBaseDir}
instead of ${basedir} in your project
Good idea. Thanks a lot.
-- Daniel
-Ursprüngliche Nachricht-
Von: Brett Porter [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 15. April 2004 09:55
An: 'Maven Users List'
Betreff: RE: how can I change ${basedir}
Its possible to move the project file (I understand why you
want
I would be interested in the same subject. No response since over one year
on that?
Daniel
Date: Mon, 17 Mar 2003 15:08:32 -0500
From: Justinus Menzel [EMAIL PROTECTED]
Subject: how can I change ${basedir}
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi,
I moved
]
Sent: Thursday, 15 April 2004 9:58 AM
To: 'Maven Users List'
Subject: how can I change ${basedir}
I would be interested in the same subject. No response since
over one year on that?
Daniel
Date: Mon, 17 Mar 2003 15:08:32 -0500
From: Justinus Menzel [EMAIL PROTECTED]
Subject: how
That was the problem, I am using (the released) RC1.
Thanks!
--
Svetlin
Emmanuel Venisse wrote:
Do you work with changelog plugin present in cvs head. changelog basedir
option isn't in released version of plugin
Emmanuel
- Original Message -
From: Svetlin Stanchev [EMAIL PROTECTED
Do you work with changelog plugin present in cvs head. changelog basedir
option isn't in released version of plugin
Emmanuel
- Original Message -
From: Svetlin Stanchev [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Monday, February 09, 2004 4:04 AM
Subject: setting
maven.scm.checkout.dir = ${basedir}/checkouts
is also standard resulting in the dir structure
M:\module\checkouts\module
I am able to compile with these settings.
Now how do I specify that the changelog report should be run against
this checkout directory? I tried to set in project.properties
Ok, so it is definitely the maven.gen.docs property that is
getting mauled.
I can't see anything wrong with the plugin code - maybe it is a bug in the
lazy plugin installation. What happens if you plugin:install the readme
plugin and remove the dependency?
As soon as I remove the
Can you come up with a small test case and file it in JIRA?
Thanks,
Brett
-Original Message-
From: Oliver Nölle [mailto:[EMAIL PROTECTED]
Sent: Thursday, 22 January 2004 7:06 PM
To: Maven Users List
Subject: AW: ${basedir} modified on invoking a plugin?
Ok, so
-Ursprüngliche Nachricht-
Von: Brett Porter [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 20. Januar 2004 23:26
An: 'Maven Users List'
Betreff: RE: ${basedir} modified on invoking a plugin?
You'll probably need a smaller test case to make this replicatable enough
for JIRA.
Have
-
From: Oliver Nölle [mailto:[EMAIL PROTECTED]
Sent: Thursday, 22 January 2004 3:21 AM
To: Maven Users List
Subject: AW: ${basedir} modified on invoking a plugin?
-Ursprüngliche Nachricht-
Von: Brett Porter [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 20. Januar 2004 23:26
I have the following problem:
On invoking maven site the site gets created in the target directory of a
plugin, not the target directory of the project from which I invoke maven
site.
More precisely
- my project contains a postgoal to java:compile in its maven.xml, which
calls a goal of a
was
changed.
Cheers,
Brett
-Original Message-
From: Oliver Nölle [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 20 January 2004 9:49 PM
To: Maven Users List
Subject: ${basedir} modified on invoking a plugin?
I have the following problem:
On invoking maven site the site gets created
to a ${basedir}
issue. The subproject looks for the jars in ../lib/ejb.jar, but when
running from the parent directory that path doesn't exist.
I've tried putting ${basedir}/../lib/ejb.jar into the
project.properties, but that doesn't work either. I've tried putting a
project.properties in the trunk
I'm having problems with properties in project.properties involving
relative paths:
For the top-most maven.xml/project it points to ./aDirectory
For the subsequent directories i've for a shared project.properties that
has the property set to ../aDirectory.
When I use the reactor at the top it
Hello,
In the POM we have found that dependencies can have war, jar and ear properties:
e.g.
properties
war.bundletrue/war.bundle
/properties
What other properties can be defined for a POM dependency.
Cheers
Neil
-
To
to absolute by prepending ${basedir}
makes sense (and ${basedir} should probably be put through a
getAbsoluteFile() too).
Agreed - ${pom.build.sourceDirectory} should always return an absolute
path, because most of the time that's what a plugin will want.
There are occasions when a plugin will want
to
chdir, setting all File objects to absolute by prepending ${basedir}
makes sense (and ${basedir} should probably be put through a
getAbsoluteFile() too).
Yeah, true. It's probably not possible to reliably identify relative
paths in maven.xml scripts. Not without making all the jelly tags aware
On Mon, 2003-06-23 at 14:42, Brett Porter wrote:
There are two alternatives:
1) assume all of these paths are relative to project.xml.
I'd vote for this one unless someone can explain...
2) require all to be absolute paths (using basedir where needed to know
where project.xml lives
Mark H. Wilkinson wrote:
On Mon, 2003-06-23 at 14:42, Brett Porter wrote:
There are two alternatives:
1) assume all of these paths are relative to project.xml.
I'd vote for this one unless someone can explain...
If you vote for this one, do you also allow ${basedir}?
2) require all
101 - 196 of 196 matches
Mail list logo
