hi lakshmi,
try this
properties
basedirYOUR DIRECTORY HERE/basedir
/properties
is this what you are looking for?
Thanks
aravi
Lakshmi Kurella wrote:
Can someone tell me what path $basedir points to and how can I alter
this.
Thank you,
LK
--
View
On Thu, Aug 7, 2008 at 8:06 PM, Lakshmi Kurella [EMAIL PROTECTED] wrote:
Can someone tell me what path $basedir points to and how can I alter
this.
$basedir is the root of the project that's being built. I'm not sure
you can change it.
What problem are you trying to solve? There's probably
Shouldn't ${basedir} be resolved correctly on both windows and *nix?
If that's the case, you could try using the '/' separator, since this works
both on *nix and windows...
However, if ${basedir} is not correctly resolved, you will probably still have
the same issues...
On Friday 07 September
Hello,
Use 2 profiles that are auto-activated based on OS and hard-code the
proper value in both.
Wayne
Doesn't the defeat the purpose of having an environment portable build?
And when I use ${basedir} I can't insert two ${file.separator}'s
inside of that variable.
I.E.
Use 2 profiles that are auto-activated based on OS and hard-code the
proper value in both.
Wayne
On 9/7/07, Andrew Leer [EMAIL PROTECTED] wrote:
Hello all,
I am using Maven2 on Windows XP
Lets say that I have this property in my pom.xml file:
There are *always* some small differences in environments. Therefore,
profiles are a way of handling those differences in Maven.
${file.separator} is simply not valid/available at this time for use
in the pom. Feel free to file an RFE.
Wayne
On 9/7/07, Andrew Leer [EMAIL PROTECTED] wrote:
Thanks Wayne...
Submitted a bug...
http://jira.codehaus.org/browse/MNG-3198
Thanks,
Andrew J.Leer
On 9/7/07, Wayne Fay [EMAIL PROTECTED] wrote:
There are *always* some small differences in environments. Therefore,
profiles are a way of handling those differences in Maven.
/project/module1, that would help. Instead we'll continue to
use relative paths.
Bummer...
-Original Message-
From: pjungwir [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 25, 2006 3:51 PM
To: users@maven.apache.org
Subject: RE: basedir
Oh, okay. By default, all paths are relative
${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?
?
-Original Message-
From: pjungwir [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 25, 2006 2:35 PM
To: users@maven.apache.org
Subject: Re: basedir
${basedir} :-)
Technically, this gives the directory where the pom is located, not the
directory from which you run mvn.
Paul
EJ
?
-Original Message-
From: pjungwir [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 25, 2006 2:35 PM
To: users@maven.apache.org
Subject: Re: basedir
${basedir} :-)
Technically, this gives the directory where the pom is located, not the
directory from which you run mvn.
Paul
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
: Wednesday, October 25, 2006 3:31 PM
To: users@maven.apache.org
Subject: RE: basedir
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
}/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
Ahh - I'm not talking about having it IN a resource, I'm
]
Sent: Wednesday, October 25, 2006 3:51 PM
To: users@maven.apache.org
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
continue to
use relative paths.
Bummer...
-Original Message-
From: pjungwir [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 25, 2006 3:51 PM
To: users@maven.apache.org
Subject: RE: basedir
Oh, okay. By default, all paths are relative to basedir already, so I'm
not
sure why you'd need
I just noticed that the resources plugin supports an outputDirectory
configuration element. So you could try a relative targetPath and an
absolute outputDirectory. Note that the former is on the resource
itself; the latter, on the plugin's configuration.
Paul
--
View this message in context:
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
No you can't.
It would be better to use an url to reference your clover license file.
Emmanuel
Ingo Düppe a écrit :
Hello,
is it possible in a multi module project to reference a directory in an
absolute manner of the super pom?
Independent of the current position I like to reference a
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.
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
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 (which is the parent of the eportal-web module,
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
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 not
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
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
Thanks for the quick reply. I am trying to convert from ant to maven in a
large project and am excited at the prospect of using maven.
As an example, I have the following directory structure:
common
common1
common2
subcommon
subcommon1
subcommon2
project1
some1model1
some1model2
war
ear
project2
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 it is
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 you got any weird project.properties or plugin.properties?
Nop.
I checked my personal build.properties
You'll probably need a smaller test case to make this replicatable enough
for JIRA.
Have you got any weird project.properties or plugin.properties?
Maybe you can try outputting ${maven.build.dir} in your plugin to see
whether it is that that is changed, or whether the docs output directory was
34 matches
Mail list logo
