Thu, 21 Dec 2023 09:10:44 +0100, /Slawomir Jaranowski/:
Release under vote ... you can check candidate version:
https://lists.apache.org/thread/scb8qw1or396l4hqgf5h78z5h0km60z4
Tried maven-compiler-plugin 3.12.1 from the staging repository – no
error during the build.
--
Stanimir
Hi,
Release under vote ... you can check candidate version:
https://lists.apache.org/thread/scb8qw1or396l4hqgf5h78z5h0km60z4
śr., 20 gru 2023 o 21:04 Slawomir Jaranowski
napisał(a):
> Hi
>
> MCOMPILER-379 - was about missing SourcesDirectory and we have IT for it:
>
Hi
MCOMPILER-379 - was about missing SourcesDirectory and we have IT for it:
https://github.com/apache/maven-compiler-plugin/commit/6fd3a46885edd81e62ae62cfc798c1e1b903e170
MCOMPILER-567 - is for missing generated-sources/annotations - now we also
have IT for it:
Hello Sławomir,
Do you know if MCOMPILER-379 is the same issue as MCOMPILER-567 ? If so,
shouldn't the IT test in MCOMPILER-379 have caught it?
Greg
Hi,
I faced the similar error
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.12.0:testCompile
(default-testCompile)
Fatal error compiling:
basedir ...\target\generated-test-sources\test-annotations-java does not exist
-> [Help 1]
and investigating I
..
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.12.0:compile
> (java9-compile) on project xbrz-core: Fatal error compiling: basedir
> C:\...\xbrz-java\xbrz-core\target\generated-sources\annotations does not
> exist -> [Help 1]
>
> that
"windows"
...
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.12.0:compile
(java9-compile) on project xbrz-core: Fatal error compiling: basedir
C:\...\xbrz-java\xbrz-core\target\generated-sources\annotations does not
exist -> [Help 1]
tha
Hi,
I have parent pom.xml and I have modules there, structure is like this:
pom.xml
module1/
module2/
module3/
some_dir1/
some_dir2/
README.adoc
When I want to release this project, I do it like
mvn release:prepare release:perform
What it does is that when I look into sources of parent
users@maven.apache.org
Betreff: How to exclude directory in Maven in basedir from adding sources
torelease?
Hi,
I have parent pom.xml and I have modules there, structure is like this:
pom.xml
module1/
module2/
module3/
some_dir1/
some_dir2/
README.adoc
When I want to release this project, I do
Betreff: How to exclude directory in Maven in basedir from adding sources
torelease?
Hi,
I have parent pom.xml and I have modules there, structure is like this:
pom.xml
module1/
module2/
module3/
some_dir1/
some_dir2/
README.adoc
When I want to release this project, I do it like
Replies:
To Jeff: Yes, that doesn't work; it still assumes the basedir is the
parent directory of the POM.
To Baptiste: I'll look into it, thanks for the pointer.
On Thu, Jun 13, 2013 at 8:13 PM, David P. Caldwell
da...@code.davidpcaldwell.com wrote:
The use case is that I have a project
Maven, and then overwriting the updates
with the original (hope the process doesn't crash in a way that
prevents me from restoring the original). I'd probably lean toward the
last but it's more cumbersome and error-prone than I'd like. Is what
I'd like possible?
You cannot modify the basedir, i.e
and error-prone than I'd like. Is what
I'd like possible?
You cannot modify the basedir, i.e your generated POM has to be at same
location with a different name. You might select a name pattern that is
ignored by your SCM e.g. pom.tmp. As Jeff said, call Maven like
mvn -f pom.tmp
However, keep
Ron asks:
Why?
What is the problem that you are actually trying to solve?
I explained it at more length in the original question, but more
succinctly: I want to be able to execute a project with an arbitrary
POM file without modifying the original source repository or source
working directory in
development need.
If you can tell us this, there might be a solution that builds the
artifacts that you need and does not require changing the basedir.
Ron
On Thu, Jun 13, 2013 at 8:13 PM, David P. Caldwell
da...@code.davidpcaldwell.com wrote:
The use case is that I have a project (actually
The use case is that I have a project (actually, many projects, so I
want to be able to do this in bulk) that are source-controlled and I'd
like to be able to create a modified version of the POM in a temporary
directory and then execute that modified POM, but against the original
base directory
Have you tried the mvn -f param? mvn -f path/to/pom/generated.pom from the
source tree base dir. Inverts what you are thinking of...
On Thu, Jun 13, 2013 at 7:13 PM, David P. Caldwell
da...@code.davidpcaldwell.com wrote:
The use case is that I have a project (actually, many projects, so I
I think this is what the sonar maven plugin does. Maybe you should have a
look at its sources.
My 2 cents.
Cheers
Le 14 juin 2013 03:20, Jeff Jensen jeffjen...@upstairstechnology.com a
écrit :
Have you tried the mvn -f param? mvn -f path/to/pom/generated.pom from the
source tree base dir.
:Re: maven-antrun-plugin and ant basedir question
I am trying to do a custom build of Dojo using Maven and the Dojo
supplied
build.xml file. I have managed to get most of the pieces that I need
into
the pom.xml file to where the ant clean task works and the default task
starts
The build.xml file is part of the Dojo distribution. I would like to
avoid modifying their files as Dojo is being updated all the time. So
I strongly doubt their build.xml file is being updated all the time.
I would just edit this one spot and then keep an eye for changes to
this file so you
of basedir
which is set to . at the top of the build.xml file (project name=dojo
default=cldr basedir=.). Since Maven is not running from the
directory where the build.xml file is at, all the paths are wrong. In my
pom.xml file I have tried to override this value by adding, property
name=basedir
I am trying to do a custom build of Dojo using Maven and the Dojo supplied
build.xml file. I have managed to get most of the pieces that I need into
the pom.xml file to where the ant clean task works and the default task
starts. Unfortunately the default task depends on the value of basedir
generation:
Error rendering Maven report: Failed during checkstyle execution: Failed
during checkstyle configuration: unable to read
D:\IDE\workspaces\current\score_common\target\checkstyle-checker.xml -
unable to parse configuration stream - Property ${basedir} has not been
set - [Help 1
On 02/15/2011 12:58 PM, Steve Cohen wrote:
I can set the permissions of fileSets and moduleSets and
dependencySets in the maven-assembly-plugin, but it seems from the
online documentation that I can't do so on the baseDir. What is more,
when assembling a zip format, the perms default to 777
I can set the permissions of fileSets and moduleSets and
dependencySets in the maven-assembly-plugin, but it seems from the
online documentation that I can't do so on the baseDir. What is more,
when assembling a zip format, the perms default to 777. At least
that's what I get when I unzip
Andreas Sewe wrote:
Hi,
I need to invoke an external command using the Exec plugin, with one of
the
arguments equal to ${basedir}/target. The problem is that under Windows
this expands to c:\\temp\\project/target because ${basedir} uses
Windows-style slashes whereas the rest
cowwoc wrote:
... one of the arguments equal to ${basedir}/target.
maybe I'm missing something here, but why won't ${project.build.directory}
work?
--
View this message in context:
http://maven.40175.n5.nabble.com/Passing-basedir-into-Exec-plugin-tp512272p696566.html
Sent from the Maven
cowwoc wrote:
Andreas Sewe wrote:
Hi,
I need to invoke an external command using the Exec plugin, with one of
the
arguments equal to ${basedir}/target. The problem is that under
Windows
this expands to c:\\temp\\project/target because ${basedir} uses
Windows-style slashes whereas
lukewpatterson wrote:
cowwoc wrote:
... one of the arguments equal to ${basedir}/target.
maybe I'm missing something here, but why won't ${project.build.directory}
work?
nevermind, I see what you are saying now, you want a general way to create a
String parameter value
/browse/mojo/trunk/mojo/exec-maven-plugin/src/main/java/org/codehaus/mojo/exec/AbstractExecMojo.java?r=HEAD#l155
try (with the quotes)
${basedir}${file.separator}target${file.separator}lib
interestingly though,
\ or \a or a\
throw error args contains not properly formatted string
but a\a is ok
lukewpatterson wrote:
ok, and then the plugin does some massaging, and '\' is an escape
character
http://fisheye.codehaus.org/browse/mojo/trunk/mojo/exec-maven-plugin/src/main/java/org/codehaus/mojo/exec/AbstractExecMojo.java?r=HEAD#l155
try (with the quotes)
${basedir
to be
fixed too.
Either way, might as well file the bug so you can leave some clues to follow
for others experiencing the same obstacle.
--
View this message in context:
http://maven.40175.n5.nabble.com/Passing-basedir-into-Exec-plugin-tp512272p704257.html
Sent from the Maven - Users mailing list
Hi,
I need to invoke an external command using the Exec plugin, with one of the
arguments equal to ${basedir}/target. The problem is that under Windows
this expands to c:\\temp\\project/target because ${basedir} uses
Windows-style slashes whereas the rest of the argument uses Unix-style
slashes
ah, that is really overkill :-)
On Thu, Jul 1, 2010 at 12:08 AM, Andreas Sewe
s...@st.informatik.tu-darmstadt.de wrote:
Hi,
I need to invoke an external command using the Exec plugin, with one of
the
arguments equal to ${basedir}/target. The problem is that under Windows
this expands to c
Hi,
I need to invoke an external command using the Exec plugin, with one of the
arguments equal to ${basedir}/target. The problem is that under Windows
this expands to c:\\temp\\project/target because ${basedir} uses
Windows-style slashes whereas the rest of the argument uses Unix-style
slashes
lookup maven profile where you can configure your properties to
${basedir}\\target when on windows platform
-D
On Wed, Jun 30, 2010 at 9:26 PM, cowwoc cow...@bbs.darktech.org wrote:
Hi,
I need to invoke an external command using the Exec plugin, with one of the
arguments equal to ${basedir
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
Hasn't anyone faced this problem? I really need some help there..
--
View this message in context:
http://www.nabble.com/Backslash-colon-problem-with-%24%7Bbasedir%7D-using-maven-plugin-tools-ant-tp24111308p24142465.html
Sent from the Maven - Users mailing list archive at Nabble.com.
=== Problem solved ===
The ${basedir} variable was replaced because in the project's POM I had
specified filteringtrue/filtering for the directory enclosing the Ant
script file.
I still think there is a bug in the Ant plugin (adding the backslash before
the colon).
--
View this message
basedir=.
target name=info
mkdir dir=${basedir}/foo /
/target
/project
Upon calling mvn clean package, this file is copied in the
target/classes directory, with the following content:
project name=build_foo default=info basedir=.
target name=info
Why does mvn package transform ${basedir} to a hard-coded directory
anyway? I don't see any particular reason for doing this...
--
View this message in context:
http://www.nabble.com/Backslash-colon-problem-with-%24%7Bbasedir%7D-using-maven-plugin-tools-ant-tp24111308p24111587.html
Sent from
tried defining property in pom.xml as shown below
properties
basedirC:\src\main\java/basedir
/properties
but still it didn't work,
I also use some systempath variables in my dependency as shown below
dependency
groupIdjavax/groupId
artifactIdj2ee
\pom.xml
it was reading this file. but its taking base dir has
C:\my-mvn\pom.xml i tried defining property in pom.xml as shown below
properties
basedirC:\src\main\java/basedir
/properties
but still it didn't work,
I also use some systempath variables in my dependency as shown below
]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] basedir C:\dev\workspace\dashboard-web\src\main\webapp\js? does not
exist
[INFO
Can someone tell me what path $basedir points to and how can I alter
this.
Thank you,
LK
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
Hi the list,
I'm trying to use the Maven Javadoc Plugin to generate a documentation
using a custom Java doclet. A trouble persists. My pom uses an
additionalparam section to
configure the doclet as below :
additionalparam
-index ${basedir}/src/site/docbook/reference/index.xml
Are you using the text ${basedir} in your Checkstyle configuration file?
Hart, Leo wrote:
I'm trying to migrating my build process from Ant to Maven and have been
struggling quite a bit so far.
I want to integrate CheckStyle into the build, so I've added the
following:
reporting
plugins
Brian,
I did as you suggested and changed configLocation to:
configLocation${basedir}/config/checkstyle-rules.xml/configLocation
I'm getting the same message:
C:\workspace\sharesmvn checkstyle:check -e
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Searching
] An error has occurred in Checkstyle report generation.
Embedded error: Failed during checkstyle configuration
Property ${basedir} has not been set
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException
That is a weird one, but try changing your configLocation to :
configLocation${basedir}/config/CheckStyle Rules.xml/configLocation
This will give an absolute path to checkstyle. You also might want to
get rid of the space in the file name.
-Original Message-
From: Hart, Leo [mailto
Hi,
Maybe I'm not understanding something basic here, but in my JAR project
I am finding that folders in my basedir are getting copied into
target/classes when I compile. I really didn't expect this behaviour. I
thought target/classes only loaded up with stuff under src? Any ideas
please?
TIA
igore this post ty
Eurobase International Limited and its subsidiaries (Eurobase) are unable to
exercise control over the content of information in E-Mails. Any views and
opinions expressed may be personal to the sender and are not necessarily those
of Eurobase. Eurobase will not enter into
I want to convert:
fileString = FileUtils.getStringFromFile(
C:\\viewstore\\esp_lynx_dap\\esp\\dap\\utilities\\common\\common-jar\\src\\test\\resources\\test.txt);
into something like:
fileString = FileUtils.getStringFromFile(
${basedir}\\src\\test
\\common\\common-jar\\src\\test\\resources\\test.txt);
into something like:
fileString = FileUtils.getStringFromFile(
${basedir}\\src\\test\\resources\\test.txt);
inside my junit test. Is there a way to do this?
--
Thanks,
Mick Knutson
http
What would you want to use this basedir property for? Maven has a
different mindset for referencing resources within a project than ant.
I'm sure if you describe your use case here someone will show you the
maven way to do things.
I'm using maven to call a ant-build file that is in another
Users List
Subject: Re: Ant basedir
What would you want to use this basedir property for? Maven has a
different mindset for referencing resources within a project than ant.
I'm sure if you describe your use case here someone will show you the
maven way to do things.
I'm using maven to call a ant
Hi,
How do I set ant basedir from maven?
I was trying something like that:
*ant basedir=/tmp/test antfile=build.xml*
but there is no basedir attribute.
Thanks,
Luis
What would you want to use this basedir property for? Maven has a
different mindset for referencing resources within a project than ant.
I'm sure if you describe your use case here someone will show you the
maven way to do things.
Rgds,
ste
-Original Message-
From: Luis Roberto P
Hi Yaakov,
Not sure if this is your problem, but
${project.build.directory} refers to the target directory.
${project.directory} refers to the directory that contains the src
directory. Also I am wondering why you have the context.xml file where you
do in src/resources, and not in
I got mixed up when typing up the email. I do have the context.xml in
src/test/resources.
Either way, I am not sure why the FileNotFoundException cites the
literal string: ${project.build.directory} and not the absolute path.
Yaakov.
On 10/28/07, Nicole Lacoste [EMAIL PROTECTED] wrote:
Hi
Hi Yaakov,
Do I understand right that the ${project.build.directory} in in a file that
is not a pom? I don't think that if gets resolved outside of pom files.
Try just the name of the file aim-validator.properties instead of ${
project.build.directory}/aim-validator.properties. If it is in
Wait a second... If I am pretty new to maven, so...
I did tell maven in my pom.xml that I want the directory
src/test/resources filtered. So, why wouldn't it filter it? OR are you
saying that I have to create a 'filters' directory and place a
property file there and use THAT to filter things?
I don't know about filters. But maven sees src/test/resources, so you can
refer to stuff directly. Did you try it? Are you still getting the same
error?
Nicole
On 28/10/2007, Yaakov Chaikin [EMAIL PROTECTED] wrote:
Wait a second... If I am pretty new to maven, so...
I did tell maven in
A nice test to do would be:
constructor-arg index=0 value=${pom.artifactId}/aim-validator.properties
/
That way, if you get FileNotFoundException citing the file location
your-artifact-id/aim-validator.properties, then the problem is (somehow)
with the ${project.build.directory}. If you get a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaakov Chaikin wrote:
Wait a second... If I am pretty new to maven, so...
I did tell maven in my pom.xml that I want the directory
src/test/resources filtered. So, why wouldn't it filter it? OR are you
saying that I have to create a 'filters'
clamb wrote:
Jörg Schaible-2 wrote:
Why don't you simply keep those filters in an own module and pack them
into
an archive? Every other project that needs to access them may declare a
dep
on that artifact and can user the build-helper plugin to unpack them into
a
temporary location.
Hi,
I have a spring context XML file in src/resourses/context.xml. I need
to refer to a property file inside the context.xml file, so I have the
following line there:
constructor-arg index=0
value=${project.build.directory}/aim-validator.properties/
I also have this in my pom.xml:
build
OK, i've been fighting this battle for a few days now and have a fairly ugly
solution.
in every pom.xml define a common root property:
properties
rootPOM${basedir}/..//rootPOM
/properties
Ensure that you have enough ../ to reference the rootPOM directory.
Everywhere you need to refer
deep tree of projects?
Sincerely,
Matthew McCullough
Managing Partner
Ambient Ideas, LLC
clamb wrote:
OK, i've been fighting this battle for a few days now and have a fairly
ugly solution.
in every pom.xml define a common root property:
properties
rootPOM${basedir}/..//rootPOM
defs${rootPOM}/genericFilters/defs
/configuration
...
/plugin
/plugins
/pluginManagement
/build
-MatthewsProject rootPOM${basedir}/rootPOM
+Core
clamb wrote:
Matthew McCullough wrote:
This is a creative idea, but appears only to work if your leaf nodes of
the project are all at the same level so that the ../../ is consistently
just the right amount back up the directory tree.
Yeah ... that is a limitation. However, once you
('cause i need to
filter them) for all 12 of my sub-projects vs: have my sub-project simply
point to the filter in the parent.
--
View this message in context:
http://www.nabble.com/How-can-I-get-the-path-for-a-root-pom.xml%27s-basedir-in-a-multimodule-project-with-pom-inheritance-tf4577123s177.html
a solution in the thread though:
http://mail-archives.apache.org/mod_mbox/maven-continuum-users/200701.mbox/[EMAIL
PROTECTED]
Matthew McCullough wrote:
Maven users,
Is there a way to retrieve the super, or super-super pom.xml's ${basedir}
such that it consistently returns the rootmost
.
Can't find a solution in the thread though:
http://mail-archives.apache.org/mod_mbox/maven-continuum-users/200701.mbox/[EMAIL
PROTECTED]
Matthew McCullough wrote:
Maven users,
Is there a way to retrieve the super, or super-super pom.xml's
${basedir}
such that it consistently returns
Maven users,
Is there a way to retrieve the super, or super-super pom.xml's ${basedir}
such that it consistently returns the rootmost pom.xml's path? It appears
that ${basedir} is always the leafmost pom's path when running a multimodule
build.
So, for example:
1) I have a pom.xml at the root
, or super-super pom.xml's ${basedir}
such that it consistently returns the rootmost pom.xml's path? It
appears that ${basedir} is always the leafmost pom's path when running a
multimodule build.
So, for example:
1) I have a pom.xml at the root of my tree.
2) I have pom.xmls
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 all,
I am using Maven2 on Windows XP
Lets say that I have this property in my pom.xml file:
log.app.directory${basedir}${file.separator}log${file.separator}/log.app.directory
This property is being used to write the location of a directory for
holding log files, to a log4j.xml
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.
${basedir}=C
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:
log.app.directory${basedir}${file.separator
:
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.
${basedir}=C
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.
${basedir}=C:\workspace\dev\projectTest
(under windows)
I can't add an extra path separator that way
Thank you,
Andrew J
Hi!
I have read some documents and books about Maven and I am not able to find a
list which describes variables like ${basedir}.
Regards,
Raul
--
View this message in context:
http://www.nabble.com/How-to-set-variables-like-%24%7Bbasedir%7D-tf3950655s177.html#a11208298
Sent from the Maven
http://sonatype.com/book/properties.html
Andy
On 20 Jun 2007, at 08:08, capira wrote:
Hi!
I have read some documents and books about Maven and I am not able
to find a
list which describes variables like ${basedir}.
Regards,
Raul
--
View this message in context: http://www.nabble.com
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Monday, May 14, 2007 7:06 PM
To: Maven Users List
Subject: RE: Parent POM and basedir
Can PMD find things on the classpath the way Checkstyle can? In that
case, deploy a jar with your rules, and add it as a build extension so
On 5/15/07, Chris Helck [EMAIL PROTECTED] wrote:
Can you explain what you mean? I've already set things up with the
extension but I'd rather change it now if that is the right thing to do.
How can I make my rules file be a dependency of the PMD plugin? Do I
have to recreate my own version of
Can PMD find things on the classpath the way Checkstyle can? In that
case, deploy a jar with your rules, and add it as a build extension so
it's available on the classpath.
Yes it can. Although the preferred method is to make it a dependency of
the PMD plugin. Extensions work, but it's
linkXreftrue/linkXref
sourceEncodingutf-8/sourceEncoding
minimumTokens100/minimumTokens
rulesets
ruleset${basedir}/src/site/pmd.xml/ruleset
/rulesets
/configuration
/plugin
The line ruleset${basedir}/src/site/pmd.xml/ruleset causes problems
targetJdk1.5/targetJdk
linkXreftrue/linkXref
sourceEncodingutf-8/sourceEncoding
minimumTokens100/minimumTokens
rulesets
ruleset${basedir}/src/site/pmd.xml/ruleset
/rulesets
/configuration
/plugin
The line ruleset
Hi all,
I've got some unit tests in a subproject of a multiproject that run fine
when building from the subproject's basedir, but when the subproject is
built as part of the multiproject build (that is, maven is launched in the
parent directory), the basedir is that of the parent directory
the subproject's basedir, but when the subproject is
built as part of the multiproject build (that is, maven is launched in the
parent directory), the basedir is that of the parent directory, and my
unit
tests fail to find the resources they need to test (some xml files).
How does Maven 1 handle setting
cl29 wrote:
Good day to you, Franz!
Good day to Arnaud!
Thanks for your fast reply and sorry for my late reply.
I have tested this with Maven2 now, and basedir properties in conf/pom.xml
as you mentioned below, but scm:update announces as workingdir
project/conf and by this does
I'm trying to build a multi-module project that requires some
resources (an xsl file) to complete. The location of the XSL file is
relative to ${basedir}, which changes based on whether I am in the
sub-module or at the top level. As a result, the processing can find
the necessary
,
I am not sure if I understand your situation perfectly ( your post seems
to
be wrapped into one long line ). But you may want to try adding
project
...
properties
basedir!-- your path --/basedir
/properties
/project
See [1] for more info.
Cheers,
Franz
[1] http
Good day to you, cl29,
I am not sure if I understand your situation perfectly ( your post seems to
be wrapped into one long line ). But you may want to try adding
project
...
properties
basedir!-- your path --/basedir
/properties
/project
See [1] for more info.
Cheers,
Franz
[1
...
properties
basedir!-- your path --/basedir
/properties
/project
See [1] for more info.
Cheers,
Franz
[1] http://maven.apache.org/ref/2.0.4/maven-model/maven.html
cl29 wrote:
we are going to change our cvs, splitting our project into modules and
for
this reason project.xml
|_
New structure: |_ conf |_build.properties
|_project.properties |_project.xml |_ src |_ tools |_ ...So files -
usually corresponding to ${basedir} - are no longer in the top level
directory and goals like scm:update for example working recursive start in
directory conf and miss
Basedir depends entirely on where you are executing Maven from...
AFAIK, ${basedir} actually resolves to the current pom.xml's directory,
so if yo run mvn install on a multimodule project, the submodules have
a basedir still set to their own directories, not the one of the
multimodule
Is there some property readily available that represents the directory
from which maven was run from?
Something like ${basedir} in ant?
1 - 100 of 196 matches
Mail list logo
