Found it!
org.codehaus.plexus.util.introspection.ReflectionValueExtractor
:)
On Jan 7, 2013, at 8:05 PM, Marcos Mendez wrote:
> Hi,
>
> I'm writing a plugin and need to be able to dynamically resolve properties
> (e.g. project.version, java.version, etc). Does anyone know which component
> d
Hi,
I'm writing a plugin and need to be able to dynamically resolve properties
(e.g. project.version, java.version, etc). Does anyone know which component
does this? The neither the maven project properties not the session execution
properties have them.
Thanks!
---
Thank you for your answers, i didn't know about this solution.
On 06/11/2012 03:48 PM, Pascal Rapicault wrote:
It could mostly likely be specified on the command line.
On 2012-06-11, at 9:44 AM, Cédric Teyton wrote:
Hello,
I've a question with respect to some POM.xml files i've observed rece
hello,
this seem a property under your server properties
cheek your server properties,
2012/6/11 Cédric Teyton
> Hello,
>
> I've a question with respect to some POM.xml files i've observed recently.
> In some cases like the following one :
>
>
> 4.0.0
> activemq-web
> activemq-web
> ActiveMQ
It could mostly likely be specified on the command line.
On 2012-06-11, at 9:44 AM, Cédric Teyton wrote:
> Hello,
>
> I've a question with respect to some POM.xml files i've observed recently. In
> some cases like the following one :
>
>
> 4.0.0
> activemq-web
> activemq-web
> ActiveMQ :: Web
Hello,
I've a question with respect to some POM.xml files i've observed
recently. In some cases like the following one :
4.0.0
activemq-web
activemq-web
ActiveMQ :: Web
4.0-M2
Web Connector for REST API and Streamlets support
...
springframework
spring
${spring_version}
...
I ju
> I am suspecting that there is some plugin that is responsible for
> evaluating the properties and the version in use are different for the
> 2 cases, can some please help me identify which plugins could be
> responsible for it, then I can include it in the plugin management.
There is no plugin,
Hi,
Just confirmed that the difference in effective POM in 2 cases is here -
junit
junit
3.8.1
test
The properties are correctly resolved to -
4.8.2
I am suspecting that there is some plugin that is responsible for
evaluating the properties and the version
On Fri, Jun 24, 2011 at 9:20 PM, Wayne Fay wrote:
>> and overrides the property junit.version to 4.8.2 by -
>>
>> 4.8.2
>>
>
> Rather than running mvn -X, what does mvn help:effective-pom give you?
>
Thanks for the suggestion. The effective POM for the one resolving to
3.8.1 shows:
> and overrides the property junit.version to 4.8.2 by -
>
> 4.8.2
>
Rather than running mvn -X, what does mvn help:effective-pom give you?
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additio
Hi,
I am facing a ambiguous problem with property resolution, specifically
the properties defined in POM. I have defined
junit
junit
${junit.version}
test
in dependency management of my parent POM
(https://github.com/imyousuf/smart-core/blob/smart
I've been trying to use a property reference in the section
of my settings.xml file to define the username.
But this does not seem to work, nor do property references in the
password field seem to work.
Yet clearly properties are supported in some parts of the section:
http://maven.apache.org/
]
> Sent: Thursday, October 15, 2009 2:13 PM
> To: Maven List
> Subject: Property resolution
>
> Hi all,
>
> I am playing around with some properties in my surefire-plugin... I need
> the ${settings.localRepository} in my tests, but it seems this is not
> being resolve
To: Maven List
Subject: Property resolution
Hi all,
I am playing around with some properties in my surefire-plugin... I need the
${settings.localRepository} in my tests, but it seems this is not being
resolved. Any other properties I try to pass, seem to work...
Is this a known bug or am I
Hi all,
I am playing around with some properties in my surefire-plugin... I need the
${settings.localRepository} in my tests, but it seems this is not being
resolved. Any other properties I try to pass, seem to work...
Is this a known bug or am I doing something wrong here?
--
Roland Asmann
Building a test project shows that actually the property resolution
seems fine (so is getting the right version), it's just not invoking
the plugin - instead I get
ERROR] BUILD ERROR
[INFO]
[INFO] 'mymojo' w
Hi
I have a big reactor project. In one project, there is a property set as
2.2.1
and in a later project, it is
2.2.4-SNAPSHOT
..
commons
commons-maven
I have a property defined in a profile. I have 3 modules in a parent
project. When I build the parent project the modules build correctly,
where the modules correctly resolve the property defined in the profile.
When I build the modules individually using the profile, the property
from the profil
Thanks for your help.
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. If
you are not the intended recipient, you should delete this message.
Any disclosure, copying, or distribution of this
n.apache.org
Subject: Inherited property resolution
I have a parent project which defines a test_version property, and a
child project which attempts to this property, which is the version of
the application in this case. However, when doing a build, the
test_version property of the parent element d
I have a parent project which defines a test_version property, and a
child project which attempts to this property, which is the version of
the application in this case. However, when doing a build, the
test_version property of the parent element does not get resolved. I
get this error. May some
21 matches
Mail list logo
