src/main/resources is not a java source folder during maven command line build. The only reason m2e configures src/main/resources as java source folder is to make it visually stand out in Package Explorer viewer. Actual resource processing is implemented in m2e builder. If you remove excludes=**, this will enable both m2e and jdt process the same resource folders and I can't really tell what'll happen. I guess it will work in most cases but will very infrequently fail in some obscure and hard to troubleshoot ways.
You can develop trivial m2e extension that automatically removes excludes=** from resource folders, but I believe proper solution here is alternative way to map maven project build to eclipse workspace. Should not be too hard if you have experience eclipse plugins and I can give you some pointers and more detailed explanation on m2e-dev mailing list if you want to try. -- Regards, Igor On 2013-03-26 4:22 PM, Duncan Jones wrote:
Hi, I'm trying to use an Eclipse plugin called JInto (http://www.guh-software.de/jinto_en.html) to manage i18n properties files. The author claims it can work with any properties files "on the classpath". My properties files are located in src/main/resources. In this location the JInto plugin cannot use them. However, if I adjust my .classpath entry to remove the `excluding="**"' attribute for src/main/resources, the plugin is happy. This leads to a couple of questions: - Would I trigger any problems if I remove this attribute? - Is there an automatic way to make this change, e.g. via a POM alteration or similar? Thanks, Duncan _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
