[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] exclusion filter "**" for src/main/resources?
|
Hey.
As you mentioned the question came up with the previous versions as well. The reason, as I understand it, is that you want the resource folders to be represented as part of the classpath in Eclipse. BUT you also want it to work the same in Eclipse and building only with Maven. So everything is excluded so the Maven builder can handle the resources according the pom.
I don't think anything will break with you removing the filter, as the Eclipse builders run in sequence and not parallel AFAIK. But the reasons for doing so should likely be put in a bug report so better solutions could be considered.
>---- Original Message ----
>From: Stephan Herrmann <stephan@xxxxxxxxxxxxxxx>
>To: m2e-users@xxxxxxxxxxx
>Sent: Sun, Jun 19, 2011, 5:37 PM
>Subject: [m2e-users] exclusion filter "**" for src/main/resources?
>
>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
