Brian, many thanks for suggestions an explanation :-)
>>I was just wondering whether there is a possibility to check if the >>rule was >>OK at least once in a tree - not for every single pom. And if it failed >>in >>every pom then use the value in <fail></fail> to fail the compilation >>or not. > >Ugh. That would require aggregation and then attempting to walk all the >reactors at once. The aggregation and requiresDependencyResolution don't >work well together in Maven when bound to a lifecycle. Either way it's a >whole new rule so it can't be done now. Yeah, that's what I thought :-) But do you see any point in adding it in the future? Or you think it wouldn't be very popular? >>Well, if I have to check the properties in the modules where they >>appear >>I'll live with it :-) >>But if you have any idea for my case, please let me know about it. > >You could use properties to enable/disable the rule and/or value check. But using properties would make me put some extra code to every pom in my tree. And after some changes I would have to remember to update some enabling/disabling the rules checking etc. At least that's how I see it now. I will put my rules into the exact poms. But thank you once again. Best Pawel -- View this message in context: http://www.nabble.com/Checking-properties-in-a-multi-pom-environment-tp18945713p18962676.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]
