hmmm I suspect that what you'd need is profiles
you could activate a profilein the child if the file is present On 22/04/2009, Anastasios Angelidis <[email protected]> wrote: > I guess if that's what you call them lol > > So yes if the .properties file is in the parent then use that one. If > it's in the child module use the child one. > > > Stephen Connolly wrote: >> Ahhhh >> >> you want to use the value from the parent if the parent is in the current >> reactor but if the parent is not in the current reactor, you want to use >> the >> value from the child? >> >> Is that what you are trying to do? >> >> -Stephen >> >> 2009/4/22 Anastasios Angelidis <[email protected]> >> >> >>> Sometime we build the entire project sometimes just individual modules. >>> >>> Each module has it's own filters right now. >>> >>> Basically if the parent filter exists then use that one. If only building >>> an individual module then use it's filter. >>> >>> >>> >>> >>> Grant Rettke wrote: >>> >>> >>>> And each individual module should have filtering on right? >>>> >>>>> >>>> If you want to share them, what would you be filtering out? >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>>> >>>> >>>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
