> Hello Borut,
> > > placing those config files in your src/main/resources will make them
> > > visible
> > > in classpath. filter them out in your jar plugin and you won't see
> them
> > > during packaging. And you said you know how to do this. :
> > On Fri, Apr 4, 2008 at 3:50 AM, Borut Bolčina <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Hello,
> > >
> > > I would like to
> > >
> > > - filter config directory (some property/configuration files),
> > > - don'
n your jar plugin and you won't see them
> > during packaging. And you said you know how to do this. :)
> >
> >
> > On Fri, Apr 4, 2008 at 3:50 AM, Borut Bolčina <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Hello,
> > >
> > >
>
> On Fri, Apr 4, 2008 at 3:50 AM, Borut Bolčina <[EMAIL PROTECTED]>
> wrote:
>
> > Hello,
> >
> > I would like to
> >
> > - filter config directory (some property/configuration files),
> > - don't package the content of the conf
]>
wrote:
> Hello,
>
> I would like to
>
> - filter config directory (some property/configuration files),
> - don't package the content of the config it in the jar
> - and make config directory a classpath entry for the exec:java plugin
>
> I know how
Hello,
I would like to
- filter config directory (some property/configuration files),
- don't package the content of the config it in the jar
- and make config directory a classpath entry for the exec:java plugin
I know how to filter src/main/resources.
Any tips?
Cheers,Borut
