I tried both approaches:
C:/Documents and Settings/xname/My
Documents/maven/mrt/storage/pom.xml
This project uses <modules> on child projects and no activation would work
for <file> except <missing> and locally set properties were not recognized.
After spotting #MNG-2363 I figured that the earlier bug was not fixed.
I then used profile in the child project:
C:/Documents and Settings/xname/My
Documents/maven/mrt/storage/store-conf/pom.xml
Things are a bit better at least <exists> works with an explicit full path
but not using ${basedir} or any relative path I could find. I should note
that <exists>${basedir}</exists> does NOT work - I did further testing and
dumped ${basedir} within the profile using maven-antrun-plugin and the
variable is set but not being recognized in the activation.
ANY suggestion would be appreciated. At this point I'm forced to move back
to ant for my specialized handling.
Thanks
David Loy
C:/Documents and Settings/xname/My
Documents/maven/mrt/storage/store-conf/mrt.local.properties
--
View this message in context:
http://maven.40175.n5.nabble.com/file-exists-activation-tp3292777p3294266.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
