On Dec 4, 2007 3:40 AM, heimlich <[EMAIL PROTECTED]> wrote:
> The problem is that each subproject tries to refer to the 'filters'
> directory IN ITS OWN directory structure,
> not the one at the top.
>
> The reason for this structure is that I want:
>
> ONE conf.properties
> ONE filter file per pr
>
> >> >
> >> >
> >> >
> >> > test
> >> >
> >> >
> >> > ${basedir}/filters/test.properties
> >> >
> >> >
>
; >src/main/resources
>> >true
>> >
>> >
>> >
>> >
>> >
>> > prod
>> >
>> >
>> > ${basedir}/filters/prod.properties
>
; >
> >
> >
> >
> > The problem is that each subproject tries to refer to the 'filters'
> > directory IN ITS OWN directory structure,
> > not the one at the top.
> >
> > The reason for this structure is that I want:
> >
>
red conf.propertiesin
> each project's resources directory).
> Can it be done (how?) or should try a different approach (any
> suggestions)?
>
> Or should I have no filtering, and just three different properties files
> (dev, test and prod)
> at the top and have them included in eac
this message in context:
http://www.nabble.com/Profiles-and-filtering---global-files-tf4942371s177.html#a14148383
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
