I think I know where the problem is. Basically, if you
execute the reactor Goal in Project A, Project A's
properties overwrites all other definitions. If you
execute in Project B where 'conf.dir' is not defined,
you will get the right behavior. I am going to report
this as a bug in JIRA.
=====
Apparently, Maven allows only one definition of a
property in reactor.
Consider the following scenario:
Project A
project.properties
==================
conf.dir=/A/conf
Project B
project.properties
==================
No definition of conf.dir
My Plugin
plugin.jelly
============
<goal name="testProperty">
<echo>conf.dir=${conf.dir}</echo>
</goal>
plugin.properties
=================
(default conf.dir)
conf.dir=${maven.src.dir}/conf
If you have a reactor that executes both A and B's
testProperty goal, A's conf.dir property will be used
when running B's goal.
This is unexpected because when we execute B by
itself, it uses the default conf.dir property defined
in the Plugin.
Do we have some workaround (other than defining
conf.dir in B)?
Charles
__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
