[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] exclusion filter "**" for src/main/resources?
|
In short, to make resource filtering work correctly and reliably, m2e needs full control over processing of resources. m2e only creates resource folders as a visual cue in Package explorer. We can't guarantee correct behaviour if excludes=** is removed.
Under the hood, m2e executes maven-resources-plugin on each resource change to make sure resources are copied to the output filder.
--
Sent from my SGS
Stephan Herrmann <stephan@xxxxxxxxxxxxxxx> wrote:
>In the old m2eclipse we've been annoyed by the exclusion filter "**"
>that is generated into the classpath entry for src/main/resources,
>because incremental compile would not copy resources, only full build
>would.
>So we had to remove the exclusion filter after each checkout +
>configure.
>
>Using m2e 1.0 I'm surprised to see that the exclusion filter is still
>generated, but copying seems to be correctly triggered for each save.
>Apparently, the maven builder does this, instead of the java builder?
>
>Could you please explain the intention behind putting s.t. on the
>classpath
>but excluding everything? It looks funny to me.
>
>Also: since in the past we kept removing that exclusion filter,
>would this habit cause havoc in m2e (like concurrent copying of the
>same files with the potential of write conflicts etc)?
>
>thanks,
>Stephan
>
>_______________________________________________
>m2e-users mailing list
>m2e-users@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/m2e-users
