: 2.0
>> >>>>>>>>>>>> * Required: No
>> >>>>>>>>>>>> * Expression: ${maven.compiler.source}
>> >>>>>>>>>>>>
>> >>>>>>>>>>> Th
iler.source}
> >>>>>>>>>>>>
> >>>>>>>>>>> This means that if the property maven.compiler.source is
> >> defined,
> >>>>> use
> >>>>>>>> that
> >>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>> How can I get that value? If it is not evaluable as an
>> expression,
>>>>> how
>>>>>>>>>>>> can I know how it will be evaluated by the plugi
gt;> >>>> 2010/7/13 Anders Hammar :
> >>> >>> >>>>> No, you're not configuring the property that way. You're
> >>> configuring
> >>> >>> the
> >>> >>> >>>>> plugi
t configuring the property that way. You're
>>> configuring
>>> >>> the
>>> >>> >>>>> plugin, but you're not setting the property.
>>> >>> >>>>> A property is set in hte propertie
t; >>>>> /Anders
>> >>> >>>>>
>> >>> >>>>> On Tue, Jul 13, 2010 at 00:34, Flavio Pompermaier <
>> fla8...@gmail.com
>> >>> >
>> >>> >>>> wrote:
>> >>> >>>>
le via the configuration section of the
> compiler
> >>> >>>>>> plugin of my pom.xml but the result of help:evaluate of that
> >>> variable
> >>> >>>>>> returns null! My question is: how can I retrieve the default
> v
le via the configuration section of the
> compiler
> >>> >>>>>> plugin of my pom.xml but the result of help:evaluate of that
> >>> variable
> >>> >>>>>> returns null! My question is: how can I retrieve the default
> v
;>> >>>>>> returns null! My question is: how can I retrieve the default values
>>> of
>>> >>>>>> the parameters of a certain plugin version?if I look at the plugin
>>> >>>>>> site I can see that its default value is 1.5.
>>>>>> site I can see that its default value is 1.5. But this is valid for
>> >>>>>> the current version..if I want to know its default value for an
>> older
>> >>>>>> version what am I supposed to do??
>> >>&
> >>>>>> 2010/7/12, Anders Hammar :
> >>>>>>> This does work for me:
> >>>>>>>
> >>>>>>> mvn help:evaluate -Dmaven.compiler.source=1.5
> >>>>>>> -Dexpression=maven.compiler.source
> >
gt;>>>> 2010/7/12, Anders Hammar :
>>>>>>> This does work for me:
>>>>>>>
>>>>>>> mvn help:evaluate -Dmaven.compiler.source=1.5
>>>>>>> -Dexpression=maven.compiler.source
>>>>>>>
>&
er.source
>>>>>>
>>>>>> I'm setting the maven.compiler.source property here on command line
>>>>> instead
>>>>>> of specifying it in the project, which should work the same.
>>>>>>
>>>>>> /An
erty here on command line
>> >> instead
>> >> > of specifying it in the project, which should work the same.
>> >> >
>> >> > /Anders
>> >> >
>> >> > On Mon, Jul 12, 2010 at 23:27, Justin Edelson
>&
.
> >> >>
> >> >> Could it be that maven.compiler.source is, in fact, null?
> >> >>
> >> >> On 7/12/10 5:23 PM, Flavio Pompermaier wrote:
> >> >> > I mean,how can I display their value?
> >> >> &
t;> On 7/12/10 5:23 PM, Flavio Pompermaier wrote:
>> >> > I mean,how can I display their value?
>> >> >
>> >> > 2010/7/12, Justin Edelson :
>> >> >> what do you mean by inspect?
>> >> >>
>
their value?
> >> >
> >> > 2010/7/12, Justin Edelson :
> >> >> what do you mean by inspect?
> >> >>
> >> >> On 7/12/10 1:13 PM, Flavio Pompermaier wrote:
> >> >>> Hi to all,
> >>
to do.
>>>
>>> Could it be that maven.compiler.source is, in fact, null?
>>>
>>> On 7/12/10 5:23 PM, Flavio Pompermaier wrote:
>>> > I mean,how can I display their value?
>>> >
>>> > 2010/7/12, Justin Edelson :
>>&g
ean by inspect?
>> >>
>> >> On 7/12/10 1:13 PM, Flavio Pompermaier wrote:
>> >>> Hi to all,
>> >>> is there a way to inspect maven.* variables (such as
>> >>> ${maven.compiler
son :
> >> what do you mean by inspect?
> >>
> >> On 7/12/10 1:13 PM, Flavio Pompermaier wrote:
> >>> Hi to all,
> >>> is there a way to inspect maven.* variables (such as
> >>> ${maven.compiler.source})?
> >>> I tr
t;
>> On 7/12/10 1:13 PM, Flavio Pompermaier wrote:
>>> Hi to all,
>>> is there a way to inspect maven.* variables (such as
>>> ${maven.compiler.source})?
>>> I tried to use the help:evaluate tool but it tells me "null object or
>&
I mean,how can I display their value?
2010/7/12, Justin Edelson :
> what do you mean by inspect?
>
> On 7/12/10 1:13 PM, Flavio Pompermaier wrote:
>> Hi to all,
>> is there a way to inspect maven.* variables (such as
>> ${maven.compiler.source})?
>> I tried to
what do you mean by inspect?
On 7/12/10 1:13 PM, Flavio Pompermaier wrote:
> Hi to all,
> is there a way to inspect maven.* variables (such as
> ${maven.compiler.source})?
> I tried to use the help:evaluate tool but it tells me "null object or
> invalid expression".
Hi to all,
is there a way to inspect maven.* variables (such as ${maven.compiler.source})?
I tried to use the help:evaluate tool but it tells me "null object or
invalid expression".
Any idea??
Best regards,
Flavio
--
Hi to all,
is there a way to inspect maven.* variables (such as ${maven.compiler.source})?
I tried to use the help:evaluate tool but it tells me "null object or
invalid expression".
Any idea??
Best regards,
Flavio
--
rc gets compiled to) to the
>> unit tests as a system property?
>>
>> Thanks,
>>
>> Simon
>>
>> On Fri, 2006-03-10 at 11:47 +0100, [EMAIL PROTECTED] wrote:
>> > Hi
>> >
>> > Try project.build.directory
>> >
>> &g
Guide
M-
- Original Message -
Wrom: TLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRN
To:
Sent: Monday, February 25, 2008 10:24 AM
Subject: Maven variables?
> Is there any list of maven variables and their definition?
> I mean the properties that are not custom set like ${basedir}.
>
> Thanks,
> Bart
>
the closest explanation I've seen to date is here
http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide
M-
- Original Message -
Wrom: TLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRN
To:
Sent: Monday, February 25, 2008 10:24 AM
Subject: Maven variables?
> Is there any list
Is there any list of maven variables and their definition?
I mean the properties that are not custom set like ${basedir}.
Thanks,
Bart
I'd be more inclined to set it in profiles.xml, but sure, you can set
it in settings.xml if you want.
Read this for more details on profiles:
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Wayne
On 5/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
We are currently
We are currently passing the -Dserver= on the mvn command line.
This variable is referenced in the pom in the following manor.
src/main/${server}/resources
true
Is it possible to set this variable in the settings.xml file and pas
Hi Gilles,
Thanks for your comments.
On Mon, 2006-07-24 at 23:48 -0700, Gilles Scokart wrote:
> ${project.classpathElements} can be used when your parameter is a List .
> Here you want to place it in a String.
True, and maybe that's the problem. The things that are working are all
of type Strin
://www.nabble.com/Expansion-of-maven-variables-tf1996470.html#a5480707
Sent from the Maven - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
I'm confused by the availability of maven variables, in particular
${project.testClasspathElements}.
In a surefire config section, I've got this:
**/DumpProps.java
test.finalName
${project.build
rty?
>
> Thanks,
>
> Simon
>
> On Fri, 2006-03-10 at 11:47 +0100, [EMAIL PROTECTED] wrote:
> > Hi
> >
> > Try project.build.directory
> >
> > Hermod
> >
> > -Original Message-
> > From: Simon Kitching [mailto:[EMAIL PROTECTED]
rote:
> Hi
>
> Try project.build.directory
>
> Hermod
>
> -Original Message-
> From: Simon Kitching [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 10, 2006 3:53 AM
> To: users@maven.apache.org
> Subject: Passing maven variables as system properties
>
Hi
Try project.build.directory
Hermod
-Original Message-
From: Simon Kitching [mailto:[EMAIL PROTECTED]
Sent: Friday, March 10, 2006 3:53 AM
To: users@maven.apache.org
Subject: Passing maven variables as system properties
Hi,
I'm trying to store some maven vars into system prope
Hi,
I'm trying to store some maven vars into system properties so I can
access them from unit test code:
org.apache.maven.plugins
maven-surefire-plugin
core-static
${project.build.outputDirectory}/
38 matches
Mail list logo
